AW: Problems with TNEF and long filenames

[Randal, Phil]

You could alsways add a 

  Safe TNEF Filenames

option in MailScanner.conf

Cheers,

Phil

--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Julian Field
> Sent: 31 January 2008 09:37
> To: MailScanner discussion
> Subject: Re: AW: Problems with TNEF and long filenames
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> Ehle, Roland wrote:
> >> Ehle, Roland wrote:
> >>     
> >>> Hi all,
> >>>
> >>> I use "Use TNEF Contents = replace" and "Deliver Unparsable TNEF =
> >>>       
> >> no"
> >>     
> >>> to get rid of the winmail.dat grab from Outlook clients 
> using Outlook
> >>> Richtext Format.
> >>>
> >>> It was brought to my attention, that this setting causes long
> >>> filenames to be shortened: For example a file named "test 
> datei mit
> >>> sehr sehr langem dateinamen und viel bla bla.txt.txt" arrives as
> >>>       
> >> "test
> >>     
> >>> datei mit.txt" at the recipients mailbox.
> >>>
> >>> If I leave TNEF contents untouched, the filename is not changed.
> >>>
> >>> The above happens when using external TNEF decoder and 
> the internal
> >>> one. Same behavior with both.
> >>>
> >>> Has somebody experienced the same problem? Any hints to avoid the
> >>> problem, other than sending files with long filenames 
> inside a ZIP-
> >>>       
> >> file?
> >>     
> >> Do you mean a ZIP file or a TNEF file?
> >>     
> >
> > The problem is TNEF.
> >
> > Roland
> >   
> Well I have found it, but I'm a bit reluctant to change it:
> 
>           $safename = $message->MakeNameSafe($_->longname, $dir);
>           push @replacements, $safename;
>           #print STDERR "Safe name is \"$safename\"\n";
>           $message->{entity}->attach(Type => 
> "application/octet-stream",
>                                      Encoding => "base64",
>                                      Disposition => "attachment",
>                                      Filename => $safename,
>                                      Path => $filename);
> 
> Putting a dangerous filename back in the e-mail is a bit dodgy from a 
> security point of view. But I could change
>                                      Filename => $safename,
> to
>                                      Filename => $_->longname,
> which should fix it.
> 
> What does anyone think?
> 
> Jules
> 
> - -- 
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
> 
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
> 
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Desktop 9.7.0 (Build 1012)
> Comment: (pgp-secured)
> Charset: ISO-8859-1
> 
> wj8DBQFHoZbSEfZZRxQVtlQRAg5+AKD8vJsRt/9b7S9fvEhzg9a+NZUJ8gCggsHH
> bFlYbE2iksE60j3MLwJOGcI=
> =iEBo
> -----END PGP SIGNATURE-----
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
> 
> Before posting, read http://wiki.mailscanner.info/posting
> 
> Support MailScanner development - buy the book off the website! 
>