This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
Zend Mail does not conform with RFC2822 by not accepting content which contains additional extra lines. #218
Comments
Note the above was tested with Zend Mail 2.4.x. However with Zend Mail 2.10.0 the issue still exists:
The changes in #92 aren't enough to fix the issue. |
Could you provide test scenarios please?
…On Fri, 24 Aug 2018, 17:28 Chris Deeming, ***@***.***> wrote:
Note the above was tested with Zend Mail 2.4.x.
However with Zend Mail 2.10.0 the issue still exists:
An exception occurred: [Zend\Mail\Exception\RuntimeException] Malformed header detected in src/vendor/zendframework/zend-mail/src/Headers.php on line 90
Zend\Mail\Headers::fromString() in src/vendor/zendframework/zend-mime/src/Decode.php at line 141
Zend\Mime\Decode::splitMessage() in src/vendor/zendframework/zend-mail/src/Storage/Part.php at line 99
Zend\Mail\Storage\Part->__construct() in src/vendor/zendframework/zend-mail/src/Storage/Message.php at line 54
Zend\Mail\Storage\Message->__construct() in test.php at line 227
The changes in #92 <#92>
aren't enough to fix the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#218 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJakCGY6f0wQyrUSUR-ptsoSauik33Yks5uUBuGgaJpZM4WLhRM>
.
|
There's example code in the first comment @Ocramius. |
This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at laminas/laminas-mail#25. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Spamassassin in cPanel seems to be appending an
X-Ham-Report
header to emails which Zend Mail can't handle properly due to the existence of additional extra lines.In our opinion this seems to be a rather over-zealous interpretation of RFC2822:
(Emphasis mine)
Example to follow.
Code to reproduce the issue
Expected results
We can see the expected results if we change L80 of Header.php from:
To:
In which case, the following is the resulting headers:
Actual results
Is this a change you would be willing to accept, or is there a reason not to accept the header formatting in this case?
The text was updated successfully, but these errors were encountered: