From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: imap namespace prefix
Date: Thu, 12 May 2011 13:54:25 -0500 [thread overview]
Message-ID: <87boz7zr4u.fsf@lifelogs.com> (raw)
In-Reply-To: <87y62cats1.fsf@gmail.com>
On Thu, 12 May 2011 08:16:30 -0600 Eric Schulte <schulte.eric@gmail.com> wrote:
ES> Just to follow up, I was able to work around this problem with the
ES> following changes to `nnimap-get-groups', which limit the LIST imap
ES> command to the ~/mail/ subdirectory of my home directory (the entirety
ES> of which was being served up by uw-imap).
...
ES> Since this option wasn't already present I assume this is a weird edge
ES> case peculiar to my school's server configuration and doesn't merit the
ES> addition of any new configuration parameters to gnus.
The IMAP server is supposed to advertise its prefix at connection time.
Can you look at the IMAP debug log (setq imap-debug t) and see?
Thanks
Ted
next prev parent reply other threads:[~2011-05-12 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:42 Eric Schulte
2011-05-12 14:16 ` Eric Schulte
2011-05-12 18:54 ` Ted Zlatanov [this message]
2011-05-12 23:13 ` Eric Schulte
2011-05-13 14:52 ` Ted Zlatanov
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=87boz7zr4u.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).