Gnus development mailing list
 help / color / mirror / Atom feed
From: manuel carro <mcarro@fi.upm.es>
To: ding@gnus.org
Subject: Accessing all incoming mails, checking for network connection, changes in message status
Date: Fri, 23 Jul 2010 15:07:32 +0100	[thread overview]
Message-ID: <7saapinvff.fsf@fi.upm.es> (raw)


Dear GNUSers,

I have been using GNUS for some months now and there are some things I
would like to know how to do.

[1] 

I process a lot of mail and right now I have a series of split rules
which divert the mail into some 260 different groups.  However, when I
read mail (I download it to my laptop using IMAP, then do all processing
on the laptop) I am more or less forced to go through all the groups
with active messages and process them.  I used to have a virtual groups
which gathered all active messages, but in the end I had to go to the
group the message was in to read and answer it so that the answer was
stored in the group where the original message was stroed (I set up the
GCC: field so that mails go to the group where I am when I answer).

Wat I would like is to know how to do is:

(a) Set up Gnus variables / options (or what additional functions I
could add) so that incoming mail goes to a single group, and from there
I can respool it to other groups according to a set of spooling /
splitting rules.  I think that the best setup would be to be suggested a
group to respool which I could then edit in the command line, but this
can probably be made with other pieces from the GNUs code.

(b) It would be great if, after respooling, I could almost automatically
(or with minor effort) switch to the group where the message was
respooled (to, e.g., answer from there) and when quitting the group,
appear again in the group where all the messages are stored.


[2]

I work offline often (for example, I am writing this message while in a
plane) and I use SMTP from within GNUS.  I have a function which
switches from queing to non-queieng messages and vice-versa, and takes
care of sending the stored messages when selecting the non-queuing
state.  But I have to remember to make that switch.  Is there any way to
cleanly check that there is connection?  I would like to do something
like:

(defun my-gnus-mail-send-message ()
    (store-message)
    (if (connection-ok smtpmail-default-smtp-server)
        (send-all-mails)
    )
)


Also, unrelated with the above, I am intermittently experiencing small
problems with mails changing status - i.e., unread mails which move to
the "O[ld]" state or to the "r[ead]" state, and old / already read
messages which appear again as new.  Does any of you exeperience
something similar.  Does that happen to any of you?  I usually run the
version in git.

Cheers and thank you!
-- 
+------------------------------------------------------------------------------+
|  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-23 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 14:07 manuel carro [this message]
2010-07-26 21:13 ` Ted Zlatanov
2010-07-27 12:47   ` Manuel Carro
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=7saapinvff.fsf@fi.upm.es \
    --to=mcarro@fi.upm.es \
    --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).