similar to: recipient delimiter and lmtp

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username at domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly.

Just a comment about the documentation for postfix integration when using receipient delimiter and delivery of user+foo at domain.ext to user at domain: http://wiki.dovecot.org/LDA/Postfix I had some issues to get this working, so thought I'd share my experience. Dovecot version 1.2.rc3. Postfix version postfix-2.7-20090511. I have no local (unix) mailboxes, everything is delivered to

Since many broken websites and idiot companies will not allow a ?+? in an email address, I have long used two delimiters in postfix: recipient_delimiter = +_ However, now that dovecot is handling verification for postfix via reject_unverified_recipient, dovecot complains about any address using an _ as a delimiter. I don?t see a way to tell dovecot what delimiters to use, and it appears it is

On 20/06/2019 01:20, @lbutlr via dovecot wrote: > On 18 Jun 2019, at 15:03, @lbutlr via dovecot <dovecot at dovecot.org> wrote: >> I don?t see a way to tell dovecot what delimiters to use, and it appears it is still using a single delimiter only despite postfix having added support for more than one years ago. > Ideas? There is the recipient_delimiter setting. For recent

Hello, There is a disconnect between the way Postfix handles recipient_delimiter and the way Dovecot handles it. For Postfix, it is a set of delimiters that can each individually be used to separate the address from the . In Dovecot, having multiple characters in recipient_delimiters simply makes it a multi-character single delimiter. For my purposes, the Postfix method is much more

Trying to find out if dovecot supports the use of multiple recipient delimiters, as postfix does, but can't find an answer... The wiki only mentions it in two meaningful places (that I can find)... With respect to postfix: /wiki.dovecot.org/LDA/Postfix The above seems to imply that for postfix/LDA all I need to do is define it in postfix (which supports multiple recipient delimiters). And

Hi! As a new user, I'm trying to set up a postfix + dovecot combination, and so far all is running smoothly. I'm using the guidelines that came with postfix and adjusting them as I go. My user and alias database is stored in MySQL, using the scheme from 'PostfixAdmin' (http://high5.net/page9.html) and I am using the dovecot LDA 'deliver' to drop messages into mailboxes

On 6/2/2016 3:50 PM, Tanstaafl <tanstaafl at libertytrek.org> wrote: > On 6/2/2016 10:35 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: >> Trying to find out if dovecot supports the use of multiple recipient >> delimiters, as postfix does, but can't find an answer... > > The reason this is important is simple. I've encountered a lot of sites > that

Hello, I have a forum system which can potentially have users send email to it for posting purposes that arrives addressed to a particular user account with a recipient delimiter: user+1a2b3c4d5e6f at domain.com The forum server is supposed to check the "user" account mailbox's inbox for the messages and post them to the site automatically. This doesn't work right now

Hello We have migrated our email services from a server, which did not support IMAP and folders, therefore threated the plus sign + as a normal character in a part of an email address. Our new server delivers the emails via lmtp to dovecot. the few users which got a + character in the username first could not log-in (fixed by adding + to auth_username_chars). Now the next problem turn out to

On 15/03/2020 21:26, GMX Account wrote: > have a look at this: > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > [...]When the recipient_delimiter [1] set contains multiple characters > (Postfix 2.11 and later), a user name or .forward file name is > separated from its extension by the first character that matches the > recipient_delimiter [1] set.[...]

Hi, It would be nice if the recipient_delimiter configuration option supported multiple recipient delimiters as Postfix now does. e.g. now if I set: recipient_delimiter = +- in Postfix, then test-extension at sample.com and test+extension at sample.com are both recognized. But if I set: recipient_delimiter = +- in Dovecot, neither of the above are recognized and instead test+-extension at

Hello, I'm using dovecot 1.0.3 and Dovecot Sieve plugin 1.0.2. Sieve script works fine with normal addresses, like user at domain.., and messages marked with "X-Spam-Flag: YES" are delivered directly to INBOX.Spam. To make deliver understand recipient_delimiter I tried two methods, the first one as per wiki (tweaking postfix master.cf), and the second one by tweaking

Hi there, Dovecot's LMTP implementation and Pigeonhole Sieve already do support the <user><delimiter><suffix> format. RfC 5233, the Sieve subaddress extension, also offers <prefix><delimiter><user>. Could Docecot's LMTP and Pigeonhole be extended to that effect? Thanks & greetings, Paul

I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox if anyof (header :contains ["to"] [ ?FOO", ?foo", ?bar", ?florin"]) { fileinto :create ?later"; stop; } When I get an email addressed to me+FOO at example.com or me_florin at example.com, the messages end up in my inbox (Yes, I have both + and _

Hi, Am 15. November 2015 01:46:29 MEZ, schrieb fsantiago at garbage-juice.com: >Hello, > >I have a forum system which can potentially have users send email to it > >for posting purposes that arrives addressed to a particular user >account >with a recipient delimiter: > >user+1a2b3c4d5e6f at domain.com > >The forum server is supposed to check the "user"

Hi list, I have a small problem with recipient_delimiters contained in usernames. Recently I have extended recipient_delimiter from "+" to "+-" in both Postfix and Dovecot (using lmtp) and now any user that have a '-' in it's username can't receive mail anymore, because lmtp truncates the localpart after the '-' and of course can't find the first

On 18 Jun 2019, at 15:03, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > I don?t see a way to tell dovecot what delimiters to use, and it appears it is still using a single delimiter only despite postfix having added support for more than one years ago. Ideas? -- Lead me not into temptation, I can find the way.

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

Op 3/24/2018 om 9:16 AM schreef Andr? Rodier: > Dear all, > > I have found a way to automatically copy sent emails in the "Sent" > folder, but I am not sure it is the simplest and more reliable way on > the long term. > > I am open to suggestions if I miss a feature in Dovecot - or Postfix, > that allows me to do this. I vaguely remember an SMTP extension that do