Nate, Sounds like your goal is to have the downstream mailserver insert a message tagged for quarantining into an quarantine folder, say an IMAP accessible mailstore.
You can do this with amavis + postfix + dovecot by using address extensions instead of headers or subject modifications. So items for quarantining, spam tag2 & virus infected in this case get placed in a INBOX.quarantine folder in the recipient's mailstore. the effect is a message to be quarantined leaves the amavis/policy stage with rctp to userid+.quarant...@domain.tld below is some configuration snippets from a production system that does this, I'm just providing the key parameters for the three daemons to enable this. amavis, this is the syntax for a _policy bank_ that # do not block on content for this policy bank # virus_subject_tag2_maps only works if you have a patch that I posted to the list a few weeks ago, else you get the default [***INFECTED***] final_virus_destiny => D_PASS, # if you don't want infected quarantined, D_DISCARD spam_subject_tag2_maps => ["[**SPAM**] "], virus_subject_tag2_maps => ["[**VIRUS**] "], spam_quarantine_to_maps => [ ], defang_virus => 1, # I recommend this if you're going to quarantine virii addr_extension_virus_maps => [ ".quarantine" ], addr_extension_spam_maps => [ ".quarantine" ], postfix, at a downstream mailserver which delivers mail to a dovecot mailstore, master.cf # Dovecot LDA # - enable user+extens...@domain support, see http://wiki.dovecot.org/LDA/Postfix # - delivers mail to INBOX/extension folder, if "extension" namespace exists # - used to deliver quarantined mail to a given folder dovecot unix - n n - 128 pipe flags=DRhu user=mail:mail argv=/usr/libexec/dovecot/deliver -c /etc/dovecot/dovecot.conf -f ${sender} -d ${us...@${nexthop} -n -m INBOX${extension} postfix, part of main.cf to set the parameters for dovecot deliver and "+" address extension # mailbox control # - how to deliver to mailbox, see "dovecot" in /etc/posfix/master.cf # - don't use mailbox_command, that's only good for one domain # - dovecot does quota # - dovecot & postfix expecting "+" delimiter # - dovecot can only receive one destination recipient at a time # dovecot_destination_recipient_limit = 1 mailbox_size_limit = 0 recipient_delimiter = + dovecot 1.2.10, should have it autocreate the quarantine folder if it doesn't exist, dovecot.conf namespace private { separator = . prefix = INBOX. inbox = yes } protocol lda { mail_plugins = autocreate quota sieve } plugin { autocreate = INBOX.quarantine autosubscribe = INBOX.quarantine } Cheers, -Martin Foster Le 02-Apr-10 05:16, Mark Martinec a écrit : > Nate, > > >> Curious if anybody has accomplished the following and/or can give me >> any tips on how to accomplish. >> >> I would like to instead of amavis delivering quarantine to a SQL >> database (how we have it now), instead have it perhaps add a header: >> X-Quarantine: TRUE or something to that effect. Second choice would >> be to append the subject with [QUAR]. >> >> Our setup forwards to the mail servers once scanned, so then have the >> mail server (postfix) read the header or subject and automatically >> create if necessary, and then deposit into a Quarantine folder. >> >> Knowing amavis and postfix fairly well, I believe this is do'able. >> Before I go through the trouble of figuring it out, I'm wondering if >> somebody else already has? >> > If you give up the flexibility offered by independent controls > on quarantining, from passing/blocking/tagging of messages, > and tie quarantining action with message being blocked, you can > accomplish this with tag2 or tag3 modifications to a message > (Subject edits, 'plus' addressing, X-Spam* headers). > > Otherwise what you ask for is not possible without a hack in code. > But think of / explain a situation where a choice of quarantining > would not match a choice to tag/block a message. > > Mark > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > 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/ > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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/
