-
Notifications
You must be signed in to change notification settings - Fork 24
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
e-mail is not recognised as bouncemail and is skipped #127
Comments
Thank you for the detailed report and sample email above. The entire message body of the second message of "inbox.txt" is BASE64 encoded text:
The following sting is decoded text of the message above. Delivery to the following recipient failed permanently:
doesnotexist@sanyutechnos-ph.com
Technical details of permanent failure:
Google tried to deliver your messa I think, implementation of additional codes for decoding BASE64 text in a message body required to parse the message like the second mail in "inbox.txt". It seems that implementation is not so difficult. |
…ng MIME encoded message body and are called from Sisimai::Message->resolve().
…t for parsing us-google-14.eml attached at issue #127
The second message could be parsed by the code of "message-body-is-base64" branch and the codes return the following results:
|
Created Pull-Request #132 |
Implementation to resolve issue #127
I would just like to inquire something regarding Sisimai.
I am currently using this version:
I have been using the above version of Sisimai and have encountered the following problem.
There seem to be a problem in the analysis of an email if it contains multiple Chinese characters.
the return of Sisimai->make( $mailbox ); does not include e-mails that have multiple chinese characters.
the following are the test scenarios I have tried:
(1) Long english email. Result: Success
(2) multiple chinese characters email. Result: Fail
(3) minimal chinese characters email. Result: Success
Also attached is the mailbox copy of the 3 mails above.
As per initial feedback regarding this issue via e-mail consultation:
"Message body of the second mail in inbox.txt is BASE64 encoded string.
As of present, Sisimai does not decode BASE64 string and can not parse such bounce message."
inbox.txt
The text was updated successfully, but these errors were encountered: