-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Proper formatting of long subjects. #1437
Conversation
Could you please add test? |
In what way? Does it break any RFC? |
In RFC822 are parts of long headers divided by CRLF. |
In this case testing is IMHO impossible. Emails uses only CRLF, but Unix mail replaces LF by CRLF automatically, which leads to doubling CR if CRLF is used. See http://cz1.php.net/manual/en/function.mail.php According to PHP source codes, Subject + To must contain CRLF. Can you fix "To" too? |
This commit caused me problems when Is this problem on wedos mailserver or is it possible, that the solution is not 100% correct? |
@CasperN confirming the problem.. Some of our clients receive base64 chars instead of attachments. Reverting to the version with str_replace fixed it. |
Reopening the issue. |
It is related to "subject" or "to" parameter? |
Seems its subject related problem (http://i.imgur.com/IvCRbUf.png) |
…#1437 (comment) This reverts commit bc797e0.
…#1437]" See: nette/nette#1437 (comment) This reverts commit 67d37e3.
Under Windows Message::EOL and PHP_EOL are same and everything work fine. But in Linux \r\n is replaced by \n and long subjects are send in wrong format.