| |||||||||||||||||||||||||||||||
|
> On Wed January 16 2008, mouss wrote: >> Mihira Fernando wrote: >>> On Wed January 16 2008, mouss wrote: >>>> The following is untested. risk at your own use. >>>> >>>> always_bcc = bcc >>>> >>>> in transport maps: >>>> bcc.example.com copy2sent: >>>> >>>> in master.cf, define a copy2sent transport to deliver to the Sent folder >>>> of ${sender} (instead of the usual delivery to ${recipient}). for >>>> example: >>>> >>>> copy2sent - n n - - pipe >>>> flags=... user=... >>>> flags=... user=... argv=/path/to/maildrop >>>> -d ${sender} folder=Sent >>>> >>>> and in maildroprc, pickup the folder=Sent argument and append it to >>>> ${DEFAULT}. >>>> >>>> If ${sender} doesn't match your setup (for example, if users are stored >>>> without the @domain part), use a wrapper script. >>>> >>>> >>>> Note that this must be done for submitted mail, with SASL AUTH and >>>> sender login match. mail to @bcc.example.com must not be accepted >>>> otherwise. >>> Thanks, I'll give this a try. >> in fact, sender_bcc_maps (with pcre) is better > > Noted. > Actually I was planning to try your suggestion with sender_bcc_maps rather > than always_bcc > > One more question, in my setup I'm using Dovecot LDA for mail delivary rather > than maildrop. I have the following in master.cf > > dovecot unix - n n - - pipe > flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient} > > > Can I use the '-d ${sender} folder=Sent' with dovecot or is it time to RTF > Dovecot M ? > no, the folder=sent thing isn't support by any MDA, but you can parse arguments in maildroprc. with dovecot, you can use the -m argument. if you use sieve, you need to make sure it doesn't get in the way. you may use -c and use a different config. An alternative is to put the info into the sender_bcc_maps result. For example: /(.*)@(example\.com)$/ $1+sent@$2 then let your user map return the Sent folder as the mailbox for foo+sent... etc.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com