What is the purpose of the NO_MX_FOR_FROM test? It can check for a forged from, true... but wouldn't it make as much (or more) sense to test the envelope sender for MX, since that's where bounces might go?
Also, shouldn't the check fallback to checking for an A record if an MX doesn't exist? For example, there isn't an MX for bluevelvet.ais.cx, but its A record is the appropriate mail server for that domain... Unless there is some overwhelming reason not to do this, I will add check_for_envsender_mx() and make that and check_for_from_mx() fallback to an A record. Thanks, /pg -- Peter Green : Architekton Internet Services, LLC : [EMAIL PROTECTED] ------------------------------------------------------------- "I've decided I don't want to be a manager. Every time you try to be responsive to your employees, they say you're being reactive and not proactive. And when you try to be proactive, they accuse you of being capricious and arbitrary. So I don't wanna be a manager... " --- Larry Wall _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
