anomy-list

Fw: Strange problem with tnet2multipart.

From: list (88932@xyz.molar.is)
Date: Tue 22 Jul 2003 - 20:48:31 GMT

  • Next message: Leandro Rodrigo Saad Cruz: "[BEST PRACTICES] Using more than one policy"

     Thank you logging helped a lot.
     The main problem turned out to be a corrupted winmail.dat file.
    > ----- Original Message -----
    > From: "Derrick Webber" <89015@xyz.molar.is>
    > To: "list" <88932@xyz.molar.is>
    > Cc: <88965@xyz.molar.is>
    > Sent: Tuesday, July 22, 2003 2:32 AM
    > Subject: Re: [anomy-list]: Strange problem with tnet2multipart.
    >
    >
    > > list wrote:
    > >
    > > > System Suse 7.2 perl 5.6 anomy 1.63 tnef2multipart 0.3.
    > > > I have set up a system as desribed by Advosys with postfix spamassasin
    > and
    > > > above mentioned components.
    > > > In tnef2multipart it is stated that:
    > > > file_list_1 = (?i)(winmail.dat)
    > > > file_list_2_policy = accept:drop:drop:drop
    > > > file_list_2_scanner = 0:::/usr/local/bin/tnef2multipart.pl %FILENAME
    > > >
    > > > I belive that the first line in a typo so i changed it to:
    > > > file_list_2 = (?i)(winmail.dat)
    > > > file_list_2_policy = accept:drop:drop:drop
    > > > file_list_2_scanner = 0:::/usr/local/bin/tnef2multipart.pl %FILENAME
    > >
    > > Thanks for pointing out the typo. We fixed it.
    > >
    > > > Anyway:
    > > > When i call tnet2multipart from the commandline with winmail.dat a
    > resonable
    > > > output is produced.
    > > >
    > > > BUT when it is called via the sanitizer (incoming mail) it somehow
    dies.
    > All
    > > > I can see in the error log is a exitcode of 65280,
    > > > I have traced the problem to that tnef2multipart is called OK but it
    > dies
    > > > silently somewhere in the TNEF::Convert.
    > > > Besides that I am out of clues.
    > > >
    > >
    > > An exit code of 65280 sounds like something returned by a system()
    > > call... ie. the open() call in tnef2multipart that re-injects the output
    > > back into the sanitizer. Perhaps a file permission problem?
    > >
    > > It's difficult to debug external scanners in Anomy as it seems to always
    > > throw away the standard error of the scanner program. Unless the scanner
    > > has the ability to log to a file, it seems you have to guess.
    > >
    > > So to make tnef2multipart easier to debug, we've added an option to log
    > > errors to a file. Hopefully this will let you see exactly what's
    > > happening on your system.
    > >
    > > Version 0.04 is now available at
    > > http://advosys.ca/papers/filter-misc/tnef2multipart.pl Uncomment line
    > > 55 to turn on the logging.
    > >
    > > --
    > > Derrick Webber 89015@xyz.molar.is
    > > Advosys Consulting Inc. Ottawa
    > > http://advosys.ca/
    > > --
    > >
    > >
    >



    hosted by molar.is