New Year's Resolution and new beta release

Julian Field MailScanner at ecs.soton.ac.uk
Fri Jan 5 12:19:31 CET 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



David Lee wrote:
> On Thu, 4 Jan 2007, Julian Field wrote:
>
>   
>> [...]
>> My New Year's Resolution is to try to spend more time doing MailScanner
>> support. For the last 6 months I have only had time to check my
>> mailscanner at ecs.soton.ac.uk address, not the mailing lists at all.
>>
>> [...]
>> Secondly, I have just released a new Beta version. This is 4.58.4.
>>
>> [...]
>> I intend to release a new Stable version very soon, hopefully in the
>> next week or so. Please do test the new {Fraud?} tag code and give the
>> whole thing a good run on any test hosts you may have available.
>> [...]
>>     
>
> Julian: Just before Christmas there was a thread about checking return
> codes from system calls.  The consensus seemed to be that MS had the
> balance about right: checking those that were likely to fail, but not
> being too paranoid about those that were either extremely unlikely or had
> not occured in anyone's real experience.  That's fine with me.
>
> But (hah! there's always a "but" isn't there?)...
>
> Could you check, please, the report from November:
>    http://lists.mailscanner.info/pipermail/mailscanner/2006-November/067706.html
>
> which is part of thread:
>    http://lists.mailscanner.info/pipermail/mailscanner/2006-November/067415.html
>
> This is (presumably) rare for others, but it has been, and still is, real
> for us. That is, it falls into the "occurs in real experience" category.
> (I'm surviving by using a suboptimal fudge around the problem.)
>
>
> Brief summary: "MailScanner/SA.pm" does a fork()/exec() to SpamAssassin.
> If, for some reason, that SA crashes then the parent (MS) process seems
> not to detect this, and treats it as a good, 'ham' result.  (I give
> possible suggestions in that November email.)
>   
And therefore it is failing 'safe'. Why wouldn't you want it to fail 
safe? Failure resulting in message delivery sounds a whole lot better 
than failure resulting in message disposal.

> Hope you are able to look into this.  I would be happy to try to beta-test
> your fix.  Thanks.
>
> Best wishes.
>
>
>   

Jules

- -- 
Julian Field MEng CITP
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.5.2 (Build 4075)
Comment: (pgp-secured)
Charset: ISO-8859-1

wj8DBQFFnjS/EfZZRxQVtlQRAukaAJ9uMmWeO6XQkuNtwe8k7zODPEr6jQCcCvqS
/Kl7uRgyQZumvo+9Hab19/4=
=iIXc
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk



More information about the MailScanner mailing list