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 > (f...@bar.com). Using Dovecot LMTP, they are in > brackets (<f...@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.
signature.asc
Description: OpenPGP digital signature
