You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please add the ability to parse the text file attachment as file when the Content-Disposition: attachment header exists for the part. I have a mail with following part configuartion:
The createPartParserForHeaders method tries to parse this attachment as text part of the mail, so it tries to convert its encoding to utf-8 and fails, because it tries to interpret the part as 'us-ascii'. This is the attachment so it has no the encoding headers (actual file encoding can be any multibyte enoding to cause the mail parsing failure). If I set the ezcMailPartParser::$parseTextAttachmentsAsFiles to True the entire mail is parsed successfully, but it consists from attachments only, without any body text.
The text was updated successfully, but these errors were encountered:
speller
changed the title
Force parce text file attachment as file when Content-Disposition: attachment header
Force parse text file attachment as file when Content-Disposition: attachment header
Apr 15, 2016
Please add the ability to parse the text file attachment as file when the
Content-Disposition: attachment
header exists for the part. I have a mail with following part configuartion:The
createPartParserForHeaders
method tries to parse this attachment as text part of the mail, so it tries to convert its encoding to utf-8 and fails, because it tries to interpret the part as 'us-ascii'. This is the attachment so it has no the encoding headers (actual file encoding can be any multibyte enoding to cause the mail parsing failure). If I set theezcMailPartParser::$parseTextAttachmentsAsFiles
to True the entire mail is parsed successfully, but it consists from attachments only, without any body text.Suggested fix at part_parser.php:170:
The text was updated successfully, but these errors were encountered: