Gitweb:
http://git.exim.org/exim.git/commitdiff/23461791bfb0685bb769328e7a38b245d9f4853b
Commit: 23461791bfb0685bb769328e7a38b245d9f4853b
Parent: 7c261cc6918d1bdb019a213fc986b668cbbe456e
Author: Todd Lyons <tlyons@???>
AuthorDate: Tue Oct 8 11:00:33 2013 -0700
Committer: Todd Lyons <tlyons@???>
CommitDate: Tue Oct 8 11:00:33 2013 -0700
Bug 1150: Enhance docs for ${addresses:} expansion
---
doc/doc-docbook/spec.xfpt | 23 +++++++++++++++++++++++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 31767bf..0d539b0 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -9652,6 +9652,29 @@ expansion item, which extracts the working address from a single RFC2822
address. See the &*filter*&, &*map*&, and &*reduce*& items for ways of
processing lists.
+To clarify "list of addresses in RFC 2822 format" mentioned above, Exim follows
+a strict interpretation of header line formatting. Exim parses the bare,
+unquoted portion of an email address and if it finds a comma, treats it as an
+email address seperator. For the example header line:
+.code
+From: =?iso-8859-2?Q?Last=2C_First?= <user@???>
+.endd
+The first example below demonstrates that Q-encoded email addresses are parsed
+properly if it is given the raw header (in this example, &`$rheader_from:`&).
+It does not see the comma because it's still encoded as "=2C". The second
+example below is passed the contents of &`$header_from:`&, meaning it gets
+de-mimed. Exim sees the decoded "," so it treats it as &*two*& email addresses.
+The third example shows that the presence of a comma is skipped when it is
+quoted.
+.code
+# exim -be '${addresses:From: \
+=?iso-8859-2?Q?Last=2C_First?= <user@???>}'
+user@???
+# exim -be '${addresses:From: Last, First <user@???>}'
+Last:user@???
+# exim -be '${addresses:From: "Last, First" <user@???>}'
+user@???
+.endd
.vitem &*${base62:*&<&'digits'&>&*}*&
.cindex "&%base62%& expansion item"
