No, only some multipart messages are causing the error. Maybe it depends on the characters used for the MIME-boundary string. As the workaround...
The problem of course is not that one line message itself. The error occurs with some normal MIME messages with attachments and with virus...
A one line text message, properly encoding and containing just the following line, causes the error "not scanned (archive error)" and the message...
Mails got truncated at lines starting with a dot when delivered via Exim4 with nod32mda. Fix: replace "nod32mda -oMr" with "nod32mda -oi -oMr"...
Even if you just copy the ASCII text into your favorite MUA and send it as a normal text message it does not get past nod32d. Note that in this...
When forwarding some harmless ascii text only message inside a MIME-type "text/rfc822-headers", nod32d in MTA mode crashes with "error occurred...
Yes, that's a very low probability. However if it's really a bug it should be fixed as this problem might occur in other cases, too.
Update: The problem is not caused by the Exchange server as the Mail shows the missing MIME-boundary already in the spool directory before...
The attachments virus1.zip and virus2.pif are correctly removed from the mail as they contain testviruses which cannot be cleaned. However, the...
Is this a known problem or maybe some configuration problem? Multipart MIME messages with attachments look like being corrupted by NOD32 as the...
Separate names with a comma.
