From: Patrick Gundlach <newsgroup@levana.de>
Subject: Re: IMAP splitting problem
Date: 24 May 2002 13:28:42 +0200 [thread overview]
Message-ID: <vuu1ox9445.fsf@levana.de> (raw)
In-Reply-To: <ilun0uqddqp.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
Hello Simon,
[...]
thanks for the patch. I think, I am getting closer! The log now
states:
543 OK Completed
544 UID COPY 9 "INBOX.private"
544 NO Mailbox does not exist
545 CREATE "INBOX.private"
545 NO Permission denied
546 EXPUNGE
* 4 EXISTS
* 0 RECENT
546 OK Completed
547 CLOSE
and so on. The server accepts the CREATE statement as follows
. create INBOX.bla
. NO Permission denied
. create INBOX/bla
. OK Completed
In my case, emacs/gnus/imap should issue the CREATE statement with the
"/" instead of the "." Or did I misunderstand something?
Patrick
--
I'll fade into the darkness
prev parent reply other threads:[~2002-05-24 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vu8z6dedng.fsf@levana.de>
[not found] ` <acebuj219pk@enews3.newsguy.com>
[not found] ` <vafadqs76yu.fsf@lucy.cs.uni-dortmund.de>
2002-05-23 1:18 ` those who know me have no need of my name
[not found] ` <ilud6vpe14p.fsf@latte.josefsson.org>
2002-05-23 12:55 ` Patrick Gundlach
2002-05-23 16:34 ` Simon Josefsson
2002-05-24 11:28 ` Patrick Gundlach [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vuu1ox9445.fsf@levana.de \
--to=newsgroup@levana.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).