similar to: LMTP and Sieve with <prefix><recipient_delimiter><user>

Displaying 20 results from an estimated 4000 matches similar to: "LMTP and Sieve with <prefix><recipient_delimiter><user>"

2019 May 15
0
LMTP and Sieve with <prefix><recipient_delimiter><user>
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
2019 Nov 16
2
Sieve and recipient_delimiter
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 _
2019 Nov 17
0
Sieve and recipient_delimiter
From the Notes section of my sieve file, because I always forget this # MORE NOTES: # Using :localpart takes just the local part of an address # header selects a header, address selects an address # Looks like this is the spec: # :localpart = :user+:detail # address are :localpart @ :domain, or :user + :detail @ :domain # See RFC5233 I use this bit for figuring out what :detail something (might)
2020 Mar 11
2
lmtp and recipient_delimiter
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
2020 Mar 15
2
lmtp and 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.[...]
2020 Oct 22
2
Sieve_before
On 22 Oct 2020, at 10:05, @lbutlr <kremels at kreme.com> wrote: > require ["variables", "copy"]; > > if address :matches ["To", "Cc"] ["*@*."] { > redirect :copy "backup+295.${1}.${2}@*example.com*"; > } I have tried this with similar results: require ["copy", "variables",
2013 Sep 25
2
recipient_delimiter
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 =
2016 Mar 31
2
multiple recipient_delimiter
Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards J?rg Backschues
2013 Jan 12
1
[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
2013 Oct 23
1
recipient_delimiter deux
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
2020 Mar 15
0
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 > >
2015 Apr 14
2
Dovecot and recipient_delimiter
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
2020 Mar 12
0
lmtp and recipient_delimiter
> 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
2015 Feb 12
0
[Patch] Allow for more than one recipient_delimiter (a la postfix 2.11)
Hey everyone, as my previous emails apparently got stuck in a spam filter I'll try this again. The patches attached here allow for more than one recipient delimiter in the address. Which is allowed in postfix since version 2.11. E.g. lhw+postfix at ring0.de would be equal to lhw-postfix at ring0.de if configured that way. Same as postfix only the first discovered delimiter is taken into
2014 Mar 06
1
no sieve with lmtp_save_to_detail_mailbox=yes
i have a problem with sieve and lmtp_save_to_detail_mailbox = yes. If the mailbox "detail" exists everything works fine, but if the mailbox detail does not exist then sieve does not work. The .dovecot.sieve.log file says sieve: info: started log at Mar 06 14:28:47. error: msgid=<531877EE.7070806 at heinlein-support.de>: failed to store into mailbox 'test2': Mailbox
2006 Oct 06
2
factor levels with umlauts
Hi all I have to generate some test data for import in an sql database. The database is meant for web-based data entry in a study taking place in a german speaking region, so factor levels of the variables include umlauts. The variables in the dataframe t.muster are generated e.g. like this: t.muster$screening <- rep("ausgef?llt",50) and exported to a .csv file by:
2014 Oct 25
1
Dynamic tags in email address
I'm trying to get dynamic tagging (user+sometag at example.com) to work on a mail server I'm setting up, however it only works as long as it's sent to the main user and not to aliases. virtual-alias-maps query: SELECT get_email_alias_dyn('%s') virtual-mailbox-domains query: SELECT 1 FROM domain WHERE name='%s' virtual-mailbox-maps query: SELECT 1 FROM user_alias
2013 Oct 02
2
doveadm can't import his own mdboxes
We're running Dovecot 2.1.17 on Debian: # 2.1.17 (9efbc0731929): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab078.27.debug i686 Debian 7.1 simfs and we're having this namespace configuration: mail_location = mdbox:/var/mail/%Ld/%Ln/mdbox namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = prefix = separator = .
2020 Mar 15
3
lmtp and recipient_delimiter
On 12/03/2020 08:04, Jean-Daniel wrote: > > >> 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
2020 Mar 15
2
lmtp and recipient_delimiter
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