dovecot - Oct 2009 - Wish-list: X-Delivered-To headers generated by dovecot-deliver

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]

I need it to:
a) *clearly* mark POP/IMAP account fetched by fetchmail
   [with fetchmail using directly dovecot-deliver in --mda option]
b) cleanly implement "shared mailboxes" with MTA such as sendmail
   that can be easily forced to generate "one header per one
recipient"
   [AFAIK]

-- 
[pl>en: Andrew] Andrzej Adam Filip : anfi at onet.eu
Order and simplification are the first steps toward mastery of a subject
-- the actual enemy is the unknown.
  -- Thomas Mann

On Sat, 2009-10-17 at 22:41 +0200, Andrzej Adam Filip
wrote:
> a) *clearly* mark POP/IMAP account fetched by fetchmail
>    [with fetchmail using directly dovecot-deliver in --mda option]
Would the fetchmail tracepolls option not do? It generates a header like
this, including local and remote account info.

  Received: from mail.example.net [192.0.0.1] by local-server with POP3
   (fetchmail-6.3.4 polling mail.example.net account user) for
   <local-user at localhost> (single-drop); Sat, 17 Oct 2009 22:42:27
+0200 (CEST)


-- 
char *t="\10pse\0r\0dtu\0. at
ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8?
c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){
putchar(t[s]);h=m;s=0; }}}

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? How is X-Delivered-To different from
Delivered-To header? Do you mean there would be another parameter
specifying what its content is?

Somehow this sounds more like MTA's job (and perhaps LMTP server's job,
so I might need to do that anyway there).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20091027/4d4c0a02/attachment-0002.bin>

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 at gmail.com
  X-Delivered-To: userx at gmail.com
deliver -d userx -x userx at yahoo.com
  X-Delivered-To: userx at yahoo.com.com
deliver -d userx -x user1 at example.net -x user2 at example.net
  X-Delivered-To: user1 at example.net
  X-Delivered-To: user2 at 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.