Hi Liste
We are and ISP and use Dovecot.
From time to time, we have customer reporting not being able to delete IMAP folder they have created.
This often seems to happen when some email client is creating temporary folder on some move or copy operations.
Permissions look right. I can't figure out, what goes wrong, but I can reproduce via telnet by manually issuing IMAP commands.
To me it looks like Dovecot forgets about what folders exist. Is there some caching of the folder information? Is there a way to enable some debug logging of folder creation and deletion?
Example: Customer has a Folder named: ARCHIV.AdministrationXXX
Folder file exists and permissions look right: ./ARCHIV/AdministrationXXX
d delete ARCHIV.AdministrationXXX d OK Delete completed (0.001 + 0.000 secs).
Folder file is still present and can not be deleted again. Re-Connecting with a client lists the folder as present despite having been deleted. It's sort of a Schrödinger Folder. It is there but it's also not there.
c create ARCHIV.AdministrationXXX c OK Create completed (0.007 + 0.000 + 0.006 secs). d delete ARCHIV.AdministrationXXX d OK Delete completed (0.006 + 0.000 + 0.005 secs).
Now the Folder File is gone, showing the permissions were correct.
I can do this corrective action via telnet. But most mail clients will refuse to create a Folder with the same name as an existing one.
What could cause that issue and how I could try to further debug the issue?
No errors, no hints in the logs.
-- Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
I m p r o W a r e A G - Leiter Commerce Kunden
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch
Example: Customer has a Folder named: ARCHIV.AdministrationXXX
Folder file exists and permissions look right: ./ARCHIV/AdministrationXXX
d delete ARCHIV.AdministrationXXX d OK Delete completed (0.001 + 0.000 secs).
Folder file is still present and can not be deleted again. Re-Connecting with a client lists the folder as present despite having been deleted. It's sort of a Schrödinger Folder. It is there but it's also not there.
What could cause that issue and how I could try to further debug the issue?
I think a good work around would be using LAYOUT=INDEX then you get folder names like this and you 'probably' do not have such conflicts. I think this layout is also better for when people start using 'weird' characters or long names. Bad thing is, you need to convert everything.
drwxrwx--- 2 10001 10001 6 Sep 17 20:44 67b77b07fa3330635457000052412a8e drwxrwx--- 2 10001 10001 6 Sep 18 21:09 a2585d3ae5714e636229030052412a8e drwxrwx--- 2 10001 10001 6 Sep 18 21:53 36179613fa3330637557000052412a8e drwxrwx--- 2 10001 10001 6 Sep 21 20:19 c07dd6138d5d3063615b000052412a8e drwxrwx--- 2 10001 10001 6 Sep 21 22:56 7908061cf23330634d57000052412a8e
Hi Marc
I think a good work around would be using LAYOUT=INDEX then you get folder names like this and you 'probably' do not have such conflicts. I think this layout is also better for when people start using 'weird' characters or long names. Bad thing is, you need to convert everything.
Hmm, interesting, so there is an abstraction layer between the folder names in the file system and what is reported when listing the folder via IMAP?
Maybe an index file that got corrupted?
If so, where is this file? Could it be safely deleted to have dovecot re-create it?
-- Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
I m p r o W a r e A G - Leiter Commerce Kunden
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch
I think a good work around would be using LAYOUT=INDEX then you get folder names like this and you 'probably' do not have such conflicts. I think this layout is also better for when people start using 'weird' characters or long names. Bad thing is, you need to convert everything.
Hmm, interesting, so there is an abstraction layer between the folder names in the file system and what is reported when listing the folder via IMAP?
sort of, you can have multiple storage backends. I am using mdbox, looks like this
├── control │ ├── dovecot-uidvalidity │ ├── dovecot-uidvalidity.66410c64 │ └── subscriptions ├── mdbox │ ├── dbox-alt-root -> /home/altmail/xxxx │ ├── dovecot-acl-list │ ├── mailboxes │ │ ├── 36179613fa3330637557000052412a8e │ │ ├── 67b77b07fa3330635457000052412a8e │ │ ├── 7908061cf23330634d57000052412a8e │ │ ├── 80628213e4f562613b27000052412a8e │ │ ├── a2585d3ae5714e636229030052412a8e │ │ ├── b45e8a3819f662614d27000052412a8e │ │ └── c07dd6138d5d3063615b000052412a8e │ └── storage │ ├── m.2 │ ├── m.3 │ ├── m.4 │ ├── m.5 │ ├── m.8 │ └── m.9 ├── sieve │ ├── managesieve.sieve │ └── tmp └── whitelist.gdbm
Maybe an index file that got corrupted?
I don't know. I did not see such things. Maybe if you have busy server and io waits on the file system you run into such things. I don't really have a busy server.
If so, where is this file? Could it be safely deleted to have dovecot re-create it?
There is indeed a doveadm command to check/fix indexes. I would stick to doveadm operations, not touch files/dirs directly.
participants (2)
-
Benoît Panizzon
-
Marc