Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] running oder of and

2004-07-12 by C.S.Chen

manu@... wrote:

>C.S.Chen <cschen@...> wrote:
>  
>
>>I wonder if there are obvious differences in performance (and others, if
>>any) on the issue of the
>>running order of <milter-regex> and <milter-greylist> with sendmail. 
>>--That is, if there are difference between the following two 
>>configuration  sendmail options:  (sendmail.cf)
>>    
>>
>
>milter-greylist will reject at the RCPT stage. If you use milter-regex
>as a content filter, order makes no difference, because milter-greylist
>will always has done his job when milter-regex will check the DATA
>stage.
>

So, do you mean that <milter-regex> and <milter-greylist> runs 
concurrently instead of sequentially ?

> O InputMailFilters=milter-regex,greylist,clamav,spamc

However, in the above configuration, as I observed from some system log 
excerpt, since a connection had been rejected by
<milter-regex>, the  <spamass-milter> (or spamc )  seemed to receive the 
same connection with NULL content (because it is
rejected by milter-regex in the first phase).

=======================================================================================
Jul 12 09:44:24 ns2 milter-regex[14311]: 218.164.157.97: 
cb_connect('218-164-157-97.dynamic.hinet.net', '218.164.157.97')
Jul 12 09:44:24 ns2 milter-regex[14311]: 218.164.157.97: REJECT: 
Rejected, SPAM from TwIspBL (Ra-1); any problem, call +886-3-
5731721 !, From: , To: , Subject:
Jul 12 09:44:24 ns2 milter-regex[14311]: 218.164.157.97: cb_close()
Jul 12 09:44:24 ns2 spamass-milter[216]: NULL context in mlfi_close! 
Should not happen!
Jul 12 09:44:24 ns2 sm-mta[42921]: i6C1iOwL042921: Milter: connect: 
host=218-164-157-97.dynamic.hinet.net, addr=218.164.157.97
, rejecting commands
======================================================================================

-cschen

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.