Originally Posted by wls
I did not solve this - rather, the sending mailer had a misconfiguration problem which they eventually fixed (and the problem with the /t before the .^M went away). I'm not sure how other MTAs (e.g. Exchange) would have handled that syntax error. I'd also be curious as to what mailer they were using that could have caused their problem.
I found this topic because I am sitting on the other end of the line - having the problem as the sender of the e-mail.
In my SMTP Log every connection ends at 354+Enter+mail,+end+with+"."+on+a+line+by+itself.
I just got the log-file of the recipient which says:
SYSERR(root): collect: read timeout on connection from mymailserver.at
We had a few mail sending issues (everytime with the connection dropped after the 354 ... was received) because of bad formatted newlines (\n was used but \r\n is expected) - but these problems are solved.
Our system generates about 500 Messages every day and sends them to about 400-500 different receipients, but just one of those receipients generates this error and the mail cannot be sent. (the product of my company are pdf files which are delivered by email...)
Opening the undelivered Mail with the regular e-mail program and resending it over the normal MTA (Exchange
) is working fine.
So it has to do with the formatting, newlines, ... of the message content.
If someone has a clue what the problem could be please reply.
thank you in advance, yours rene