Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Subject: Re: Problems with BCCing from spammers
From: Karsten =?ISO-8859-1?Q?Br=E4ckelmann?= <guenther@rudersport.de>
To: users@spamassassin.apache.org
In-Reply-To: <520D076D.8060808@ipinc.net>
References: <520BC7AC.2080709@ipinc.net> <520BEFC8.5000602@gmail.com>
	 <520C02B5.8080404@ipinc.net> <520C7FBF.1010907@gmail.com>
	 <520D076D.8060808@ipinc.net>
Content-Type: text/plain
Date: Fri, 16 Aug 2013 03:22:24 +0200
Message-Id: <1376616144.4766.36.camel@monkey>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2013-08-15 at 09:53 -0700, Ted Mittelstaedt wrote:

> > it is *not* a bug. It's not SA's task to split a msg to multiple rcpts.
> > Your glue (hack) or MTA (best) should do this.
> 
> It IS a bug since the software is not acting according to how it's
> documented or expected.  That is the definition of a software bug.
> 
> You can argue that it's a documentation bug and I might agree but it's
> still a bug

See the M::SA::Conf [1] docs, option whitelist_to. The expected behavior
and headers considered are clearly listed.

Please show some evidence, that SA is acting in violation to its
documentation, and that none of the listed headers contain an address in
your whitelist_to / all_spam_to configuration.


> An option stating "all_spam_to" followed by the email address of the
                                                                   ^^^
> RECIPIENT is basically stating that ONLY mail sent TO the recipient will
> be exempted.

Let me re-emphasize that: "THE recipient". Who is "the" recipient of a
message with multiple recipients? At which point is it "the" recipient,
before or after local alias expansion?

Regardless, the whitelist_to option is not about THE recipient, but A
recipient. The first sentence of documentation shows this:

 "If the given address appears as a recipient in the message headers
  (Resent-To, To, Cc, obvious envelope recipient, etc.) the mail will be
  whitelisted."


> It would be better to have the option
> 
> "all_spam_to_envelope_recipient"

Patches accepted.

> with the explanation that the recipient is who is being passed on the 
> envelope To: not the To: in the header, or something like that, but
> the option as it stands implies the To: in the header, and that 
> implication should be disabused in the documentation for the config
> file, at the very least.

It only implies (referring exclusively to) the To header, if one fails
to read the documentation -- absolutely clearly listing 12 headers.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}