mailboxes and capitalisation
Dear all,
I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge
namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash } ... }
However, doveconf -n reports only one mailbox, namely the second (lowercase t) and autoexpunge does not trigger for the first one (capital T). Removing the special use flag has no influence.
namespace inbox { inbox = yes list = children location = ... mailbox trash { auto = subscribe special_use = \Trash } ... prefix = INBOX. separator = . subscriptions = yes type = private }
Is this the intended behaviour? The example 15-mailboxes.conf seems to indicate otherwise and I would prefer the ability to set autoexpunge for both Trash and trash. (dovecot 2.2.26 built from source on Debian 8.0)
Best regards, Thorsten
On 12/13/2016 4:48 AM, Thorsten Hater <thorsten.hater@gmail.com> wrote:
I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge
namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash }
Ugh... why create such a huge pain point for yourself?
I would never allow case sensitivity for usernames, or mail storage. Makes no sense.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 13 Dec 2016, Tanstaafl wrote:
On 12/13/2016 4:48 AM, Thorsten Hater <thorsten.hater@gmail.com> wrote:
I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge
namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash }
Ugh... why create such a huge pain point for yourself?
I would never allow case sensitivity for usernames, or mail storage. Makes no sense.
it starts with missing standards and device- or application-specific ways to do the same thing.
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBWFAQwHz1H7kL/d9rAQJkxwf/ea5WVv13qiPWhEUvNSKwIAXbgUDRbxru YJRYvqc9MpNDi+WibI0/2KojbjH2dxMk2xTRGfDodfkDd41Eue0npKaTR1/D49YZ CNT34yQMHGVpGyRQbRSsLncoMTrtGx9S8xYS/JwTWXgZ6B7FFYe00ypXVp8T6mxu O+/yre/DUfkTZW/0pqMj2i0kbL2NAeb6A1dSOxMuOCS2U4T5ZYNB6MuA6kIZsZ+S ZDvRx0uNJSRpS9hjdNdRFJ/ODyAdAE97LNqJTGUwSVlXHnTo3b4ibuLWHO9F4xs0 Cy/kRmpvxnyStcBaQqkARGefSRpp/hHI0E7X8AylDJpY4Ib38g5tmg== =ZiGg -----END PGP SIGNATURE-----
As far as I understand IMAP folders are -- largely -- case-sensitive, so I need to plan for Trash and trash (and worse), as there is no standard. Further, I cannot really expect all MUAs to honor special-use flags. My intention is to cover the most likely cases with autoexpunge.
I am still wondering if this behaviour is correct, given the case-sensitivity of IMAP.
Thorsten
On Tue, Dec 13, 2016 at 4:16 PM, Steffen Kaiser < skdovecot@smail.inf.fh-brs.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 13 Dec 2016, Tanstaafl wrote:
On 12/13/2016 4:48 AM, Thorsten Hater <thorsten.hater@gmail.com> wrote:
I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge
namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash }
Ugh... why create such a huge pain point for yourself?
I would never allow case sensitivity for usernames, or mail storage. Makes no sense.
it starts with missing standards and device- or application-specific ways to do the same thing.
- -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBWFAQwHz1H7kL/d9rAQJkxwf/ea5WVv13qiPWhEUvNSKwIAXbgUDRbxru YJRYvqc9MpNDi+WibI0/2KojbjH2dxMk2xTRGfDodfkDd41Eue0npKaTR1/D49YZ CNT34yQMHGVpGyRQbRSsLncoMTrtGx9S8xYS/JwTWXgZ6B7FFYe00ypXVp8T6mxu O+/yre/DUfkTZW/0pqMj2i0kbL2NAeb6A1dSOxMuOCS2U4T5ZYNB6MuA6kIZsZ+S ZDvRx0uNJSRpS9hjdNdRFJ/ODyAdAE97LNqJTGUwSVlXHnTo3b4ibuLWHO9F4xs0 Cy/kRmpvxnyStcBaQqkARGefSRpp/hHI0E7X8AylDJpY4Ib38g5tmg== =ZiGg -----END PGP SIGNATURE-----
On 13 Dec 2016, at 11.48, Thorsten Hater <thorsten.hater@gmail.com> wrote:
Dear all,
I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge
namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash } ... }
However, doveconf -n reports only one mailbox, namely the second (lowercase t) and autoexpunge does not trigger for the first one (capital T). Removing the special use flag has no influence.
I think you could do it for example:
mailbox Trash { ... } mailbox trash2 { name = trash ... }
By default name is the same as the section name, but while name setting itself is case-sensitive, the section name is not. This is because the setting keys may end up being environment variables, which are always uppercased.
participants (4)
-
Steffen Kaiser
-
Tanstaafl
-
Thorsten Hater
-
Timo Sirainen