clamd and tnef error?

[Randal, Phil]

Unfortunately, we're not in control of the outside world, as much as
we'd like to be.

 

Phil

-- 
Phil Randal | Networks Engineer 
NHS Herefordshire & Herefordshire Council  | Deputy Chief Executive's
Office | I.C.T. Services Division 
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT 
Tel: 01432 260160 
email: prandal at herefordshire.gov.uk 

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

This e-mail and any attached files are confidential and intended solely
for the use of the addressee. This communication may contain material
protected by law from being passed on. If you are not the intended
recipient and have received this e-mail in error, you are advised that
any use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited. If you have received this e-mail in error please
contact the sender immediately and destroy all copies of it.

From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Martin
Hepworth
Sent: 14 September 2010 15:32
To: MailScanner discussion
Subject: Re: clamd and tnef error?

 

yeah  some sites need internal and others external expander, seems
totally random.

But as Steve says MIME/html email is the way to go then we get rid of
the silly winmail.dat anyway ;-) 

-- 
Martin Hepworth
Oxford, UK



On 14 September 2010 14:45, Steve Freegard <steve.freegard at fsl.com>
wrote:

On 14/09/10 14:13, Paul wrote:

I've switched to the internal tnef expander and there are no errors.

 

Small word of warning on the internal expander; Convert-TNEF hasn't been
updated in a very long time and I recently had a number of issues on
multiple sites where it was causing MailScanner to segfault on messages
generated by recent versions of Exchange.  This was causing MailScanner
to quarantine loads of messages as 'attempted to kill MailScanner' and
required a bit of cleanup to correct.

That said - I also had issues with the external expander a long time ago
which is why I switched to the internal as the preferred method.  But
the external expander is much more up-to-date and I doubt if these
problems are still present.

These days 'Expand TNEF = no' is my preferred method and get the
Exchange server to send messages in MIME format instead of working
around bad defaults on the Exchange side.

Regards,
Steve.


-- 
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! 

 

Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council monitors its email service.
This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100914/e3fea84d/attachment.html