[AMaViS-user] Per user prefs
Hi folks, I've a question about user preferences. What if a mail has multiple addressees? If they use different settings is it possible that some of them receives a potential spam while others do not? How tagging does work in this case? Each recipients get a different header with its own scores? Regards Gabor -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
Re: [AMaViS-user] Per user prefs
Gabor, I've a question about user preferences. What if a mail has multiple addressees? Each recipient is treated individually, according to their preferences. If they use different settings is it possible that some of them receives a potential spam while others do not? Yes. How tagging does work in this case? Each recipients get a different header with its own scores? Essentially yes, but the answer depends on what the question refers to. Since early days of supporting SpamAssassin from amavisd it was possible to configure several per-recipient settings which shape the outcome, individually for each recipient. Examples are kill_level, which allows some recipients to be more tolerant to spam score and receive spammy mail while other recipients of the same message may be blocked. Another example is tag2_level, which marks a message in its header either as spam or not, individually. Similarly, @spam_subject_tag_maps can specify individual string to be inserted into a Subject, according to a recipient or its domain. Or the addr_extension_maps. In all cases above, SpamAssassin is called only once per message, regardless of the number of recipients. Header edits and delivery decisions are then done for each recipient individually. If header edits differ among recipients of the same message, the message is forwarded to MTA as several messages, grouped into clusters by edits needed. Now in the 2.7.0, in addition to the above, it became possible to call SpamAssassin more than once per message. See description of settings @sa_userconf_maps and @sa_username_maps in the recent RELEASE_NOTES. Recipients of a message may specify individual SA user configuration files. If this happens, SpamAssassin is called once for each cluster of same-config-file and same-username (i.e. username for Bayes checks). This does not come cheap, you pay the price of saving current SpamAssassin settings and loading a new set, and calling it for each group - so use this sparingly, only if really necessary. Unlike the per-recipient @*_maps described above, which cost almost nothing (apart from substantial programming effort). Mark -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
Re: [AMaViS-user] Per user prefs
--On Wednesday, February 23, 2011 3:50 PM +0100 Mark Martinec mark.martinec+ama...@ijs.si wrote: Now in the 2.7.0, in addition to the above, it became possible to call SpamAssassin more than once per message. See description of settings @sa_userconf_maps and @sa_username_maps in the recent RELEASE_NOTES. Recipients of a message may specify individual SA user configuration files. If this happens, SpamAssassin is called once for each cluster of same-config-file and same-username (i.e. username for Bayes checks). This does not come cheap, you pay the price of saving current SpamAssassin settings and loading a new set, and calling it for each group - so use this sparingly, only if really necessary. Unlike the per-recipient @*_maps described above, which cost almost nothing (apart from substantial programming effort). Hi Mark, This sounds to be something very different than I ever desired. What we modified amavis for was adding an additional SA .cf file that applied to all users, i.e., an overall administrative policy if you will. This sounds more like something that allows users to adjust their configurations, which is quite different, and it sounds like it requires both @sa_username_maps and @sa_userconf_maps to be set for it to work. I just need to be able to say to use the additional .cf file for all mail, regardless of user. Is there a way to do that, or do I need to continue to patch amavisd for that functionality? --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
Re: [AMaViS-user] Per user prefs
Quanah, mark.martinec+ama...@ijs.si wrote: Now in the 2.7.0, in addition to the above, it became possible to call SpamAssassin more than once per message. See description of settings @sa_userconf_maps and @sa_username_maps in the recent RELEASE_NOTES. Recipients of a message may specify individual SA user configuration files. If this happens, SpamAssassin is called once for each cluster of same-config-file and same-username (i.e. username for Bayes checks). This does not come cheap, you pay the price of saving current SpamAssassin settings and loading a new set, and calling it for each group - so use this sparingly, only if really necessary. Unlike the per-recipient @*_maps described above, which cost almost nothing (apart from substantial programming effort). This sounds to be something very different than I ever desired. What we modified amavis for was adding an additional SA .cf file that applied to all users, i.e., an overall administrative policy if you will. This sounds more like something that allows users to adjust their configurations, which is quite different, and it sounds like it requires both @sa_username_maps and @sa_userconf_maps to be set for it to work. I just need to be able to say to use the additional .cf file for all mail, regardless of user. Is there a way to do that, or do I need to continue to patch amavisd for that functionality? I believe that just having a global @sa_userconf_maps seting with a fixed string (a 'constant'-type lookup table) achieves what you need: @sa_userconf_maps = ( '/etc/my_user_prefs.cf' ); If you do not change this setting by a policy bank and do not specify per-user lookup tables, there is no additional performance hit apart from the loading of the extra config file at the child process startup. I don't think this is unlike your suggestion, but I may be wrong. Please try it. Mark -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
