(When I add back in "x-originating-ip", I lose ALL_TRUSTED, which would
be expected if you
treat it like a Received: header.)
On 10/02, Mabry Tyson wrote:
One user complained about a false positive. When I examined the mail,
there appeared to be at least two rules that didn
One user complained about a false positive. When I examined the mail,
there appeared to be at least two rules that didn't work as I thought
they should because of a Received line in which IPv6 Link Local
addresses were used. It appears that a patch was previously put in
that was thought to f
We keep occasionally (once a day or two) hitting an infinite loop in
spamd 3.1.0 where the process fails to terminate. We find that after a
while some resource is used up and the system stops accepting new spamd
connections. The process accumulates run time, but is not running at
100% of th
ers for their
display names, I looked only at the mail that had display names for my
email address. "Standard display name" means the display name(s) that I
use on outgoing mail. Non-standard display name means anything else
where a display name is given. So, as you see by this mail, my
(We use SA (currently 2.64) called from procmail-delivered sendmail on
Solaris systems. We get something over 100K msgs/day. Most of our mail
is addressed using @ our local domain.)
Three suggested rules:
1) Detect mail allegedly from a local address that is invalid
(should get a high s