This might be a MTA question, but because I use Dovecot as an LDA, maybe
some can help me here.
Our users would like that outgoing mail is automatically saved in some
folder, say Sent. We use Postfix with virtual domains, Maildir and
Dovecot+Sieve as LDA. Outgoing mail is relayed by our imap-server (with
authentification of course, no open relay).
Most people seem to advice Postfix sender_bcc_maps and Dovecot's deliver
with the -m argument. But I can't get it work. I tried:
In master.cf:
dovecot-archive unix - n n - - pipe
flags=DRhu user=mailowner:mailowner argv=/usr/libexec/dovecot/deliver -d
${recipient} -m Sent
In main.cf:
sender_bcc_maps = hash:/etc/postfix/sender_bcc_map
In sender_bcc_map:
tester at ruijs.cc dovecot-archive:
But that doesn't work. It looks like "dovecot-archive:" should be
a real
email address, not a transport (this give an idea of my Postfix knowledge
;). Then I tried:
In sender_bcc_map:
tester at ruijs.cc tester+archive at ruijs.cc
But I don't think Dovecot's LDA supports plus addressing.
So my question is, has anyone here done a similar thing in a similar
setting. If so, how did you configure it.
Thans,
Mark
Oudenhof 14b, 4191 NW Geldermalsen, The Netherlands
Web site and travel directions: www.in2sports.net
Phone +31.345.473699 :: Mobile +31.6.51298623
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://dovecot.org/pipermail/dovecot/attachments/20061107/676aa49a/attachment.htm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 7 Nov 2006, Mark Ruys wrote:> Our users would like that outgoing mail is automatically saved in some > folder, say Sent.Hmm, any IMAP mail client I know has an option for exactly that feature. I don't know postfix. I would look into the line: Variant I a) MTA adds envelope sender (aka MAIL FROM) to envelope recipient list (aka RCPT TO, aka BCC). b) LDA delivers mail into Archive folder if the sender is the owner of the mailbox. Variant II as variant I, but adds an Header that helps the LDA to decide, if the mail has been sent by one particular user, e.g. the MD5 hash of the SMTP AUTH uid. Variant III a) MTA always adds a robot to the envelop recipient list. b) This robot spools the mail according the From: header of the mail or yet another piece of information you can most likely aquire the sender from, e.g. authentification data. E.g. match the message ID or queue ID with the logs of the MTA. Of course, in all these cases you need to decide beforehand, if the mail is inbound or outbound. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iQEVAwUBRVB19i9SORjhbDpvAQKQAwf9HoMeq2CDNbhOlx79HCpaHT6/sjb1Fjg8 iq2EPzDIDTpcwqsyucmwI5Ib6y8PPABv4B4E38TusqCLt211ZmdPGbl6HxP5/sTb fAUPy9zGr1rJu92AdELZKRhHDrM6YjNayr/nlKt5DNbto8o6Bs4LbIzybgJbGrYQ j3u3BUobxwLPA1EvSihCePp6H2vJEyjgVssdc0WSfh7ZTO6nID6PT5ZHYaifWLaz MFTv9c6x5V26A/s4i+EsbYGNrjVLkI3br8scstRvT2OcJsTfyOc3OwSNJxqia9wN vbe97b5WZPhgcOqgJhwTslcKfUKPL2xDHTQbTGsOk2gJKUHWvk7KQA==LSHW -----END PGP SIGNATURE-----