dovecot - Mar 2019 - “doveadm mailbox” command fails with UTF-8 mailboxes

Hello,

	I?ve got a strange misconfiguration where the following command:

doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX
'INBOX.*'

? fails with error code 68, saying that it can?t find one of the mailboxes. (It
lists the user?s other mailboxes.) The name of the mailbox in question is saved
to disk in UTF-8 rather than mUTF-7, but strace shows that doveadm is stat()ing
the mUTF-7 path; the failure of that stat() is, assumedly, what causes doveadm
to report the error status.

	I?ve tried to paw through the source code to see what might be causing this but
haven?t made much headway. Can someone here point out where the misconfiguration
might be that is causing doveadm to stat() the mUTF-7 path rather than UTF-8? Or
perhaps offer any tips as to how I might diagnose what?s going on? What causes
doveadm to stat() one path or the other?

	Thank you!


-Felipe Gasper
Mississauga, ON

> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at
dovecot.org> wrote:
> 
>  
> Hello,
> 
> 	I?ve got a strange misconfiguration where the following command:
> 
> doveadm -f pager mailbox status -u spamutf8 'messages vsize guid'
INBOX 'INBOX.*'
> 
> ? fails with error code 68, saying that it can?t find one of the mailboxes.
(It lists the user?s other mailboxes.) The name of the mailbox in question is
saved to disk in UTF-8 rather than mUTF-7, but strace shows that doveadm is
stat()ing the mUTF-7 path; the failure of that stat() is, assumedly, what causes
doveadm to report the error status.
> 
> 	I?ve tried to paw through the source code to see what might be causing
this but haven?t made much headway. Can someone here point out where the
misconfiguration might be that is causing doveadm to stat() the mUTF-7 path
rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what?s
going on? What causes doveadm to stat() one path or the other?
> 
> 	Thank you!
> 
> 
> -Felipe Gasper
> Mississauga, ON
Mailbox should be stored on disk using mutf7, not UTF-8.

Aki

> On Mar 12, 2019, at 3:28 PM, Aki Tuomi <aki.tuomi at
open-xchange.com> wrote:
> 
> 
>> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at
dovecot.org> wrote:
>> 
>> 
>> Hello,
>> 
>> 	I?ve got a strange misconfiguration where the following command:
>> 
>> doveadm -f pager mailbox status -u spamutf8 'messages vsize
guid' INBOX 'INBOX.*'
>> 
>> ? fails with error code 68, saying that it can?t find one of the
mailboxes. (It lists the user?s other mailboxes.) The name of the mailbox in
question is saved to disk in UTF-8 rather than mUTF-7, but strace shows that
doveadm is stat()ing the mUTF-7 path; the failure of that stat() is, assumedly,
what causes doveadm to report the error status.
>> 
>> 	I?ve tried to paw through the source code to see what might be causing
this but haven?t made much headway. Can someone here point out where the
misconfiguration might be that is causing doveadm to stat() the mUTF-7 path
rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what?s
going on? What causes doveadm to stat() one path or the other?
>> 
>> 	Thank you!
>> 
>> 
>> -Felipe Gasper
>> Mississauga, ON
> 
> Mailbox should be stored on disk using mutf7, not UTF-8.
> 
> Aki
Hm. I have other users where the command above works, and the mailbox is stored
on-disk with a UTF-8 name, and the stat() call is indeed referencing the UTF-8
name.

Is there nothing in Dovecot that allows for a variance?

-FG

A tool to determine the encoding of a file is 'file -bi
<filename>' This
command is not perfect though.

On 3/12/19 2:20 PM, Felipe Gasper via dovecot wrote:
> Hello,
>
> 	I?ve got a strange misconfiguration where the following command:
>
> doveadm -f pager mailbox status -u spamutf8 'messages vsize guid'
INBOX 'INBOX.*'
>
> ? fails with error code 68, saying that it can?t find one of the mailboxes.
(It lists the user?s other mailboxes.) The name of the mailbox in question is
saved to disk in UTF-8 rather than mUTF-7, but strace shows that doveadm is
stat()ing the mUTF-7 path; the failure of that stat() is, assumedly, what causes
doveadm to report the error status.
>
> 	I?ve tried to paw through the source code to see what might be causing
this but haven?t made much headway. Can someone here point out where the
misconfiguration might be that is causing doveadm to stat() the mUTF-7 path
rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what?s
going on? What causes doveadm to stat() one path or the other?
>
> 	Thank you!
>
>
> -Felipe Gasper
> Mississauga, ON
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20190312/96d1518d/attachment.html>

On 12 Mar 2019, at 21.20, Felipe Gasper via dovecot <dovecot at
dovecot.org> wrote:
> 
> Hello,
> 
> 	I?ve got a strange misconfiguration where the following command:
> 
> doveadm -f pager mailbox status -u spamutf8 'messages vsize guid'
INBOX 'INBOX.*'
> 
> ? fails with error code 68, saying that it can?t find one of the mailboxes.
(It lists the user?s other mailboxes.) The name of the mailbox in question is
saved to disk in UTF-8 rather than mUTF-7, but strace shows that doveadm is
stat()ing the mUTF-7 path; the failure of that stat() is, assumedly, what causes
doveadm to report the error status.
> 
> 	I?ve tried to paw through the source code to see what might be causing
this but haven?t made much headway. Can someone here point out where the
misconfiguration might be that is causing doveadm to stat() the mUTF-7 path
rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what?s
going on? What causes doveadm to stat() one path or the other?
What's your doveconf -n? Using UTF-8 on filesystem requires using
"UTF-8" option in mail_location. Do you have it set?
https://wiki2.dovecot.org/MailLocation

> On Mar 12, 2019, at 5:23 PM, Timo Sirainen via dovecot <dovecot at
dovecot.org> wrote:
> 
> On 12 Mar 2019, at 21.20, Felipe Gasper via dovecot <dovecot at
dovecot.org> wrote:
>> 
>> Hello,
>> 
>> 	I?ve got a strange misconfiguration where the following command:
>> 
>> doveadm -f pager mailbox status -u spamutf8 'messages vsize
guid' INBOX 'INBOX.*'
>> 
>> ? fails with error code 68, saying that it can?t find one of the
mailboxes. (It lists the user?s other mailboxes.) The name of the mailbox in
question is saved to disk in UTF-8 rather than mUTF-7, but strace shows that
doveadm is stat()ing the mUTF-7 path; the failure of that stat() is, assumedly,
what causes doveadm to report the error status.
>> 
>> 	I?ve tried to paw through the source code to see what might be causing
this but haven?t made much headway. Can someone here point out where the
misconfiguration might be that is causing doveadm to stat() the mUTF-7 path
rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what?s
going on? What causes doveadm to stat() one path or the other?
> 
> What's your doveconf -n? Using UTF-8 on filesystem requires using
"UTF-8" option in mail_location. Do you have it set?
https://wiki2.dovecot.org/MailLocation
It turns out we had a missing a cache expiration when a user switches to UTF-8
filenames. So that?s why doveadm was looking for the mUTF-7 filename.

Now that we tracked that down, this appears to be working as it should.

Thank you, everyone!

-FG

On 2019-03-12 17:23, Timo Sirainen via dovecot wrote
> https://wiki2.dovecot.org/MailLocation
Sorry, this might be off-topic, but while reading up on the link you sent,
I've noticed the following sentence:

Use only absolute paths. Even if relative paths would appear to work, they
might just as well break some day.

Yet, all examples in the documentation use ~ which is a relative path.

Also, using an absolute path is impossible, if your users are located in
different parent home directories. e.g.:
/home2/<uname> /home3/<uname> /home4/<uname>
/var/users/<uname>

So how am I supposed to use an absolue path in such a case?
(If I wanted to have the maildir in their home directories and not in a
central location?)

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/20190312/e8d5ee48/attachment.sig>