dovecot-2.2.36-3.el7.x86_64
The below configuration seems to work for Thunderbird and emclient, when moving a message to Junk. Emclient uses "Junk E-mail" and Thunderbird uses "Junk". On the server is only the file .Junk created as expected.
When I move a message to Archive in Thunderbird. On the server the files .Archives and .Archives.2018 are created (Thunderbird creates a subfolder in Archives)
How is this possible? On the server there is already an .Archive folder so it should create .Archive.2018 not?
imap_capability = +SPECIAL-USE
# drafts folders merging mailbox Drafts { special_use = \Drafts auto = create }
# archive folders merging mailbox Archive { special_use = \Archive auto = create } mailbox Archives { special_use = \Archive auto = no }
# spam folders merging mailbox Junk { special_use = \Junk auto = create } mailbox Spam { special_use = \Junk auto = no } mailbox "Junk E-mail" { special_use = \Junk auto = no }
Op 15/12/2018 om 19:10 schreef Marc Roos:
dovecot-2.2.36-3.el7.x86_64
The below configuration seems to work for Thunderbird and emclient, when moving a message to Junk. Emclient uses "Junk E-mail" and Thunderbird uses "Junk". On the server is only the file .Junk created as expected.
When I move a message to Archive in Thunderbird. On the server the files .Archives and .Archives.2018 are created (Thunderbird creates a subfolder in Archives)
How is this possible? On the server there is already an .Archive folder so it should create .Archive.2018 not?
I can't say I have much experience with such client issues. Your configuration doesn't look wrong at first glance. Maybe assigning the special use flag to the mailboxes you don't want is a bad idea, but I am not sure.
First, you could connect to your IMAP server directly (e.g. using telnet) to verify that:
The SPECIAL-USE capability is actually announced.
The mailbox listed below are actually being returned by LIST command with the appropriate arguments.
Then (or alternatively), you can check the communication between your clients and Dovecot using the rawlog facility to find out what those are doing. That may give you some clues.
Regards,
Stephan.
imap_capability = +SPECIAL-USE
# drafts folders merging mailbox Drafts { special_use = \Drafts auto = create }
# archive folders merging mailbox Archive { special_use = \Archive auto = create } mailbox Archives { special_use = \Archive auto = no }
# spam folders merging mailbox Junk { special_use = \Junk auto = create } mailbox Spam { special_use = \Junk auto = no } mailbox "Junk E-mail" { special_use = \Junk auto = no }
Hi,
I also experienced that thunderbird behavior, I guess
[...]
When I move a message to Archive in Thunderbird. On the server the files
What exactly means move? Like drag and drop or via context menu "archive/archivieren"?
.Archives and .Archives.2018 are created (Thunderbird creates a subfolder in Archives)
How is this possible? On the server there is already an .Archive folder so it should create .Archive.2018 not?
I think this is intended. At least all my clients (thunderbird) do this. I think mozilla hoped to improve performance on big mailboxes by simply sorting archived mails by the mail's year.
[...]
-M info@awib.it
Am 07.01.2019 um 07:47 schrieb admin:
Hi,
I also experienced that thunderbird behavior, I guess
[...]
When I move a message to Archive in Thunderbird. On the server the files
What exactly means move? Like drag and drop or via context menu "archive/archivieren"?
.Archives and .Archives.2018 are created (Thunderbird creates a subfolder in Archives)
How is this possible? On the server there is already an .Archive folder so it should create .Archive.2018 not?
I think this is intended. At least all my clients (thunderbird) do this. I think mozilla hoped to improve performance on big mailboxes by simply sorting archived mails by the mail's year.
Thunderbird uses yearly archived folders by default, but this behaviour can be changed.
https://support.mozilla.org/en-US/kb/archived-messages
-- Alex JOST
participants (4)
-
admin
-
Alex JOST
-
Marc Roos
-
Stephan Bosch