I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo at example.com to user at example.com? I'm not interested in the delivery into folder stuff, just the plain delivery to inbox. thanks, John
On Fri, 2009-05-22 at 20:45 +0200, John Fawcett wrote:> I read in the list archives about work in progress on > an lmtp delivery agent.As a previous cyrus user > where that was the preferred delivery method > from postfix, this sounds interesting. > > I was wondering whether it will handle > recipient delimiters. ie will it be able to map > user+foo at example.com to user at example.com? > I'm not interested in the delivery into folder stuff, > just the plain delivery to inbox.Hmm. Stephan, you currently have sieve_subaddress_sep setting. Should we instead use a common setting here? Like: protocol lda { recipient_delimiter = + } With v1.2 it probably wouldn't do anything, but with v2.0 LMTP could use it. -------------- 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/20090525/6095e587/attachment-0002.bin>
Timo Sirainen schreef:> On Fri, 2009-05-22 at 20:45 +0200, John Fawcett wrote: >> I read in the list archives about work in progress on >> an lmtp delivery agent.As a previous cyrus user >> where that was the preferred delivery method >> from postfix, this sounds interesting. >> >> I was wondering whether it will handle >> recipient delimiters. ie will it be able to map >> user+foo at example.com to user at example.com? >> I'm not interested in the delivery into folder stuff, >> just the plain delivery to inbox. > > Hmm. Stephan, you currently have sieve_subaddress_sep setting. Should we > instead use a common setting here? Like: > > protocol lda { > recipient_delimiter = + > } > > With v1.2 it probably wouldn't do anything, but with v2.0 LMTP could use > it.Sounds sensible. I can for instance make the plugin use this setting if sieve_subaddress_sep is not set. Regards, -- Stephan Bosch stephan at rename-it.nl