Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and new mail notification
Date: Mon, 27 Dec 2010 18:47:48 +0100	[thread overview]
Message-ID: <87oc875cqj.fsf@tux.homenetwork> (raw)
In-Reply-To: <ifafkv$8qa$1@quimby.gnus.org>

Richard Riley <rileyrg@googlemail.com> writes:

> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>
>> Richard Riley <rileyrg@googlemail.com> writes:
>>
>>> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>>>
>>>> Richard Riley <rileyrg@googlemail.com> writes:
>>>>
>>>>> Yuri D'Elia <wavexx@users.sf.net> writes:
>>>>>
>>>>>> On Sun, 26 Dec 2010 00:19:42 +0100, Richard Riley wrote:
>>>>>>>> As soon as you use splitting or virtual groups, an external process
>>>>>>>> becomes useless (for instance, I have several rules that split messages
>>>>>>>> into groups that I ignore).
>>>>>>>
>>>>>>> Not if you dont use the demon and then split when you hit g. In other
>>>>>>> words you only fetch your mail when gnubiff or something similar tells
>>>>>>> you that you have new mail.
>>>>>>
>>>>>> Concrete example: if splitting includes spam rules, gnubiff will notify
>>>>>> you of spam too.
>>>>>>
>>>>>
>>>>> Yes that is most certainly true. Since I use googlemail I'm kind of
>>>>> spoiled as their spam filtering server side is pretty good these days
>>>>> (that and my spam-split set up doesnt work anymore on NoGnus) and so I
>>>>> turned off client side "spam-split"ting.
>>>>
>>>> If you use gmail, you can have easy mail notification with:
>>>>
>>>> https://mail.google.com/mail/feed/atom
>>>>
>>>> It give you an xml buffer you have to parse.
>>>>
>>>> A library exists on emacswiki for this, don't remember the name, it
>>>> didn't work for me so i wrote small code for this for my personal use, i
>>>> can send it if interested.
>>>> Of course if one use gnus-demon, it's non--sense to use this.
>>>
>>> Just as an FYI to the OP if new to Gnus, I have found the best set up
>>> for me with Gnus is dovecot locally fed by offlineimap which is run as a
>>> cron job every half hour or so.
>> I use here offlineimap.el that is started each time i start gnus.
>> http://julien.danjou.info/offlineimap-el.html
>> I think that coupled with a gmail notification is better than a
>> cronjob.
>
> I dont think it is since the benefit of my way is I dont need gnus
> running to see email notifications.
Me too ;-) See above

Gnus is stopped.

1) I call async https://mail.google.com/mail/feed/atom every five
minutes.

2) When i am notified of a new email, i run Gnus who run offlineimap.

> Emacs/Gnus just dont do "async" well
> and for me its not its job to run offlineimap which isnt necessarily the
> quickest anyway. Still horses for courses and an interesting mix of
> approaches ;)

>>
>>> nnir search works really well and of
>>> course there are then no performance or bandwidth issues with Gnus
>>> talking imap with remote gmail servers. Plus you have a local copy of
>>> your mail. Here is one "how to" for the set up:
>>>
>>> http://sachachua.com/blog/2008/05/geek-how-to-use-offlineimap-and-the-dovecot-mail-server-to-read-your-gmail-in-emacs-efficiently/
>>> http://tinyurl.com/26cwmok
>>
>> I have also started to use dovecot/offlineimap, however it's was not so
>> easy to configure dovecot, especially the mail_location, what is
>> described in sacha blog is deprecated.
>>
>> So here i use for gmail:
>> ,----[ dovecot config ]
>> | mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=~/Maildir/INBOX
>> `----
>> Hope that's help
>
> I use multiple virtual users to handle my different gmail accounts. I
> can share the set up if anyone is interested.

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

  reply	other threads:[~2010-12-27 17:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.26.1293233609.7272.info-gnus-english@gnu.org>
2010-12-25 13:25 ` e20100633
2010-12-26 18:26   ` Philipp Haselwarter
2010-12-26 18:59     ` Philipp Haselwarter
2010-12-25 20:31 ` Richard Riley
2010-12-25 21:55   ` Tassilo Horn
2010-12-25 22:56   ` Yuri D'Elia
     [not found]   ` <mailman.13.1293317806.24913.info-gnus-english@gnu.org>
2010-12-25 23:19     ` Richard Riley
2010-12-26 16:22       ` Yuri D'Elia
     [not found]       ` <mailman.1.1293380566.6185.info-gnus-english@gnu.org>
2010-12-27  8:11         ` Richard Riley
2010-12-27  9:25           ` Thierry Volpiatto
     [not found]           ` <mailman.2.1293441979.18751.info-gnus-english@gnu.org>
2010-12-27 13:30             ` Richard Riley
2010-12-27 15:39               ` Philipp Haselwarter
2010-12-27 16:04               ` Thierry Volpiatto
     [not found]               ` <mailman.8.1293465927.24495.info-gnus-english@gnu.org>
2010-12-27 16:42                 ` Richard Riley
2010-12-27 17:47                   ` Thierry Volpiatto [this message]
     [not found]                   ` <mailman.19.1293472126.24495.info-gnus-english@gnu.org>
2010-12-27 18:11                     ` Richard Riley
2010-12-27 19:09                       ` Thierry Volpiatto
2010-12-24 23:33 Yuri D'Elia
2010-12-25 13:10 ` Philipp Haselwarter
2010-12-25 15:26   ` Yuri D'Elia
2010-12-25 21:52     ` Tassilo Horn
2010-12-26 20:11 ` Yuri D'Elia
2011-01-02 12:02   ` Philipp Haselwarter

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=87oc875cqj.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=info-gnus-english@gnu.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).