From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Accessing all incoming mails, checking for network connection, changes in message status
Date: Tue, 03 Aug 2010 14:07:15 -0500 [thread overview]
Message-ID: <87bp9jcy70.fsf@lifelogs.com> (raw)
In-Reply-To: <7smxtdrt12.fsf@fi.upm.es>
On Tue, 27 Jul 2010 14:47:05 +0200 Manuel Carro <mcarro@fi.upm.es> wrote:
>> Virtual groups should do this. Otherwise you're reinventing the same
>> functionality. So if the only problem is that the GCC field is wrong,
>> let's fix that. Or is there another reason why virtual groups are not
>> what you want?
MC> I have a virtual group which puts together all mail, so that when I
MC> enter the group I see all unread and ticked articles. But these
MC> articles have already been spooled to the corresponding groups. What I
MC> would like is to receive all mail in a single group (that is easy) and,
MC> as I read the messages, respool them to other groups using a set of
MC> rules and "B t" (basically the ones I have now). It is the second part I did not
MC> manage to find how to do, as it seems that at the moment I set up
MC> splitting rules the mail start to be split.
Yeah, splitting rules are not meant to be optional. But they can call
ELisp! So make a function that normally returns the "main" group, but
make it operate differently (returning nil) when invoked interactively.
(defvar pass-through nil)
(defun my-special-splitter ()
(if pass-through
nil
"main group name here"))
Now you just have to a) insert this function in your split rules before
anything else, and b) advise or override `B t' inside a lambda that sets
pass-through to t before the call and sets it back to nil afterwards.
Look in the splitting rules section of the manual for more details.
It's not too bad.
>> This indicates article marks are inconsistent. Is this over IMAP or
>> another protocol? Could the server be modifying article numbers behind
>> Gnus' back?
MC> It is over IMAP, but use IMAP to copy the mail messages over to my
MC> machine and I the processing is done locally after my mail has been
MC> downloaded. I do not think the article numbers are being modified,
MC> then.
OK. I'm not sure what's going on then.
Ted
next prev parent reply other threads:[~2010-08-03 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 14:07 manuel carro
2010-07-26 21:13 ` Ted Zlatanov
2010-07-27 12:47 ` Manuel Carro
2010-08-03 19:07 ` Ted Zlatanov [this message]
2010-08-09 10:44 ` Manuel Carro
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=87bp9jcy70.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).