Could not check ... (corrupt)
mailscanner at ecs.soton.ac.uk
Wed Jan 22 16:21:03 GMT 2003
Please can you send me a copy of the entire original message so that I can
see what is going on?
Don't post it to the list, just directly to me.
At 15:35 22/01/2003, you wrote:
>Saw this message a couple of time since we're running production,
>most of the time it's because of DSN's which include the original attachment
>sent (where the original message is one mime-part and the original attachment
>is not a separate mime-part in the DSN messag because the mime boundaries
>But i also got it on a "correct" message:
>Content-Type: multipart/mixed; boundary="part1_181.15952dd4.2b5fd091_boundary"
>Content-Type: text/plain; charset="US-ASCII"
>Content-Type: application/octet-stream; name="Notulen COB 13-01-03.doc"
>Content-Disposition: attachment; filename="Notulen COB 13-01-03.doc"
>Any ideas why it coudn't extract the attachment? I did it by hand using
>perl -MMIME::Base64 -ne 'print decode_base64($_)' < file > x.doc
>and that worked ok, and the document contained no virusses.
>Could it be the spaces?
>We are using mailscanner-4.11-1 on RedHat-8 with Sophos.
>These are the logs:
>Jan 22 11:47:08 MailScanner: Could not check
>./h0MAl3er016081/Notulen COB 13-01-03.doc (corrupt)
>Jan 22 11:47:09 MailScanner: Saved entire message to
>Jan 22 11:47:09 MailScanner: Saved infected "Notulen COB
>13-01-03.doc (corrupt)" to
>thanx in advance,
>Ewald Beekman, Security Engineer, Academic Medical Center,
>dept. ADB/ICT Computer & Network Services, The Netherlands
>## Your mind-mint is:
>Don't you wish you had more energy... or less ambition?
MailScanner thanks transtec Computers for their support
More information about the MailScanner