On 2018-10-01 04:07, Timo Sirainen wrote:> > https://wiki2.dovecot.org/Plugins/Listescape?maybe?It should be mentioned somehow that one can't just change the hierarchy separator on the fly (without manual changes to the fs). If you used . as the separator, it would look this in the filesystem: .testfolder.sub1 Now you change the separator to $. Your mail client will see the existing folders as .testfolder.sub1 instead of: testfolder sub1 Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20181002/676c9aa5/attachment.sig>
On 2 Oct 2018, at 22.52, Helmut K. C. Tessarek <tessarek at evermeet.cx> wrote:> > On 2018-10-01 04:07, Timo Sirainen wrote: >> >> https://wiki2.dovecot.org/Plugins/Listescape maybe? > > It should be mentioned somehow that one can't just change the hierarchy > separator on the fly (without manual changes to the fs). > > If you used . as the separator, it would look this in the filesystem: > .testfolder.sub1 > Now you change the separator to $. > Your mail client will see the existing folders as .testfolder.sub1 > instead of: > > testfolder > sub1No, that's not how the listescape plugin works. You can't change the filesystem separator with or without listescape plugin. It's always "." with Maildir++. You can change the namespace's visible separator to e.g. "$" which allows you to start using "." in the folder names with listescape. But using "." will be encoded as \2e (or something) in the filesystem. Changing the namespace separator can have other problems though. Clients generally don't like it much, and may redownload all mails in subfolders if it's changed. Some clients may become even more confused. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Message signed with OpenPGP URL: <https://dovecot.org/pipermail/dovecot/attachments/20181002/6f511e21/attachment.sig>
On 2018-10-02 16:02, Timo Sirainen wrote:> No, that's not how the listescape plugin works. You can't change the filesystem separator with or without listescape plugin. It's always "." with Maildir++.This exactly my point. This fact is nowhere stated in the documentation. I'm actually not talking about the plugin at all. (I'm very sorry that I've replied to your listescape reply, my bad.) The documentation only mentions that the separator can be changed by setting the `separator` option. But it doesn't explain what it actually does and why one wanted to do so in the first place. e.g. Someone uses the default. Then changes it to something else. What happens then? (you answered it already partly - clients might be confused). But if the filesystem always used the . for Maildir, why would somebody want to change the separator (without the plugin)? Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20181002/65536274/attachment-0001.sig>
I have an odd issue. One user has an email in her Maildir/cur folder named: 1545229920.27374_0.mail:2,. She cannot see this message in her mail client (Thunderbird). All other emails have 'S' and 'W' components to the name, e.g. 1488471573.M167365P19808.mail,S=41356,W=42118:2,RS, but this one does not. Would that somehow make a difference in it being visible to the mail client? Why would this message have been saved without the 'S' and 'W' bits? In fact, there are two such message with this abbreviated file name, both from the same sender. Is there possibly something about the message that affects naming? Dovecot version 2.2.33.2 THX --Mark