From: Clinton Roy <latte@uq.net.au>
Subject: Re: nnimap-list-pattern
Date: Fri, 30 Jun 2000 19:48:39 +1000 (GMT+1000) [thread overview]
Message-ID: <Pine.OSF.4.21.0006301946040.12739-100000@fox.uq.net.au> (raw)
In-Reply-To: <ilu4s6bv83h.fsf@localhost.localdomain>
On 30 Jun 2000, Simon Josefsson wrote:
> `nnimap-list-pattern' is a server variable, so this might not be
> appropriate if you have more than one nnimap server.
i only have one imap server, so i'm assuming i've only got nnimap server
> Are you sure the mailbox is named "inbox.www" and not "INBOX.www"?
well, when i move the files from ~/imap (which are all prefixed with
inbox.) everything is unky dory again.
next prev parent reply other threads:[~2000-06-30 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-30 0:45 nnimap-list-pattern Clinton Roy
2000-06-30 9:20 ` nnimap-list-pattern Simon Josefsson
2000-06-30 9:48 ` Clinton Roy [this message]
2000-06-30 10:10 ` nnimap-list-pattern John Prevost
2000-06-30 11:16 ` nnimap-list-pattern Simon Josefsson
2000-06-30 12:18 ` nnimap-list-pattern John Prevost
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=Pine.OSF.4.21.0006301946040.12739-100000@fox.uq.net.au \
--to=latte@uq.net.au \
/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).