On 6/23/06, Daryl C. W. O'Shea <[EMAIL PROTECTED]> wrote:
Well you could s/address/address pattern/.
I could, but plainly what I did was s/used in/used in processing/,
because it seemed a whole lot more intuitive for it to function that
way. Ah, well.
This will probably change in a future v
On 6/23/2006 11:54 PM, Bart Schaefer wrote:
On 6/23/06, Daryl C. W. O'Shea <[EMAIL PROTECTED]> wrote:
Did you read the Mail::SpamAssassin::Conf perldoc?
Yes ... so what you're saying is, "previously used in" means "written
in the config file entry" not "used in spamassassin when matching".
T
On 6/23/06, Daryl C. W. O'Shea <[EMAIL PROTECTED]> wrote:
Did you read the Mail::SpamAssassin::Conf perldoc?
Yes ... so what you're saying is, "previously used in" means "written
in the config file entry" not "used in spamassassin when matching".
The phrase "the address" is what threw me; the s
On 6/23/2006 10:24 PM, Bart Schaefer wrote:
The short of it is that I can't get unwhitelist_from_rcvd to
unwhitelist anything.
whitelist_from_rcvd [EMAIL PROTECTED] brasslantern.com
unwhitelist_from_rcvd [EMAIL PROTECTED] brasslantern.com
but this does not change anything. In fact I've tr
The short of it is that I can't get unwhitelist_from_rcvd to
unwhitelist anything.
Here's the situation: We have a brand-new machine that's going to be
swapped in as our mail server. We're trying to test everything
thoroughly before we switch over to it. To avoid any loss of mail, I
have a tes
