Displaying 20 results from an estimated 80 matches similar to: "recipient_delimiter"
2009 Feb 12
2
delivering to folder based on recipient_delimiter?
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
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
2014 Jan 28
1
recipient_delimiter -- feature request
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
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
2015 Apr 14
0
Dovecot and recipient_delimiter
Am 14.04.2015 um 15:28 schrieb Edwardo Garcia:
> Should not need to alter flags, eg:
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda
> -f ${sender} -e -d ${user}@${nexthop}
>
> works perfectly good.
Hi Edwardo,
here it doesn't.
If i use your settings i get this:
Apr 14 15:47:34 mule
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 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 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
2020 Mar 15
0
lmtp and recipient_delimiter
On 16/03/20 7:10 am, Juri Haberland wrote:
> My question would be:
> Is this due to a misconfiguration somewhere?
> Is this the intended behavior?
> Or is this a bug?
Poorly documented, imo, but you want lmtp_save_to_detail_mailbox = yes:
https://github.com/dovecot/core/blob/master/doc/example-config/conf.d/20-lmtp.conf#L8
Peter
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
2020 Mar 15
0
lmtp and recipient_delimiter
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
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
> >
2020 Mar 15
1
lmtp and recipient_delimiter
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/03/2020 21:26 Peter <
<a href="mailto:peter@pajamian.dhs.org">peter@pajamian.dhs.org</a>> wrote:
</div>
<div>
2016 Mar 31
2
multiple recipient_delimiter
Hello,
does the recipient_delimiter option accepts multiple delimiter by now?
--
Regards
J?rg Backschues
2010 May 26
4
recipient_delimiter
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?
2015 Apr 14
0
Dovecot and recipient_delimiter
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
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.[...]
2019 May 13
2
LMTP and Sieve with <prefix><recipient_delimiter><user>
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
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 _
2015 Apr 14
2
Dovecot and recipient_delimiter
On 4/14/15, J. Echter <j.echter at echter-kuechen-elektro.de> wrote:
> 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
>>