From: "Georg C. F. Greve" <greve@gnu.org>
Cc: ding@gnus.org
Subject: Re: IMAP question
Date: 07 Dec 2000 11:02:36 +0100 [thread overview]
Message-ID: <m3bsuolfb7.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <3A2F4EDE.82301B07@rsasecurity.com>
[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]
|| On Thu, 07 Dec 2000 09:48:30 +0100
|| Simon Josefsson <sjosefsson@rsasecurity.com> wrote:
sj> Also you might want to look at `imap-log', perhaps there's a
sj> permission problem or something. (On Cyrus IMAPD servers,
sj> mailboxes are normally named "INBOX.whatever", rather than just
sj> "whatever". So unless your nnmail-split-fancy variable contain
sj> the "INBOX." prefix, nnimap can't save your mail.)
It seems that this was the cause of the problem. After putting a few
fancy splitting rules into nnimap-split-fancy, it did auto-create the
INBOX.mine mailbox as it should and I was able to read it. Thanks.
So now it seems I either have to change all my splitting rules to
something with INBOX.* or get myself another IMAP
server. Recommendations, anyone?
Regards,
Georg
P.S. Anyone have experience with a good & reliable utility to keep two
IMAP repositories/servers in sync even if one is offline for a while
and both might have been changed?
--
Georg C. F. Greve <greve@gnu.org>
the monthly GNU forum in English, German,
French, Spanish and Japanese. Check it out
at http://brave-gnu-world.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2000-12-07 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 22:53 Georg C. F. Greve
2000-12-07 6:44 ` Kai Großjohann
2000-12-07 7:20 ` Georg C. F. Greve
2000-12-07 8:48 ` Simon Josefsson
2000-12-07 10:02 ` Georg C. F. Greve [this message]
2000-12-09 3:17 ` Kai Großjohann
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=m3bsuolfb7.fsf@reason.gnu-hamburg \
--to=greve@gnu.org \
--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).