dovecot - Jan 2013 - [PATCH] LMTP: Permit user IDs containing recipient_delimiter

The Dovecot 2.1 LMTP server currently always strips the address extension
from a recipient address (if recipient_delimiter is set), meaning user IDs
cannot contain the recipient delimiter character, e.g. "user+foo" is
not
supported.

This was surprising for me, as Postfix behaves differently in this regard:
It first looks up "user+foo", and only then "user".

The attached patch works for me and brings Dovecot's behavior in line with
Postfix. Please let me know what you think about it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lmtp_recipient_delimiter_in_uid.patch
Type: text/x-diff
Size: 3043 bytes
Desc: not available
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20130112/5ccebf50/attachment-0004.bin>

On Sat, 2013-01-12 at 17:45 +0100, Ulrich Zehl wrote:
> The Dovecot 2.1 LMTP server currently always strips the address extension
> from a recipient address (if recipient_delimiter is set), meaning user IDs
> cannot contain the recipient delimiter character, e.g. "user+foo"
is not
> supported.
> 
> This was surprising for me, as Postfix behaves differently in this regard:
> It first looks up "user+foo", and only then "user".
> 
> The attached patch works for me and brings Dovecot's behavior in line
with
> Postfix. Please let me know what you think about it.
What do you need this for? Do you really have usernames that have '+'
characters? Sounds like a bad idea. In Postfix it makes more sense,
because you might want user+ext to be delivered differently, but with
Dovecot you can do this in Sieve.