Re: [Dovecot] recipient_delimiter
$recipient_delimiter = ‘+’
ahem, dumb question coming:
//I often read various threads here, and, look at my own setup, with a view of optimizing or understanding things I should...//
I have working dovecot 2.1.1 with postfix, only have virtual domains, all users in mysql;
'+' delimiter is enabled in postfix, and, works OK
postfix]# grep _delimiter main.cf # The recipient_delimiter parameter specifies the separator between
recipient_delimiter = +
BUT, I seem to have nothing in dovecot.conf:
postfix]# cd /etc/dovecot dovecot]# grep delimiter *
dovecot]# cd conf.d conf.d]# grep delimiter * 15-lda.conf:#recipient_delimiter = + 20-lmtp.conf:# the mail to the detail mailbox. See also recipient_delimiter and 20-lmtp.c_org:# the mail to the detail mailbox. See also recipient_delimiter and
should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ?
what will it add to this working setup, what am I missing?
thanks for all pointers
On Fri, 2013-09-27 at 07:29 +1000, voytek@sbt.net.au wrote:
I have working dovecot 2.1.1 with postfix, only have virtual domains, all users in mysql;
'+' delimiter is enabled in postfix, and, works OK
postfix]# grep _delimiter main.cf # The recipient_delimiter parameter specifies the separator between
recipient_delimiter = +
BUT, I seem to have nothing in dovecot.conf:
postfix]# cd /etc/dovecot dovecot]# grep delimiter *
dovecot]# cd conf.d conf.d]# grep delimiter * 15-lda.conf:#recipient_delimiter = + 20-lmtp.conf:# the mail to the detail mailbox. See also recipient_delimiter and 20-lmtp.c_org:# the mail to the detail mailbox. See also recipient_delimiter and
should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ?
what will it add to this working setup, what am I missing?
thanks for all pointers
Not needed, dovecot defaults to that setting, adding it in postfix is all thats required to work
On 26 Sep 2013, at 15:29 , voytek@sbt.net.au wrote:
should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ?
what will it add to this working setup, what am I missing?
Setting it will, as I understand it, cause dovecot to automatically file +extension mail in .extension/ (and auto-create the maildir if needed).
-- Varium et mutabile semper Femina.
On Thu, 2013-09-26 at 17:24 -0600, LuKreme wrote:
On 26 Sep 2013, at 15:29 , voytek@sbt.net.au wrote:
should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ?
what will it add to this working setup, what am I missing?
Setting it will, as I understand it, cause dovecot to automatically file +extension mail in .extension/ (and auto-create the maildir if needed).
Certainly does not do that by _default_ in a normal mysql/virtuser/maildir setup using lda when mail arrives for foo+dovecot@example.com it gets stored in foo's cur/ leaving it for the end users mail client to decide what to do with it, if anything.
On 26 Sep 2013, at 17:36 , Noel Butler <noel.butler@ausics.net> wrote:
Certainly does not do that by _default_ in a normal mysql/virtuser/maildir setup using lda when mail arrives for foo+dovecot@example.com it gets stored in foo's cur/ leaving it for the end users mail client to decide what to do with it, if anything.
Hmm. I guess I was misinformed. Too bad, since currently my procmail pipe is not working for virtual users (I am getting permission denied errors).
-- The quality of our thoughts and ideas can only be as good as the quality of our language.
On Fri, 27 Sep 2013 12:01:20 -0600 LuKreme articulated:
On 26 Sep 2013, at 17:36 , Noel Butler <noel.butler@ausics.net> wrote:
Certainly does not do that by _default_ in a normal mysql/virtuser/maildir setup using lda when mail arrives for foo+dovecot@example.com it gets stored in foo's cur/ leaving it for the end users mail client to decide what to do with it, if anything.
Hmm. I guess I was misinformed. Too bad, since currently my procmail pipe is not working for virtual users (I am getting permission denied errors).
Why use procmail when sieve is so much more powerful?
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On 27 Sep 2013, at 13:45 , Jerry <jerry@seibercom.net> wrote:
On Fri, 27 Sep 2013 12:01:20 -0600 LuKreme articulated:
On 26 Sep 2013, at 17:36 , Noel Butler <noel.butler@ausics.net> wrote:
Certainly does not do that by _default_ in a normal mysql/virtuser/maildir setup using lda when mail arrives for foo+dovecot@example.com it gets stored in foo's cur/ leaving it for the end users mail client to decide what to do with it, if anything.
Hmm. I guess I was misinformed. Too bad, since currently my procmail pipe is not working for virtual users (I am getting permission denied errors).
Why use procmail when sieve is so much more powerful?
First, I have a lot of procmail recipes over many years. Second, there are quite a few things that sieve can’t do that procmail does well (for just one example, calling external programs).
Sieve also doesn’t allow you to add or alter headers, I don’t believe.
-- Qui me amat, amat et canem meam
On Fri, 27 Sep 2013, LuKreme wrote:
Why use procmail when sieve is so much more powerful?
First, I have a lot of procmail recipes over many years. Second, there are quite a few things that sieve can?t do that procmail does well (for just one example, calling external programs).
One of the things I do with Procmail is look for certain key phrases in email to a particular special account and if found, send an email that includes the line containing that key phrase to my cell phone text message address. It's easy to do with Procmail and formail (which is part of the Procmail suite); I haven't a clue how to do that (if it's even possible) in Sieve.
I think those who advocate getting rid of Procmail in favor of Sieve are those whose interest is in sorting mail into folders. Those of us who advocate using Procmail are those who use Procmail for other purposes.
-- Larry Stone lstone19@stonejongleux.com
On Fri, 27 Sep 2013 15:54:41 -0500 (CDT) Larry Stone articulated:
On Fri, 27 Sep 2013, LuKreme wrote:
Why use procmail when sieve is so much more powerful?
First, I have a lot of procmail recipes over many years. Second, there are quite a few things that sieve can?t do that procmail does well (for just one example, calling external programs).
One of the things I do with Procmail is look for certain key phrases in email to a particular special account and if found, send an email that includes the line containing that key phrase to my cell phone text message address. It's easy to do with Procmail and formail (which is part of the Procmail suite); I haven't a clue how to do that (if it's even possible) in Sieve.
Clue: http://www.iana.org/assignments/sieve-extensions/sieve-extensions.xhtml
and
http://tools.ietf.org/html/draft-ietf-sieve-body-00
More clues are available.
I think those who advocate getting rid of Procmail in favor of Sieve are those whose interest is in sorting mail into folders. Those of us who advocate using Procmail are those who use Procmail for other purposes.
I have found very little that procmail can do that sieve cannot, other than being a nightmare to debug if something goes wrong.
Just my 2¢.
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
On Fri, 27 Sep 2013 14:39:10 -0600 LuKreme articulated:
On 27 Sep 2013, at 13:45 , Jerry <jerry@seibercom.net> wrote:
On Fri, 27 Sep 2013 12:01:20 -0600 LuKreme articulated:
On 26 Sep 2013, at 17:36 , Noel Butler <noel.butler@ausics.net> wrote:
Certainly does not do that by _default_ in a normal mysql/virtuser/maildir setup using lda when mail arrives for foo+dovecot@example.com it gets stored in foo's cur/ leaving it for the end users mail client to decide what to do with it, if anything.
Hmm. I guess I was misinformed. Too bad, since currently my procmail pipe is not working for virtual users (I am getting permission denied errors).
Why use procmail when sieve is so much more powerful?
First, I have a lot of procmail recipes over many years. Second, there are quite a few things that sieve can’t do that procmail does well (for just one example, calling external programs).
Is this what you are referring to: <http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe>
Sieve also doesn’t allow you to add or alter headers, I don’t believe.
Is this any help: <http://tools.ietf.org/html/rfc5293>
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 26 Sep 2013, LuKreme wrote:
On 26 Sep 2013, at 15:29 , voytek@sbt.net.au wrote:
should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ?
what will it add to this working setup, what am I missing?
Setting it will, as I understand it, cause dovecot to automatically file +extension mail in .extension/ (and auto-create the maildir if needed).
This setting by itself is only evaluated by Sieve scripts to let the address :detail test work.
In combination with lda_mailbox_autocreate and lda_mailbox_autosubscribe and lmtp_save_to_detail_mailbox this setting is used for LMTP delivery to override the default mailbox.
Dovecot LDA uses the "-m" option and only lda_mailbox_autocreate and lda_mailbox_autosubscribe, no need for recipient_delimiter to override the default mailbox.
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUkUkn13r2wJMiz2NAQKalQf/S7E7mZ33S0vdfdZXD3frz6PeF5MnG0AQ dCPpv+yuK4gXADbDqMpmYvA0Kpxd/wicwNFpdz98iIH+8D02pxX5xd3vWyG9WSQK 5SSptXyIgr4sqjfQwtl0SFNFnyYKT5sZg5wtevzIK/jnnLfveucXApd1DwDA6O/F gYvoYGB6BWsh/bx7qyeXilJm2P71u/s4+85rYxdJkXFZkMJZrTgMMA22bmKXyDNg 94XCA+Ynuwhvrry01u+KJLHYZGtrF1SA8uUz0C+MbAfsa1kiqcfVmKG/xbcpKj+X zawZQX6ktj+KDiUaSjUolQbxLYyVK78oJJDGrqhXBoWTItX7djwzpQ== =1+D7 -----END PGP SIGNATURE-----
participants (6)
-
Jerry
-
Larry Stone
-
LuKreme
-
Noel Butler
-
Steffen Kaiser
-
voytek＠sbt.net.au