Gnus development mailing list
 help / color / mirror / Atom feed
From: Manuel Carro <mcarro@fi.upm.es>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Accessing all incoming mails, checking for network connection, changes in message status
Date: Tue, 27 Jul 2010 14:47:05 +0200	[thread overview]
Message-ID: <7smxtdrt12.fsf@fi.upm.es> (raw)
In-Reply-To: <87eieqx7xm.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 26 Jul 2010 16:13:57 -0500")


Dear Ted,

First of all thanks for your answers and the time spent.

> 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?

I have a virtual group which puts together all mail, so that when I
enter the group I see all unread and ticked articles.  But these
articles have already been spooled to the corresponding groups.  What I
would like is to receive all mail in a single group (that is easy) and,
as I read the messages, respool them to other groups using a set of
rules and "B t" (basically the ones I have now).  It is the second part I did not
manage to find how to do, as it seems that at the moment I set up
splitting rules the mail start to be split.


> I don't think that's available like that right now.  But the Gnus Agent
> is supposed to help with connected/disconnected transitions; have you
> looked at it?

I haven't.  Thanks for the suggestion.


> I would perfonally set up a local SMTP server that will queue my mails
> until the network connection is up again.  But that's probably too
> much for most users.

I used to do that (with Postfix), but at some point I found myself using
at least three different setups (a laptop, a desktop machine, and a
vitual machine running on Mac OS X) so I decided no to set up three
different SMTP servers and use a configuration which basically runs in
user-space and which works unchanged.  I of course synchronize my
personal stuff (using unison).


> This indicates article marks are inconsistent.  Is this over IMAP or
> another protocol?  Could the server be modifying article numbers behind
> Gnus' back?

It is over IMAP, but use IMAP to copy the mail messages over to my
machine and I the processing is done locally after my mail has been
downloaded.  I do not think the article numbers are being modified,
then.

Thanks again,
-- 
+------------------------------------------------------------------------------+
|  Manuel Carro --- Facultad de Informática -- U. Politécnica de Madrid (UPM)  |
|       Campus de Montegancedo --- E-28660 Boadilla del Monte --- Spain        |
|                Phone: +34-913363747 --- FAX: +34-913363669                   |



  reply	other threads:[~2010-07-27 12:47 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 [this message]
2010-08-03 19:07     ` Ted Zlatanov
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=7smxtdrt12.fsf@fi.upm.es \
    --to=mcarro@fi.upm.es \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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).