Thank you for pointing this out. Changing the mailbox path is not an
option anymore for us, easier to avoid this mailbox name.
Thank you!
On 15.03.23 15:07, Aki Tuomi wrote:
Documentation at https://doc.dovecot.org/configuration_manual/mail_location/
provides solution(s) for you:
SUBSCRIPTIO
id = 10000
> last_valid_uid = 10000
> lda_mailbox_autocreate = yes
> lda_mailbox_autosubscribe = yes
> listen = ::
> lmtp_save_to_detail_mailbox = yes
> log_path = /var/log/dovecot
> mail_attribute_dict = file:%h/Maildir/dovecot-attributes
> mail_gid = 1
> mail_location =
>
0
default_vsz_limit = 2 G
first_valid_gid = 500
imap_idle_notify_interval = 5 mins
last_valid_gid = 1
last_valid_uid = 1
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = ::
lmtp_save_to_detail_mailbox = yes
log_path = /var/log/dovecot
mail_attribute_dict = file:%h/Maildir/dovecot-at
> On 15/03/2023 13:12 EET Dejan wrote:
>
>
> > lmtp_save_to_detail_mailbox = yes
>
> Plus-delivery conflicts with existing, reserved files such as
> "subscriptions":
>
> Message for kim+subscriptions@ results in:
>
> lmtp(kim@***.com)<1449
> lmtp_save_to_detail_mailbox = yes
Plus-delivery conflicts with existing, reserved files such as
"subscriptions":
Message for kim+subscriptions@ results in:
lmtp(kim@***.com)<14493>: Error:
stat(/var/mails/***/kim/Maildir/subscriptions/tmp) failed: Not a
directory
Version: 2.3.18
> On 05-22-2022 10:53 am, Daniel Lange wrote:
> No, because that's not (easily) possible as others have pointed out already.
> FTR: It is possible but on the postfix side of things with multiple options.
> https://groups.google.com/g/mailing.postfix.users/c/1p0ubY726N8/m/D3s9V5PXHcIJ
> for the old
Am 22.05.22 um 11:33 schrieb Lucas Rolff:
Wouldn’t it be ideal to link to a LMTP documentation page that describes how to
do the same thing under LTMP, and not link to LDA?
No, because that's not (easily) possible as others have pointed out
already. FTR: It is possible but on the postfix side
Date: Sunday, 22 May 2022 at 12:55
To: dovecot@dovecot.org
Subject: Re: Fix lmtp_save_to_detail_mailbox to be case insensitive?
On 2022-05-22 12:35, Lucas Rolff wrote:
> Neither of those two describe how to lowercase the extension part –
oh
lmtp is single delivering so multirecipient is
On 2022-05-22 12:35, Lucas Rolff wrote:
Neither of those two describe how to lowercase the extension part –
oh
lmtp is single delivering so multirecipient is not supported, details
matter
postfix side of it knows this detail in lmtp
expand extension part in postfix would possible solve it
on behalf of Benny Pedersen
Date: Sunday, 22 May 2022 at 12:26
To: dovecot@dovecot.org
Subject: Re: Fix lmtp_save_to_detail_mailbox to be case insensitive?
On 2022-05-22 11:33, Lucas Rolff wrote:
> Wouldn’t it be ideal to link to a LMTP documentation page that
> describes how to do the same
On 2022-05-22 11:33, Lucas Rolff wrote:
Wouldn’t it be ideal to link to a LMTP documentation page that
describes how to do the same thing under LTMP, and not link to LDA?
typo :)
https://doc.dovecot.org/configuration_manual/protocols/lmtp_server/
https://wiki.dovecot.org/HowTo/PostfixDovecotL
Wouldn’t it be ideal to link to a LMTP documentation page that describes how to
do the same thing under LTMP, and not link to LDA?
> On 22 May 2022, at 01:07, Daniel Lange wrote:
>
> Am 21.05.22 um 23:30 schrieb dove...@ptld.com:
>> Dovecot accepts the mail from postfix via LMTP. Dovecot alread
Am 21.05.22 um 23:30 schrieb dove...@ptld.com:
Dovecot accepts the mail from postfix via LMTP. Dovecot already found the valid
recipient and accepted the email.
You need to make postfix pass the extension as lowercase to Dovecot.
See https://wiki.dovecot.org/LDA/Postfix :
An example using ad
> On 05-21-2022 2:29 pm, Benny Pedersen wrote:
> On 2022-05-21 19:17, dove...@ptld.com wrote:
>> To bring this up again because i have not found a work around solution.
>> Can dovecot make lmtp_save_to_detail_mailbox case-insensitive?
>>
>> If you create a fold
On 2022-05-21 19:17, dove...@ptld.com wrote:
To bring this up again because i have not found a work around solution.
Can dovecot make lmtp_save_to_detail_mailbox case-insensitive?
If you create a folder "foobar" then an email with recipient
user+foo...@example.com will be placed in
To bring this up again because i have not found a work around solution.
Can dovecot make lmtp_save_to_detail_mailbox case-insensitive?
If you create a folder "foobar" then an email with recipient
user+foo...@example.com will be placed in the folder.
However with the folder as "f
>> lmtp_save_to_detail_mailbox = yes
>> Is there anyway it make this feature case-insensitive?
> auth_username_format = %Lu
> might help...
> Aki
Im using the default for that setting and it shows it is already %Lu
[root dovecot]# doveconf -a auth_username_forma
> On 19/01/2022 06:15 dove...@ptld.com wrote:
>
>
> > Create a mailbox with name "test" in user's postbox.
> > Then send an email to and it will end up in
> > mailbox "test" instead of INBOX.
>
>
> I have noticed this is case-sensitive. If i create a folder "test" but
> someone sends the e
> Create a mailbox with name "test" in user's postbox.
> Then send an email to and it will end up in
> mailbox "test" instead of INBOX.
I have noticed this is case-sensitive. If i create a folder "test" but someone
sends the email to "user+t...@example.com" it wont get sorted into the folder.
> That means, if there is a mailbox with the same name as the used detail
> extension, it will move that email there.
>
> In your example:
> Set "lmtp_save_to_detail_mailbox = yes".
> Create a mailbox with name "test" in user's postbox.
> Then sen
Hello
Am 16.01.22 um 18:49 schrieb dove...@ptld.com:
> lmtp_save_to_detail_mailbox:
> " If the recipient address includes a detail element / role (as in
> user+detail format), save the message to the detail mailbox. "
>
> Im not understanding this, what is the &q
lmtp_save_to_detail_mailbox:
" If the recipient address includes a detail element / role (as in user+detail
format), save the message to the detail mailbox. "
Im not understanding this, what is the "detail mailbox"?
I tried testing this feature by setting "lmtp_save_to_
possible to
disable subaddressing (localuser+fol...@example.com) again.
The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox
item.
My idea was to override that setting for the specific user. I changed
the user_query to return no for the user in question and all seems well
On Fri, 12 Apr 2019, @lbutlr wrote:
All users except one: Said user asked if it would be possible to
disable subaddressing (localuser+folder at example.com) again.
The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox
item.
I thought it was sieve that did this
On 12 Apr 2019, at 09:06, Andreas Thienemann via dovecot
wrote:
>
> All users except one: Said user asked if it would be possible to disable
> subaddressing (localuser+fol...@example.com) again.
>
> The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox item.
I
) again.
The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox
item.
My idea was to override that setting for the specific user. I changed the
user_query to return no for the user in question and all seems well:
# doveadm user test
field value
usert...@example.com
uid
On 3/6/2014 5:19 PM, Dennis Kuhn wrote:
> 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
>
&
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=<
On 11/02/14 07:41, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Feb 2014, Alan Chandler wrote:
The problem I am facing is I can find no documentation about what
lmtp_save_to_detail_mailbox actually causes lmtp to actually do.
Searching the wiki refers to it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Feb 2014, Alan Chandler wrote:
The problem I am facing is I can find no documentation about what
lmtp_save_to_detail_mailbox actually causes lmtp to actually do. Searching
the wiki refers to it only in the LMTP page.
How should the
decide how to handle it.
The problem I am facing is I can find no documentation about what
lmtp_save_to_detail_mailbox actually causes lmtp to actually do.
Searching the wiki refers to it only in the LMTP page.
How should the detail of the address be formatted to specify a
subdirectory - can it be s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 1 Feb 2014, Andrew Ray wrote:
Is there any way to control/disable this for certain mailboxes?
For one account (that handles bounces) I need it disabled, for all the other
(normal) accounts its great.
Override it with UserDB Extra Fields
Hi Andrew,
you should consider using SIEVE.
SIEVE conditions will allow you to control which mails to file into
sub-mailboxes.
Regards
Daniel
Is there any way to control/disable this for certain mailboxes?
For one account (that handles bounces) I need it disabled, for all the
other (normal) accounts its great.
--
Andrew Ray
On 05/ 8/12 08:30 PM, Timo Sirainen wrote:
On Tue, 2012-05-08 at 13:36 -0400, Oscar del Rio wrote:
Dovecot 2.1.6, with
lmtp_save_to_detail_mailbox=yes
recipient_delimiter=+
messages addressed to "user+detail@domain" are always delivered to INBOX
regardless if "detail" mailb
On Tue, 2012-05-08 at 13:36 -0400, Oscar del Rio wrote:
> Dovecot 2.1.6, with
> lmtp_save_to_detail_mailbox=yes
> recipient_delimiter=+
>
> messages addressed to "user+detail@domain" are always delivered to INBOX
> regardless if "detail" mailbox alread
Dovecot 2.1.6, with
lmtp_save_to_detail_mailbox=yes
recipient_delimiter=+
messages addressed to "user+detail@domain" are always delivered to INBOX
regardless if "detail" mailbox already exists or lda_mailbox_autocreate=yes.
Anything else needed to enable lmtp_save_to_de
37 matches
Mail list logo
