dovecot - Jul 2014 - Differences in "Delivered-To" header between deliver and LMTP

Hi,
I'm transitioning my server over from using the deliver LDA and LMTP.  
Suddenly a bunch of sieve filters stopped working, and I noticed the 
contents of the Delivered-To header are different.

Using Dovecot's deliver LDA, the contents are a bare email address 
(foo at bar.com).  Using Dovecot LMTP, they are in brackets 
(<foo at bar.com>).  Is there a reason why this isn't consistent
between
the two delivery agents?  It seems like it ought to be.

Jeff

Am 09.07.2014 20:20, schrieb Jeff Rice:
> I'm transitioning my server over from using the deliver LDA and LMTP. 
Suddenly a bunch of sieve filters stopped
> working, and I noticed the contents of the Delivered-To header are
different.
> 
> Using Dovecot's deliver LDA, the contents are a bare email address (foo
at bar.com).  Using Dovecot LMTP, they are in
> brackets (<foo at bar.com>).  Is there a reason why this isn't
consistent between the two delivery agents?  It seems
> like it ought to be
LMTP is practically SMTP

http://www.faqs.org/rfcs/rfc2822.html

A mailbox receives mail.  It is a conceptual entity which does not
   necessarily pertain to file storage.  For example, some sites may
   choose to print mail on a printer and deliver the output to the
   addressee's desk.  Normally, a mailbox is comprised of two parts: (1)
   an optional display name that indicates the name of the recipient
   (which could be a person or a system) that could be displayed to the
   user of a mail application, and (2) an addr-spec address enclosed in
   angle brackets ("<" and ">").  There is also an
alternate simple form
   of a mailbox where the addr-spec address appears alone, without the
   recipient's name or the angle brackets.  The Internet addr-spec
   address is described in section 3.4.1.

   Note: Some legacy implementations used the simple form where the
   addr-spec appears without the angle brackets, but included the name
   of the recipient in parentheses as a comment following the addr-spec.
   Since the meaning of the information in a comment is unspecified,
   implementations SHOULD use the full name-addr form of the mailbox,
   instead of the legacy form, to specify the display name associated
   with a mailbox.  Also, because some legacy implementations interpret
   the comment, comments generally SHOULD NOT be used in address fields
   to avoid confusing such implementations.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20140709/97e2da13/attachment.sig>

On 9.7.2014, at 21.20, Jeff Rice <jeff at jrice.me> wrote:
> I'm transitioning my server over from using the deliver LDA and LMTP. 
Suddenly a bunch of sieve filters stopped working, and I noticed the contents of
the Delivered-To header are different.
> 
> Using Dovecot's deliver LDA, the contents are a bare email address (foo
at bar.com).  Using Dovecot LMTP, they are in brackets (<foo at bar.com>).
Is there a reason why this isn't consistent between the two delivery agents?
It seems like it ought to be.
Oh, that's annoying. Dovecot LDA doesn't actually add this header, it
was your MTA that added it. But looks like I hadn't checked what the MTAs
actually write to the header when I added this feature to LMTP, and nobody had
mentioned this before either. I wonder if anybody's system breaks if I just
change it now..