-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Plain text part of a DSN is treated as attachment #137
Labels
Comments
Aah, yeah, I think my comment was wrong but the code would have to be consulted... definitely missing some documentation there. I believe my comment in #87 only applies for text/plain text/html, and anything that's not text/plain text/html is an attachment. I'll look it up though and update docblocks/put something on the main README and/or webpage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have this:
It looks like a normal Delivery Status Notification (DSN, see RFC 3461) to me (I didn't double-check if everything's valid, though).
My question is: How many attachments are there?
The third part of the DSN is the original message, which contained an attached PDF. The rest (i.e. the first two parts of the DSN) is just text.
Thunderbird gives 2 attachments:
.eml
(and extract the PDF from there).Your library gives 2 other attachments:
message/delivery-status
(i.e. just those few lines of plain text, starting withReporting-MTA: dns;mail.example.com
)message/rfc822
(Thunderbird's point 1)php-mime-mail-parser gives 3 attachments:
message/delivery-status
(same as yours)message/rfc822
(Thunderbird's point 1)At #87 (comment) you said:
But as far as I see it, the
message/delivery-status
part doesn't tell you it's an attachment ;-)So what's your reasoning?
The text was updated successfully, but these errors were encountered: