[imp] Folders with "." in their Name

Eric Rostetter eric.rostetter@physics.utexas.edu
Mon Oct 14 15:36:04 2002


Quoting Ryan Gallagher <ryan@studiesabroad.com>:

> Quoting Jan Schneider <jan@horde.org>:
> 
> > Zitat von Joerg Battermann <jb@startupx.com>:
> >
> > > when creating new folders, it seems like IMP doesn't check for "."'s in
> > > the name.

In what sense doesn't it check?  Do you mean you think it should recode these
to some other character?  Or do you mean it isn't recognizing them as a
mailbox hierarchy seperator and treating it as such?  Which do you consider
the correct action?

> > > I just created a Folder e.g. "ABC.DEF", and now it seems like IMp
> > > can't handle it properly.

In what sense?  I would expect that, unless I've set my Mailbox Hierachy
Seperator differently, that it would create a folder ABC, and inside that
create a subfolder DEF.  Is this what it is doing?  Is this not what you
expect for some reason?

> > > I can't delete the folder anymore, because IMP
> > > displays DEF as a subfolder of ABC, where the actual Dir -is- ABC.DEF :\

I would expect it to do as you say IMP does -- A folder ABC with a subfolder
DEF.  Does it work that way?  Or it it a bug in that it creates an actual
folder ABC.DEF, but then accesses it as two seperate folders when it is
really one?

Please try to clarify what exactly you expect it to do, what it is doing,
and why you think that is wrong.  I can't tell from your posting details
if this is a bug or a feature.

> > That's a "feature", not a bug. ;-)
> > Jan.

Probably, but it is really hard to tell from just the details he gives.

We need more details to actually understand if it is working or not.

> alter the full path) but the resultant behavior is entirely too vague and,
> IMHO is not appropriate for the user audience HORDE claims to target.

Okay, how is it too vague?  And what audience is Horde claiming to target?

Is your problem that we let you type in folder hierachies, rather than making
you enter them one by one in sequence?  I'm not sure at all what your complaint
is.

> It's a 'bug' with any IMAP backend that uses the default delimiter of "." for
> mailbox names (Cyrus here).

If so, I assume it is the same bug elsewhere, just by changing the character
to match the backend's hierachy character, no?

>  Using an alternate delimiter in IMAP should not be
> necessary for getting IMP to behave.

Again, behave how?

I'd really like to help, but I just have no clear idea of what it is you
consider a bug, why you consider it a bug, and what alternate handling of
it you desire.

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Why get even? Get odd!