Problems with inline warnings.
Michael Svendsen
michael at NSEC.DK
Wed Aug 20 13:01:42 IST 2003
Hi again
here is the version no. of the perl packages.
Btw. I use Mailscanner ver. 4.22-5
dev-lang/perl 5.8.0-r12
dev-perl/IO-stringy 2.108-r1
dev-perl/MIME-Base64 2.20
dev-perl/MailTools 1.58
dev-perl/File-Spec 0.84-r1
dev-perl/HTML-Tagset 3.03-r2
dev-perl/HTML-Parser 3.30
dev-perl/MIME-tools 5.411a-r2
dev-perl/File-Temp 0.12
dev-perl/Convert-TNEF 0.17-r2
I have not applied the security-patches, since I thought that they were
included in the new version of MIME-tools.
Best Regards
Michael
-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
Behalf Of Julian Field
Sent: Wednesday, August 20, 2003 12:54 PM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: Problems with inline warnings.
At 03:10 20/08/2003, you wrote:
>Hi m8s
>
>I just re-installed a server with Mailscanner, but now I have some smaller
>problems (I hope)
>
>1) Even though I've set "Warning is attachment" to no I get all
>warnings as
>a attachment.
In which case you have a bug in your email app. The warnings are sent an
"inline" MIME sections in this case and should be rendered with the main
body text.
>2) Sometimes the Mailscanner "forgets" renaming the warning
attachment.
> Ex:
> I send a test.bat from a at mydomain.com to b at mydomain.com
>
> a at mydomain.com becomes the warningmessage that he has
> sent a bad file -
>good.
>
> b at mydomain.com gets the mail subject is {Filename?}..
> WITH an attachment.
> the attachment is named test.bat - but with the warning
> as content...
>weird.
>
>Any ideas?
Not a clue on that one. Never seen it before.
How did you install MailScanner? If you used the manual installation route
did you successfully apply all 4 security patches to MIME-tools? Did you
use the version of MIME-tools I recommend?
--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support
More information about the MailScanner
mailing list