Re: INBOX.INBOX.

[Bron Gondwana <brong@xxxxxxxxxxxxxxxx>]

No, it's deliberately allowing that case because in altnamespace, those are the Inbox subfolders, so they have to be allowed.

It still stops INBOX.INBOX.INBOX.INBOX.INBOX.INBOX.... which was the pathological case.

Bron.

On Wed, May 16, 2018, at 02:57, Wolfgang Breyha wrote:

Hi!

I'm not sure if this is a bug or intended...

cyrus checks for mailbox names including "INBOX.INBOX." since 2.5 and

prevents creation to stop buggy clients like Apple Mail from recursing.

But it still allows eg.

INBOX.INBOX.Trash

since the check is done after conversion to the internal user.<uid>... format.

INBOX.INBOX.(Trash|Sent|Drafts) is widely used by K9 (and others) as it

seems. K9 fixed it "recently" ...

https://github.com/k9mail/k-9/issues/701

... but it seems existing configs still use this pattern.

Does cyrus intentionally allow user.<uid>.INBOX. and only prevents

user.<uid>.INBOX.INBOX.... or is this a bug and will be changed in future

versions?

With kind regards,

Wolfgang Breyha

--

Wolfgang Breyha <wbreyha@xxxxxxx> | https://www.blafasel.at/

Vienna University Computer Center | Austria

----

Cyrus Home Page: http://www.cyrusimap.org/

List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

To Unsubscribe:

https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

--

  Bron Gondwana, CEO, FastMail Pty Ltd

  brong@xxxxxxxxxxxxxxxx

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus