I *think* this idea should work the way I intend, but it's not likely a usage that was envisioned when flushaddr was added, so I figured I'd ping the list before trying it out in production. At my site, there are certain email addresses that act as spamtraps. Mail to these addresses are automatically forwarded into my bayes training, and I later review them for mistakes. (Thus far, there have been none, and I've had this in place for 2 years. The addresses chosen were picked very carefully and were monitored extensively prior to use, and continue to be monitored.) In any event, I very much want to receive email sent to these addresses quickly, as it gives my bayes DB a "leg up" on the freshest spam. However, I know with a very high degree of certainty that any IP emailing one of these addresses is spamming. As such, I'd like to flush out any existing greylist/autowhite entries for any site that emails a spamtrap. This winds up, for all other users, effectively blacklisting any sites that consistently email my spamtraps, as their greylist entries will keep getting purged. So, should this wind up working? Assuming of course the sender keeps "carpet bombing" batches of valid users, mixed in with spamtraps? racl whitelist rcpt /\<spamtrap@domainfragment/ flushaddr
Message
acl whitelist ... flushaddr
2007-07-09 by Matt Kettler
Attachments
- No local attachments were found for this message.