search for: recipient_delimited

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.[...]

On 15/03/2020 20:26, Peter wrote: > Poorly documented, imo, but you want lmtp_save_to_detail_mailbox = yes: Thanks, tried it, but no, that's not what I want and it doesn't help in my case. To recap: If I set recipient_delimiter to "+-" (or "-" alone), having a user named "foo-bar" won't work anymore, because Dovecot always tries to deliver to user

Can I enable $recipient_delimiter = ?+? for only the virtual sql users? $ doveconf -n # 2.2.5: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.1-RELEASE i386 auth_mechanisms = PLAIN LOGIN disable_plaintext_auth = no first_valid_uid = 89 login_log_format_elements = user=<%u> %r %m %c mail_location = maildir:~/Maildir mail_max_userip_connections = 90 managesieve_notify_capability =

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, 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

Hi, 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.[...] --- Original Nachricht --- Betreff:?Re: lmtp and recipient_delimiter

On Sonntag, 15. M?rz 2020 21:43:08 CET Juri Haberland wrote: > 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 > >

...so that postfix accepts mail for user at example.com, user+foo at example.com, and user+spam at example.com all deliver to inbox. what I would like is to have email directed to user+foo at example.com delivered to the IMAP folder foo (and, in the context of amavisd, have amavis configured for recipient_delimited, and add addr_extension_spam_maps add +spam to each mail identified as spam, and thus the mail would go to the spam folder on delivery. The postfix guys say I should be able to do this. can someone point me to how to implement this with dovecot? (as I don't see how to even start). Thx Ric...

Hi, we're using thunderbird as our client, it has the functionality to sort spamassassin tagged mails in a folder called 'Junk'. I have this folder on my dovecot server and i'd like to use the recipient_delimiter feature to get my spam/junk mails directly to this folder. what i have done yet: dovecot.conf: plugin { recipient_delimiter = + } postfix: master.cf dovecot

Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards J?rg Backschues

Am 14.04.2015 um 14:04 schrieb J. Echter: > Hi, > > we're using thunderbird as our client, it has the functionality to > sort spamassassin tagged mails in a folder called 'Junk'. > > I have this folder on my dovecot server and i'd like to use the > recipient_delimiter feature to get my spam/junk mails directly to this > folder. > > what i have done

I have recipient_delimiter = + in main.cf (Postfix). But deliveries to dovecot/deliver are still being rejected. It appears that the full email is still in the envelope (e.g. phil+howard at example.com which I want to be delivered to phil at example.com). Is that how it's supposed to work and Dovecot just doesn't support this?

> In dovecots 15-lda.conf uncomment the "recipient_delimiter = +" setting. The delimiter is configured in postfix but apparently not in your dovecot lda config I am not sure of the location of 15-lda.conf, however in my main dovecot.conf file I added "recipient_delimiter = +" The output of the lad part of "dovecot -n" is now > protocol lda { >

> Le 11 mars 2020 ? 19:32, Juri Haberland <juri at koschikode.com> a ?crit : > > 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

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

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.

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 _

OK, I've been banging my head on why my procmail setup for virtual users is no longer working (difficult to test, since enabling it breaks live user's mail). There are only a few virtual users who have any sort of filters in place anyway (the heavy procmail users are local, not virtual), and they are fairly simple, so I think I can recreate them with sieve. I think I have everything I

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

Hi, way forward could be like this: 1) Introduce a new config option 'detail_affix' with parameters 'prefix' and 'suffix', defaulting to 'suffix' making sure not to break existing setups using <user><delimiter><suffix> respectively :user<delimiter>:detail format. If 'detail_affix' is switched to 'prefix' the expected