I'll try the double-spamdyke trick to see if that works for me. Nice idea :-)
Having thought about it, other than for logging purposes, I don't absolutely 100% need filters AFTER authentication. I just need filters before authentication. e.g. IF (no rdns | is in blacklist | fails any other normal spamdyke filter) THEN block ELSE allow to attempt to authenticate. Obviously if it is done this way then there's no way to generate the special error message that would allow me to spot a compromised account (i.e. if sender fails filter AND fails to authenticate), and I admit that was an important part of what I was asking for. Sam said: > As for still enforcing filters after authentication happens... that's more > problematic. Beyond the coding required, I'm having trouble imagining what > the configuration file would look like. Specifying one filter is enabled before > authentication but not after, while another filter is enabled both before and > after will get very confusing and error-prone. My gut tells me this kind of > feature would be much more trouble than it's worth. _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
