This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
how_to:data_stream_contained_nul_character [2015/11/16 09:45] – paul | how_to:data_stream_contained_nul_character [2015/12/22 17:35] – paul | ||
---|---|---|---|
Line 3: | Line 3: | ||
In some cases, messages will arrive at VPOP3 which do contain such characters. This is usually due to a bug in the upstream mail server which has accepted a message with a NUL character and is passing it on unchanged. The email standards say that these characters are not allowed, so they should not be passed on. | In some cases, messages will arrive at VPOP3 which do contain such characters. This is usually due to a bug in the upstream mail server which has accepted a message with a NUL character and is passing it on unchanged. The email standards say that these characters are not allowed, so they should not be passed on. | ||
+ | |||
+ | For incoming SMTP, VPOP3 will reject a message that contains a NUL character and the sender should receive a delivery failure report. This is the correct thing to do when receiving an invalid message. | ||
+ | |||
+ | For incoming POP3, VPOP3 will not download the message, it will report an error message to the administrator, | ||
So, the ideal solution would be for the upstream mail server to sort the problem out, as the problem is coming from there (they should either reject the message, or recode the message to base64 or quoted-printable encoding). | So, the ideal solution would be for the upstream mail server to sort the problem out, as the problem is coming from there (they should either reject the message, or recode the message to base64 or quoted-printable encoding). |