-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Sending MAIL command twice #13
Comments
Should be fixed with 1034ae8 - if the server supported only HELO but not EHLO then all commands were sent twice. |
You are the fastest bug-fixer ever :) |
Thanks :) |
Would this also have caused the callback to return twice, i.e. is the callback only supposed to return once? |
If the response for an EHLO command was erroneos (server didn't support it) then an additional HELO request was made. As there was a bug then the original "thread" (the EHLO one) didn't stop there and tried to continue anyway regardless of the error. Meanwhile HELO ended with success and started it's own separate command "thread" (actually it's not a thread but a callback chain or smth.), so as a consequence a set of two "threads" were sending matching commands to the same connection and thus fireing the callback function also not once but twice (one from the EHLO and one from the HELO thread). In short - welcome to the wonderful world of callbacks and events :) |
I've been in this world for a while. |
I'm encountering this issue. While trying to debug it I noticed that this merge seems to have removed the fix: |
When talking to a Python SMTP server (i.e. using stmpd.py), the MAIL command is sent twice, which is illegal SMTP. Nodemailer v0.1.9 and Node v0.4.2.
generates the following output:
The text was updated successfully, but these errors were encountered: