On 9 Jun 2003 Justin Mason ([EMAIL PROTECTED]) wrote: > Matt Kettler said: > > > Unless your MTA inserts header which tell who the actual > > recipient is, SA has no way of knowing and must rely on what > > is available in the headers. This makes the all_spam_to > > configuration a bit of a kludge because it's not completely > > effective, but it's the best that SA itself can do given what > > access it has to the message. > > Our all_spam_to, etc. black/whitelisting code will check the following > headers, since about SpamAssassin v2.40: > > X-Envelope-From: for the MAIL FROM: SMTP command > X-Envelope-To: for the RCPT TO: SMTP command > > Some MTAs already create those headers, which is why they're already > supported. If an MTA plugin adds these headers, it will allow > white/blacklisting to work correctly with the SMTP data.
You might also want to set up SA to look for Delivered-To: X-Delivered-To: Envelope-To: X-Original-To: X-Rcpt-To: X-Real-To: Each of these is used by some MTA somewhere to record the original envelope recipient. I'm keeping track of which MTAs and which ISPs use which headers in my Procmail Quick Start in this section <http://www.ii.com/internet/robots/procmail/qs/#envelope> Feedback and suggestions are welcome. Nancy PS - Thanks for SA! -- Nancy McGough <http://www.ii.com> Infinite Ink Writing about procmail, imap, pine, spam-deflexion strategies & more ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
