On Tue, May 28, 2002 at 10:52:08PM -0700, Harry Putnam wrote: | [Cross post alert... This should have been posted on `talk' | I had my wires crossed for a few posts which will no be posted to | `talk'] [only replying on -talk] | Come within a hairs breadth of giving full details of what will work | with whitelist_from but then leaves a lot of room for doubts. | | Even down to how to list more than one. Are they supposed to be | whitespace separated or comma separated, or something else?
The default config file has some examples. Also look at
/etc/spamassassin/60_whitelist.cf (you're using debian, right?).
| The actual `From: ' line looks like:
|
| From: root (Cron Daemon)
That's missing the address part. It should look like eg :
From: [EMAIL PROTECTED] (Cron Daemon)
Oh, I think I see two bugs! The first bug is in your (Harry) MTA
config. It should be qualifying the unqualified address so that the
actual header is
From: [EMAIL PROTECTED] (Cron Daemon)
(though it is recommended to use one of the top-level domains in RFC 2606)
The other bug is in SA. IIRC it only properly parses
[real-name] <[address]>
addresses and not
[address] ([real name])
If I'm right on that, then you can't whitelist an address of that
format. I may be wrong, though, and SA might handle that format
correctly now.
| Can it be white listed? Or maybe there is some other way to force a
| message to be accepted.
In any event you can use a custom rule like this :
header CRON From =~ /^root \(Cron Daemon\)/
score CRON -100
-D
--
He who finds a wife finds what is good
and receives favor from the Lord.
Proverbs 18:22
GnuPG key : http://dman.ddts.net/~dman/public_key.gpg
msg05543/pgp00000.pgp
Description: PGP signature
