Justin, > OK, I think that makes sense. So the idea is this: > > The email comes in fom submitter, and since the list domain is local, > it's scanned
It is scanned regardless of domain being local. Locality only affects adding X-Spam-* mail header fields. > and headers are put in If you want. These headers are probably not of much use to be propagated to mailing list members, which probably only want to believe spam checks run on their own site (assuming the mailing list fans out to remote users). So keep tag level high or undef, and keep tag2 level the same as kill level (for the mailing list). > then whether it's spam_lovers or not will determine if it's deleted or not Exactly. > (There should be no quarantine I don't want the quarantine message > going to the list!) Quarantining is completely independent of delivery, one does not affect the other. And quarantining does not propagate to recipients. So enable or disable quarantining spam for a mailing list as you wish, it will only affect you as administrator (stores junk to local disk and keeps your conscience clean in case of a query), but does not affect recipients. > Once it's scanned, if it passes those checks AND passes mailman's checks > for subscription rules, it's submitted to the list members on port 10025 > and processed by postfix, but not re-scanned. i.e. once it reaches that > point, the mail will be delivered. Right. Mark ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
