Either Wes jinxed us or we've finally demonstrated why allowing * in
mailbox names is a bad idea. We recently had a user rename a parent
mailbox containing a *, to a name not containing the *. At that
point cyrus took the liberty of renaming all the sub mailboxes by
removing the first
Ken Murchison wrote:
Has anybody already added some of these in production without any
adverse effects?
We've been using #define GOODCHARS
#$%'()*+,-.0123456789:;=[EMAIL PROTECTED]|}~
at Berkeley since 2006. No adverse effects, and the change was needed
as part of the migration from CGPro
On Tue, 30 Sep 2008, Ken Murchison wrote:
I started wondering what other special characters we might want to allow.
The original authors were more restrictive with GOODCHARS than the RFC.
AFAICT the following characters are permitted by RFC 3501 but aren't included
in GOODCHARS
! # $ ' ;
Ken Murchison wrote:
While looking over bug #3002,
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3002
I started wondering what other special characters we might want to
allow. The original authors were more restrictive with GOODCHARS than
the RFC. AFAICT the following characters are
On 30 Sep 2008, at 16:33, Ken Murchison wrote:
While looking over bug #3002, https://bugzilla.andrew.cmu.edu/
show_bug.cgi?id=3002
I started wondering what other special characters we might want to
allow. The original authors were more restrictive with GOODCHARS
than the RFC. AFAICT the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Murchison wrote:
|
| Has anybody already added some of these in production without any
| adverse effects?
|
We have been running the following for about a year on ~2.3.8 and a few
years before that on 2.2.x:
#define GOODCHARS
On 30 Sep 2008, at 21:23, Ken Murchison wrote:
Using list-wildcards would always be a bad idea IMHO.
UMich has a lot of mailboxes with * in their names. It's not a
problem, tho you're probably right that it's a bad idea. I guess
IMAP implementations usually use literals to communicate.
