Differences

This shows you the differences between two versions of the page.

--- how_to:data_stream_contained_nul_character [2016/05/11 09:39] – paul
+++ how_to:data_stream_contained_nul_character [2018/11/14 10:45] (current) – external edit 127.0.0.1
@@ Line 8: / Line 8: @@
 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, and it will stop collecting further messages. This is because there is no way for VPOP3 to automatically know what is the right thing to do in this situation. For a standards compliant remote POP3 mail server, the only way this problem could occur is if there is mailbox corruption on the remote server, so aborting the connection and reporting an error is the best thing to do to minimize further damage. For a non-standards complaint remote POP3 server, if the message is downloaded with the NUL character intact, it will make VPOP3 non-compliant also; if the NUL character is skipped or replaced, then that could cause a loophole for virus scanning; if the message is skipped it could cause an important message to be lost. So, reporting an error and aborting the connection lets the administrator work out the best solution for this particular instance - preferably by reporting the error to the remote mail server administrators and having them fix the bug or mailbox corruption in their server.
+For incoming POP3, VPOP3 will not download the message, it will report an error message to the administrator, and it will stop collecting further messages. This is because there is no way for VPOP3 to automatically know what is the right thing to do in this situation. For a standards compliant remote POP3 mail server, the only way this problem could occur is if there is mailbox corruption on the remote server, so aborting the connection and reporting an error is the best thing to do to minimize further damage. For a non-standards compliant remote POP3 server, if the message is downloaded with the NUL character intact, it will make VPOP3 non-compliant also; if the NUL character is skipped or replaced, then that could cause a loophole for virus scanning; if the message is skipped it could cause an important message to be lost. So, reporting an error and aborting the connection lets the administrator work out the best solution for this particular instance - preferably by reporting the error to the remote mail server administrators and having them fix the bug or mailbox corruption in their server.
 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).
@@ Line 40: / Line 40: @@
 Set the <asciicode> to '0' to have the characters rejected, '255' to have them skipped, or any other [[http://www.asciitable.com/|ASCII code]] (1 to 254) to have them replaced with that character
-**Note:** you should use VPOP3 v6.16 or later if possible. Earlier versions had a bug which meant this setting did work in every situation.
+**Note:** you should use VPOP3 v6.16 or later if possible. Earlier versions had a bug which meant this setting did not work in every situation.
 Keywords: null character 10506

PSCS Wiki

User Tools

Site Tools

Differences

Page Tools