Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't support ending emails with <cf>.<cf> #2

Closed
Joshfindit opened this issue Aug 15, 2019 · 3 comments
Closed

Doesn't support ending emails with <cf>.<cf> #2

Joshfindit opened this issue Aug 15, 2019 · 3 comments

Comments

@Joshfindit
Copy link

Attempted to send email via telnet as a test

telnet localhost:8025
Type: EHLO <mail server internet name>
Type: mail from: <your_name@yourdomain.com> and press Enter.
Type: rcpt to: <recipient@recipientdomain.com> and press Enter.
Type: data and press Enter.
Type: Subject: <a subject here> and press Enter.
Type: This is a test message sent from telnet. and press Enter.
Type: . and press Enter

Server responded as expected up until attempting to confirm the contents of the email. It seemed to take <cr/lf>.<cr/lf> as part of the email body and never continued.

@ont
Copy link
Owner

ont commented Aug 15, 2019

Telnet on linux by default may send <lf> instead of <cr><lf>. Please see answer: https://stackoverflow.com/a/22974813/434255

Also do this steps:

  1. download latest tag 0.0.4 via docker pull ontrif/slacker (it has fix for None fields)
  2. rerun container
  3. run ncat -x /tmp/out.hex --crlf localhost 8025
  4. enter all your commands and data
  5. check that <cr><lf>.<cr><lf> present in /tmp/out.hex
  6. check that email was sent or error occurs via docker logs slacker

Also check that you fill From and To email fields. Currently values from mail from and rcpt to are not used for comparision with rules.

Fill free to reopen this issue.

@ont ont closed this as completed Aug 15, 2019
@Joshfindit
Copy link
Author

Aha. Found the problem: #3

@Joshfindit
Copy link
Author

(For reference, the old version did not respond to <cr><lf>.<cr><lf>. Did confirm it was present in the hex file)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants