I have SMTP parser that works mostly fine. There is a problem when receiving traffic from third party software that sends double newlines as "\r\n\r" (without the second "\n"). Currently such connections are terminated as non-compliant SMTP. Can somebody explain what exactly RFC says about such "funny" double newlines? Can I asume that software that sends data like that is doing something really wrong?
相关问题
- Django & Amazon SES SMTP. Cannot send email
- How to add sender name before sender address in py
- How can I detect a space or newline at the end of
- Squeak(smalltalk) subSrings ignores empty strings
- TCL Email Script doesn't deliver in Activestat
相关文章
- c#发送邮件,附件损坏
- com.sun.mail.smtp.SMTPSenderFailedException: 550 5
- JSON.parse with newline [duplicate]
- Python thinks a 3000-line text file is one line lo
- Outlook SMTPClient server error 5.3.4 5.2.0
-
553 5.7.1
: Sender address rejected: not - Is there an equivalent of BufferedReader.readLine(
- Java FileWriter how to write to next Line
Various operating systems have various representations for Newline characters. Check the instructions here on newline characters.. By the way its a common practice among programmers to use both the
\n
and\r
together to prevent any conflicts on the system. You need to check which newline character is supported by your system. If its\r
then you are getting both the required characters. But if its\n
, then the error lies with the sender.RFC2821. Section 2.3.7:
http://www.ietf.org/rfc/rfc2821.txt
--Dave