Re: [AMaViS-user] SMTP: NOTICE client broke the connection without a QUIT

[Jeffrey T. <jef...@ie...>]

Quoting IEEE alias <jef...@ie...>:
> Quoting Mark Martinec <Mar...@ij...>:
> > Jeffrey,
> > 
> > | After installing amavisd-new-20021227, I started seeing the above
> > | warning when running "amavisd debug".  The mail is getting thru, but
> > | warnings make me uncomfortable.
> > 
> > What was the previous version of amavisd-new? 
> > There should be not difference to amavisd-new-20021116
> > in this respect, but earlier versions did not issue this warning.
> > 
> 
> I skipped a version (or 2).  I was using the 20020517 version.
> 
> > | It appear with the majority of
> > | messages, but not all.  This is with Postfix 1.1.11, using amavis as
> > | content_filter.
> > |   This also happens when I feel amavisd's SMTP-IN port directly with
> > | the SMTP output of another Postfix or the SMTP-OUT of an amavisd-new
> > | instance running on the firewall box.
> > | Anyone else seeing this?
> > 
> > I have been seing this with some versions and configurations of
> > SpamAssassin, and this is also the reason why I added the warning
> > log entry. Since SpamAssassin runs in the same process as the rest
> > of the amavisd-new, including the SMTP protocol code, there is
> > no good protection from unwanted side effects of SpamAssassin.
> > If one of its tests would close STDIN or STDOUT, this would
> > result in shutting down the SMTP session, and result in a warning.
> > 
> > Try with SpamAssassin 2.50, and if still seing warnings about
> > broken SMTP sessions, try disabling external SA tests,
> > first all of them ($sa_local_tests_only = 1), next perhaps
> > one by one, such as Razor2.
> 
> I'll try these and post what I find.
> 

Setting $sa_local_tests_only = 1 fixes the problem.  I'll upgrade SA
next year.

Jeffrey