From: Rupert Swarbrick <rswarbrick@gmail.com>
To: ding@gnus.org
Subject: Re: Poll time: IMAP client-side default match
Date: Tue, 01 Feb 2011 09:25:07 +0000 [thread overview]
Message-ID: <ii8jhm$p2c$1@dough.gmane.org> (raw)
In-Reply-To: <87lj20jy8s.fsf_-_@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So the problem is: If you have a split that you're using both for POP3
> and IMAP, then POP3 one needs a default split, while the IMAP shouldn't
> have one.
>
> Gnus deals with this by special-casing the IMAP case. It simply ignores
> "" (catch-all) rules.
>
> We could deal with this by:
>
> 1) Just document that IMAP client-side splits ignores the catch-all
> rule.
>
> 2) Something else. Ideas are welcome.
Couldn't you say that catch-all rules are followed if they exist on
IMAP? (And if there isn't one, stuff is left in INBOX, as you described)
I don't understand why this doesn't make sense...
Rupert
[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2011-02-01 9:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 21:35 Imap split, does not work (of course) Francis Moreau
2011-01-31 21:43 ` Richard Riley
2011-02-01 1:32 ` Lars Ingebrigtsen
2011-02-01 2:16 ` Poll time: IMAP client-side default match (was: Imap split, does not work (of course)) Lars Ingebrigtsen
2011-02-01 9:25 ` Rupert Swarbrick [this message]
2011-02-01 10:10 ` Poll time: IMAP client-side default match Lars Ingebrigtsen
2011-02-01 7:34 ` Imap split, does not work (of course) Francis Moreau
2011-02-01 8:04 ` Richard Riley
2011-02-01 8:27 ` Francis Moreau
2011-02-02 8:04 ` Francis Moreau
2011-02-01 19:21 ` Francis Moreau
2011-02-02 7:08 ` Eric S Fraga
2011-02-02 11:25 ` Richard Riley
2011-02-03 0:13 ` Michael Welsh Duggan
2011-02-03 8:47 ` Steinar Bang
2011-02-03 11:59 ` Richard Riley
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='ii8jhm$p2c$1@dough.gmane.org' \
--to=rswarbrick@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).