-
-
Notifications
You must be signed in to change notification settings - Fork 790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lmtp_save_to_detail_mailbox
and aliases
#2988
Comments
Ok, either my understanding of what should happen is very wrong here or According to the
It looks to me like the fact that The same (probably) applies to
|
As you have found out, supporting this requires a significant rewrite... which may not happen any time soon unless we get a PR (and tests!) for it. |
@nextgens I think this does not need new code. We only have to make it simpler by removing the split at the recipient delimiters. |
The easiest is a sieve script; that would work with aliases, no? |
Yes, that's also my workaround for now.
|
Environment & Version
Environment
Version
2.0
Description
Dovecot comes with the
lmtp_save_to_detail_mailbox
option, which directs incoming mails into the corresponding mailbox folder if such folder exists (e.g.user+test@domain.tld
would be saved into thetest
folder), otherwise intoINBOX
.If enabled (via
lmtp_save_to_detail_mailbox
inoverrides/dovecot/dovecot.conf
), this works fine, however not in case ofalias+test@domain.tld
- in this case, the mail is delivered to the INBOX.The
Delivered-To
header showsuser+test@domain.tld
in case the mail is addressed touser+test@domain.tld
, but onlyuser@domain.tld
in case the mail is addressed toalias+test@domain.tld
, so the detail part after therecipient_delimiter
gets thrown away.Having looked around for a bit, I found that
docker compose exec smtp curl http://admin:8080/internal/postfix/alias/user+test@domain.tld
returnsuser+test@domain.tld
anddocker compose exec smtp curl http://admin:8080/internal/postfix/alias/alias+test@domain.tld
returnsuser@domain.tld
,which is consistent with the behavior I observe.
Maybe the detail part should be included here:
Mailu/core/admin/mailu/models.py
Lines 479 to 480 in ab59c32
...as it is here (implicitely):
Mailu/core/admin/mailu/models.py
Lines 460 to 467 in ab59c32
Replication Steps
lmtp_save_to_detail_mailbox = yes
inoverrides/dovecot/dovecot.conf
test
lmtp_save_to_detail_mailbox
is working by sending a mail to any user with the respective detail part (e.g.yourusername+test@domain.tld
- the mail should end up in the IMAP foldertest
.youralias+test@domain.tld
).Observed behaviour
The mail will end up in the
INBOX
.Expected behaviour
The mail should be saved into
test
.The text was updated successfully, but these errors were encountered: