[AMaViS-user] apology for bounced mail.
I do apologize for any annoyance based on e-mail rejection, we temporarily lost service and out ISP attempted to redirect mail to a holding que but got the domain names to IP mapping wrong so mail was bounced. Service has been restored. -- Dale --- 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 AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] SQL 'content' field explanation
On 8/31/05, Mark Martinec [EMAIL PROTECTED] wrote: Perhaps there should be two flags to reflect each of the kill / tag2 levels. I do not think that is necessary. The idea behind the current choice is the same as for quarantining: - if mail is not delivered, it goes to quarantine and content becomes 'S'; - if the mail _was_ delivered (tagged or not), recipient can do with it whatever he pleases, but as far as central content filtering is concerned, the mail was not treated as spam and not held. If the score was between tag2 and kill levels, I feel the content type should be 'S'. You do not lose any information from this, because if it was quarantined, the quar_type field would not be NULL. Actually with this setup you could never tell if the score passed the kill level if there was no quarantining in place at all, but I think that this is a better tradeoff. For statistical purposes it is perhaps better to deal with score levels directly. But this can be misleading when recipients have different SA levels. Depending on what kind of statistical information you needed. --- 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 AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] Courier patch: misplaced lines
There are two misplaced lines in the Courier patch with amavisd-new 2.3.3, neither of which has any effect on the functionality. First, use IO::Select; which should be at the top of the Amavis package ends up at line 5946 in the middle of the msg_from_quarantine function. This does not result in any errors because use is processed at compile time, and Amavis::Notify is always compiled. Secondly no ### Net::Server hook comment is placed before run_configure_hook, instead there is a double comment before pre_loop_hook. This is of course purely cosmetic. -- Martin Orr --- 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 AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
