From: "Austin F. Frank" <austin.frank@gmail.com>
To: ding@gnus.org
Subject: Re: Latest gnus mixup separate IMAP servers
Date: Wed, 08 Sep 2010 15:12:26 -0400 [thread overview]
Message-ID: <m0k4mwdp7p.fsf@gmail.com> (raw)
In-Reply-To: <m3fwxk5gjd.fsf@quimbies.gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
On Wed, Sep 08 2010, Lars Magne Ingebrigtsen wrote:
> Bjørn Mork <bjorn@mork.no> writes:
>> Looks like some of the recent changes makes gnus confuse different
>> IMAP servers. Opening the INBOX of one server shows the other, and
>> existing marks are messed up.
> Huh. I didn't think any of the nnimap cleanups I did before deciding
> to do a rewrite instead would have any functional effect. Anybody
> else seeing this?
I've just added a second IMAP server for the first time, so this could
be user error instead of problems with the recent changes.
I'm seeing a strange problem where my nnimap-split-rule is being applied
to folders on the wrong server.
#v+
(add-to-list 'gnus-secondary-select-methods
'(nnimap "serverA"
(nnimap-address "mail.serverA.com")
(nnimap-stream ssl)))
(add-to-list 'gnus-secondary-select-methods
'(nnimap "serverB"
(nnimap-address "mail.serverB.com")
(nnimap-stream ssl)))
(setq nnimap-split-rule
'(("serverA" ("INBOX" nnimap-split-fancy)))
nnimap-split-fancy
'(any "\\.edu" "mail.academic"))
#v-
With this setup, I'm seeing mail from serverB being sorted into
nnimap+serverB:mail.academic, which I don't actually want to happen.
Any hints on how to diagnose whether this is my fault or related to
recent changes?
Thanks,
/au
--
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-09-08 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 8:46 Bjørn Mork
2010-09-08 16:47 ` Lars Magne Ingebrigtsen
2010-09-08 18:11 ` Steinar Bang
2010-09-08 19:12 ` Austin F. Frank [this message]
2010-09-10 23:31 ` Lars Magne Ingebrigtsen
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=m0k4mwdp7p.fsf@gmail.com \
--to=austin.frank@gmail.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).