If you look at the man page for spamassassin config, in the section that talks
about the 'whitelist_to' statement, it lists the headers that SA examines when
processing the addresses to white-list. That list of headers includes the
"Delivered-To" header.
So that -should- work, assuming your qmail passes that header into SA.
If it only adds that header at final delivery time then SA may never get a
chance to see it. (that "glue" thing I was talking about; IE how SA is hooked
into your mail system).
This is sounding more like a qmailtoaster issue, you might be better served
going to a qmail list or what ever support community exists for qmailtoaster.
On Wed, 11 Feb 2015, Rajesh M wrote:
hi
i am using qmailtoaster
when the emails are sent to specified recepients via bcc then there is a header
Delivered-To created which i tried to use to check
however spamassassin does not seem to check Delivered-To header
what could be the problem ?
rajesh
----- Original Message -----
From: David B Funk [mailto:dbf...@engineering.uiowa.edu]
To: users@spamassassin.apache.org
Sent: Tue, 10 Feb 2015 17:17:32 -0600 (CST)
Subject: Re: rule for restricting incoming email
On Tue, 10 Feb 2015, Benny Pedersen wrote:
Antony Stone skrev den 2015-02-10 21:33:
What happens to an email from u...@abc.com, sent to someone other than
u...@recipient.example.com? Won't that then be whitelisted, even though
whoever it's addressed to hasn't asked for that (only user@recipient asked
for
this treatment)?
yes add all recipient to blacklist_to, missing that will be whitelist, but
only from whiteliste_from senders
Also, does "blacklist_to u...@recipient.example.org" match on emails where
u...@recipient.example.org is only a BCC address?
spamassassin does not see bcc anyway imho
A "BCC"ed recipient doesn't show up in a 'To/Cc' header (the whole point
of 'Bcc') but obviously must be listed in the envelope recipient list.
(assuming the "glue" your using in your system exposes that info to SA).
The blacklist_to/whitelist_to will work on the envelope recipient list
so (assuming your "glue" is right) Bcc shouldn't be a problem.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
