search for: recipient_delimiter

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.[...] Uhm, yes, I know what this option s...

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 "foo" and never tries "foo-bar", even though it exists. My question would be: Is this due to a misconfiguration somewhere?...

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 ma...

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 abov...

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 i...

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 recipi...

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 > > separated from its extension by the first character that matches the > > recipient_delimiter [1] set.[...] > >...

I'm currently running postfix + dovecot, with virtual users In postfix I have set recipient_delimiter = + 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...

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 unix - n n - - pipe flags=DRhu user=vmail:vmail null_sender= argv=/usr/libexec/dovecot/deliver...

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 yet: > > dovecot.conf: > > plugin { > recipient_delimiter = + > } > > postfix: master.cf > > dovecot unix - n n - - pipe > flags=DRhu us...

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

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

> 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 receive mail anymore, because lmtp truncates the localpart >...

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 m...

...mation. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly. However, if I also try to pass a detail part through to the backend the lmtp users now take the form: <username+detail at domain> I can still use user=%{username} with recipient_delimiter = +, and the detail is correctly stripped, hashing works as expected. However, I can no longer use destuser=%{orig_user} Because recipient_delimiter = +, destuser becomes: <username at domain> And the detail part never reaches the backend. There doesn't appear to be any variables su...

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

...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 need for sieve to work, but now what? The first thing I want to do is have sieve process recipient_delimiter into a separate mailbox (creating it, if needed). Googling just for example sieve scripts comes up empty (well, directing to the dovecot wiki which at least on the links that come up, does not have sample scripts). so, foo+bar at example.com will go into foo's mailstore in the folder .bar/new/...

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 '-'...

...aracters (e.g. '--'). The current # implementation looks for the separator from the left of the # localpart and uses the first one encountered. The :user part is # left of the separator and the :detail part is right. This setting # is also used by Dovecot's LMTP service. #recipient_delimiter = + + + # Define if :detail is a prefix or a suffix to the :user address part, + # e.g. left or right, when using subaddress extension. + # Defaults to 'suffix' making sure not to break existing setups using + # <user><delimiter><suffix> format. + # Switch to 'prefix...