/dev/rob0 a écrit : > On Sunday 04 October 2009 15:57:30 mouss wrote: >> /dev/rob0 a écrit : >>> On Sunday 04 October 2009 11:24:31 [email protected] wrote: >>>> Another subject of consultation, I have implemented bogofilter in >>>> my work, I have been trained according to the documentation at >>>> this point that the messages marked as SPAM and HAM, the second >>>> step would be to take a decision to the marked messages. >>>> >>>> How could move messages marked as spam that are coming, be moved >>>> to a folder called SPAM on every mailbox? >>>> >>>> I use Postfix + MailScanner + Bogofilter + Dovecot >>> FWIW, I prefer the amavisd-new approach to this. The username (LHS of >>> the email address) has "+spam" appended when reinjected. Then your >>> ~/.forward+spam (for local(8) delivery, or user+s...@domain listings >>> in $virtual_mailbox_maps for virtual(8)) controls where the spam is >>> delivered. >> works too, but requires "some" care. in particular, if one has many >> levels of virtual aliases (one can expand aliases before amavisd-new, >> but I prefer passing the original address to the filter...). >> >> for example, a virtual alias entry like: >> [email protected] [email protected] >> would apply to [email protected] (thus losing the +spam part) >> unless he has a corresponding virtual alias. > > http://www.postfix.org/postconf.5.html#propagate_unmatched_extensions > might cover the issue that you describe. :)
this might help a bit, but not enough to. the real problem is that of recursive alias expansion. if it's about foo -> bar -> tagada, then it's ok. but if you mix this with foo+blah and other variants, then you need to be careful when which alias is expanded. and when it comes to folder selection, it's better/easier to make this happen outside of alias expansion and postfix routing. I've played with virtual_mailbox in the past, and it was easy with mysql. but I stopped using this. I find it easier to let the folder selection part be completely sepearate from (postfix) routing.
