Timo Sirainen wrote:
On Sat, 2009-10-17 at 22:41 +0200, Andrzej Adam Filip wrote:
Would it be sensible/"cost effective" to make dovecot-deliver generated X-Delivered-To header(s) based on command line parameter(s)? [after striping such existing headers, before consulting sieve]
How exactly would that work?
By specifying content of the header(s) via command line parameter(s)
e.g. deliver -d userx -x userx@gmail.com X-Delivered-To: userx@gmail.com deliver -d userx -x userx@yahoo.com X-Delivered-To: userx@yahoo.com.com deliver -d userx -x user1@example.net -x user2@example.net X-Delivered-To: user1@example.net X-Delivered-To: user2@example.net
How is X-Delivered-To different from Delivered-To header?
As I understand Delivered-to header is generated by some MTA (postfix). I would like to make it a) available (via dovecot's command line) to other MTAs (e.g. sendmail) especially when message delivery to specific mailbox is generated by multiple "RCPT TO:" b) available to "MTA-less" configuration e.g. fetchmail calling directly dovecot's deliver (via --mda option)
Do you mean there would be another parameter specifying what its content is?
It would be the best solution from my perspective.
Somehow this sounds more like MTA's job (and perhaps LMTP server's job, so I might need to do that anyway there).
As I wrote I would like to get the functionality even in "MTA-less" configurations.