Just curious... I have all these Outlook users who claim they need "TNEF"
files to not be blocked anymore, does clamav directly un-encode them for
scanning, or do I need to get a perl module or external executable?
Ask your Outlook users what they think the TNEF attachments do, because AFAIK, the only thing it's good for is distributing information they never intended to send.
Afaik, Exchange will use TNEF format to send all files between Exchange servers (i.e., Exchange Server A TNEF-encodes any and all attachments when sending to Exchange Server B). Think of it as MS's replacement for MIME, since they can't be bothered to use anyone else's standard.
I have seen situations where Exchange mistakenly believes the receiving server is also Exchange and sends the attachments TNEF-formatted. See http://sourceforge.net/projects/tnef/ for a TNEF extractor if this happens to you. I don't know if Outlook itself can decode TNEF, but I would think so (haven't checked!), so I suspect it would also be possible to deliver a payload TNEF-encoded.
best, Jeff
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users