You have some other rule in your spamdyke config that's marked the
message as ALLOWED before the sender blacklist or IP blacklists get
applied, would be my guess.
For example, if the sender matches a sender-whitelist entry, then
sender-blacklist won't be applied and the message will be ALLOWED.
Seeing your entire spamdyke config will be useful to see what's going on.
On 6/13/11 4:00 PM, [email protected] wrote:
Jun 13 10:06:19 echo spamdyke[25509]: ALLOWED from:
[email protected] <mailto:[email protected]> to:
[email protected] <mailto:[email protected]> origin_ip: 64.40.119.232
origin_rdns: mta232.reply.newsmax.com auth: (unknown) encryption: (none)
--
Dossy Shiobara | "He realized the fastest way to change
[email protected] | is to laugh at your own folly -- then you
http://panoptic.com/ | can let go and quickly move on." (p. 70)
* WordPress * jQuery * MySQL * Security * Business Continuity *
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
