Scott, I have been experimenting with some spam headers that our gateway
servers (Linux/Postfix/RAV AntiVirus) can add to potential spam messages.
One of the following four message headers can be added to a message based on
spam accuracy (or no header if the messages in not suspected of being
the dns servers are 208.13.150.92 and 208.13.150.91 set in imail...
Those servers seem to be responding properly.
In this case, I would suggest using the debug mode. To use the debug mode,
you can change the LOGLEVEL LOW line in \IMail\Declude\global.cfg to
LOGLEVEL DEBUG. Then, after an
However, I have noticed that whenever these headers are added to an e-mail
message and tagged by the filter file, that none of the ip4r tests get run
on these messages...
X-Declude-Sender: [EMAIL PROTECTED] []
Here's the problem -- for some reason, Declude JunkMail thinks the IP is blank.
I've got declude set to 'warn' in order to give my clients full control of
what gets deleted. I am looking for some proven examples of Imail rules
that use the declude headers (various X-RBL-Warnings) to recommend
that they use.
Any ideas or recommendations?
Thanks,
---
[This E-mail was
Hi, Scott.
I don't use or send to anyone with MIMESweeper, but I thought I'd chime in
here, off the list, and submit a message I received this weekend. What is
unusual about it is that the header has all the X- entries before the date
entry. I haven't noted this before with Declude, and wish
