similar to: mUTF-7 vs UTF-8 in mailbox names

Hello there, I'm pretty sure I found a bug in latest Dovecot 2.2.5.5 (EE) when playing with the doveadm command. Naturally renaming a users mail folder should be done via "doveadm es consistent. So when using "doveadm rename" trying to rename a folder with special characters e.g. german umlauts like "??" it seems to create the folder wrongly in the filesystem.

Hi all, I use "doveadm mailbox mutf7 -7 $folder" to convert imap foldernames to UTF-8. If $foldername is not mUTF-7 encoded, doveadm returns "doveadm(root): Error: Mailbox name not valid mUTF-7: $folder" This errormessage is printed on stderr but the returncode of doveadm is zero. I tested with dovecot-2.0.* and dovecot-2.1.* # all right: $ doveadm mailbox mutf7 -7

Dovecot 2.2.5 In selected state: C: 1 SELECT &#-&#/# S: 1 NO Mailbox name is not valid mUTF-7 S: * OK [CLOSED] Previous mailbox closed. I can verify that this only seems to happen when the mailbox name is incorrect mUTF-7. Things work fine if I access a non-existent mailbox: C: 1 SELECT non-existent-mailbox S: * OK [CLOSED] Previous mailbox closed. S: a NO Mailbox doesn't exist:

> 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

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

> 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

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

http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz.sig Most importantly fixes a pretty bad behavior of sending mailbox names as UTF-8 instead of mUTF-7 as required by IMAP RFC. I'm surprised nobody hadn't noticed this in v2.1.x tree before yesterday. I guess some clients might have translated the name to UTF-8 anyway and not noticed

http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz.sig Most importantly fixes a pretty bad behavior of sending mailbox names as UTF-8 instead of mUTF-7 as required by IMAP RFC. I'm surprised nobody hadn't noticed this in v2.1.x tree before yesterday. I guess some clients might have translated the name to UTF-8 anyway and not noticed

Is any proven routine to migrate mailboxes from mUTF-7 to UTF-8 encoding? I've try to use doveadm list/mutf7/rename but have been stuck with nested inboxes. Say I have the next structure: INBOX INBOX.??? INBOX.???.??? encoded for FS respectively as .INBOX .INBOX.&BDYESwRA- .INBOX.&BDYESwRA-.&BE8ENARK- ?When I've try to rename ?INBOX.??? with doveadm mailbox rename -u me

Currently mailbox names are stored in IMAP's modified-UTF-7 format in filesystem. I was wondering about changing this in v2.0. The default would still be to use mUTF-7 in filesystem, but just adding :UTF8 or something to mail_location could enable UTF-8. Any thoughts? Could this be dangerous somehow? UTF-8 enables a lot of weird characters, perhaps no one really wants to see them on

Hello. I read on upgrading page that one can use UTF8 mailbox names for plugins. As i understand i do not need to convert UTF8 names to mUTF-7 and can use raw UTF8 in plugins section, e.g.: /etc/dovecot/dovecot.conf ... plugin { ... # Autocreate \Spam folder autocreate = ???? autosubscribe = ???? ... But what about sieve scripts and other configuration sections: 1. Do i need to convert UTF8

A small bug in the mail_log plugin: When I copy a mail from the inbox to a mailbox with special characters, the mailbox name is logged in UTF-8: [...] copy from INBOX: box=INBOX.Euro ?, [...] I guess the name should be in mUTF-7, like it is done when I copy the other way round: [...] copy from Euro &IKw-: box=INBOX, [...]

Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even