Pegasus Mail & Mercury

Hi allI am a bit confused about the 'S' command in the transaction rules.The rules explanation says: ''The 'S' action, however, exits from the current pass and suppresses all further transaction filtering on the message altogether.''I designed a filter wanting to target a specific sending smtp server, and took the following approach:H, ...

I'm still using v4.01b and would like to use spambust.dat to block IP ranges in received headers but can't get my head round the exact format of the rule I have to make.  If I use: if header''received'' contains ''118.*.*.*'' it will block any received header with 118 anywhere in it - what I want to do is block a received header that contains ...

I'm starting to see an increasing amount of spam get through where the MAIL FROM on the header is a valid local user (usually the same as the RCPT TO).  But the from address within the DATA portion is a different address.  Since the MAIL FROM is a valid local user, I cannot add it to the killfile.  Is it possible to reject these ...

Hi all, I may be wrong about it but: A field delimiter is never a part of the field.As by definition (RFC2821 - 2.3.7 Lines) the delimiter of any line or command in SMTP is CRLF the CRLF finishing any line should not be evaluated by transaction filtering. Besides the current status not being logical I guess many users did a ...

I created an updated version of this flowchart a few years ago that includes additions for transaction filtering, DNSBLs, and probably a few other things. The updated version can be found on my Wiki: http://email.arcm.com/wiki/index.php/MessageProcessingFlowChart Feel free to include a copy here, if you'd like.

Steps 1 through 5 are applied in real time as the message is being received by MercuryS. Failing any one of these checks results in the specified action being taken. The action could be a droped connection, message logged, etc. Check the Mercury/32 help files for more information regarding Transaction Filtering, as well as Michael Walsh's free ...