From: Simon Josefsson <jas@extundo.com>
Subject: Re: seeing no imap folders
Date: Fri, 07 Nov 2003 00:56:36 +0100 [thread overview]
Message-ID: <ilu65hxdpaj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <c2dc332c.0311061453.7a027130@posting.google.com>
mail@vrtprj.com (Rainer Volz) writes:
> Simon Josefsson wrote
>> The server says there are no mailboxes on the server. Perhaps it is
>> buggy and doesn't understand "*%", although I'm not sure how to work
>> around that. Try telnet'ing manually to port 143 on the server and
>> log in and type '. LIST "" "*"' instead.
>
> Simon, you were right, this server didn't like the "%*". With "*" I
> got the folder listing in telnet. Any tip how to tell Gnus that? I
> played around with "nnimap-list-pattern", but that one seems to have a
> different purpose.
Try searching for "%\"" in imap.el and replace it with "\"". And
report it to your IMAP server administrator/vendor, so the bug can be
fixed...
parent reply other threads:[~2003-11-06 23:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c2dc332c.0311061453.7a027130@posting.google.com>]
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=ilu65hxdpaj.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).