On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote:
> I am getting an error when trying to create a new mbox "folder" via
> remote IMAP. Is this a known issue?
you probably tried to use a forbidden char in the folder name or
something.
(iirc, generic error means it didn't even make it to the mail
On Fri, 2002-11-08 at 22:21, Jeffrey Stedfast wrote:
> On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote:
> > I am getting an error when trying to create a new mbox "folder" via
> > remote IMAP. Is this a known issue?
>
> you probably tried to use a forbidden char in the folder name or
> somethin
On Fri, 2002-11-08 at 22:21, Jeffrey Stedfast wrote:
> On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote:
> > I am getting an error when trying to create a new mbox "folder" via
> > remote IMAP. Is this a known issue?
>
> you probably tried to use a forbidden char in the folder name or
> somethin
what mailbox name was it?
On Sat, 2002-11-09 at 17:51, Andrew Bertola wrote:
> On Fri, 2002-11-08 at 22:21, Jeffrey Stedfast wrote:
> > On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote:
> > > I am getting an error when trying to create a new mbox "folder" via
> > > remote IMAP. Is this a known i
On Sun, 2002-11-10 at 18:34, Not Zed wrote:
> what mailbox name was it?
I tried rh_80 and rh-80. I just tried "foo" and it returned an error.
Maybe it's permissions based, but mutt still has no problems creating
the new mailbox.
> On Sat, 2002-11-09 at 17:51, Andrew Bertola wrote:
> > On Fri,
what name are you typing into the GtkEntry field in the
Create-New-Folder dialog? You cannot enter \'s or /'s or #'s or...a few
other characters.
Jeff
On Tue, 2002-11-12 at 20:33, Mark C wrote:
> Hi,
>
> I'm running Evolution 1.2 on RedHat 8.0 (upgraded from the official
> 1.0.8 version), I'm u
On Wed, 2002-11-13 at 05:50, Jeffrey Stedfast wrote:
> what name are you typing into the GtkEntry field in the
> Create-New-Folder dialog? You cannot enter \'s or /'s or #'s or...a few
> other characters.
no It happens on anything I type say: foo, tmp, test.
The silly thing is, I fired up mozilla
I am experiencing the same behavior.. This just started with one of the
1.2 releases.. Not sure when into the dev cycle it started.. I just
noticed it.. I know it worked find with 1.08 and several of the snapshot
from that tree... Sometime after I switched to the 1.2 beta tree did
this show up...
