Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@OCE.ORST.EDU>
Cc: ding@gnus.org
Subject: Re: [ANNOUNCE] NNDiary, a diary backend for Gnus.
Date: 10 Aug 2001 15:25:39 -0700	[thread overview]
Message-ID: <3d6z5z8c.fsf@oce.orst.edu> (raw)
In-Reply-To: <vafsnezva23.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 11 Aug 2001 00:12:36 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> appointment?) item to another person.  In our working group, we
> extensively use shared IMAP folders for cooperation.  I wonder if some
> kind of nndiary-like functionality could be had with IMAP...

Hi Kai,

This works for me:

;; with an appropriate entry in .procmail...
(setq nndiary-mail-sources '((imap :server "imap.oce.orst.edu" 
:mailbox "mail/nndiary" :dontexpunge t)))

However, it is maybe a little cruder than you would like.   The
"dontexpunge" means that it can be left on the IMAP server for other
users to fetch.   However, is it now flagged as read?  Maybe thats a
problem for other users who only fetch unread.  How does gnus decide
what articles to get from the IMAP server?  Does it keep track of
read/unread, or does it read the flags from the server?



But I think you need to bring the article to your machine for nndiary
to be able to have it be marked "unread" whenever it is coming due.  I
guess you could mark it unread on the IMAP server, but only the first
person to read it would get alerted.  Not good I guess...



-- 
Jody M. Klymak               mailto:jklymak@oce.orst.edu
College of Oceanic and Atmospheric Sicences
Oregon State University, Corvallis, OR, 97331  



  reply	other threads:[~2001-08-10 22:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 16:12 Didier Verna
2001-08-09  1:15 ` Colin Walters
2001-09-04  9:06   ` Didier Verna
2001-08-09  7:20 ` Jody Klymak
2001-08-09 11:14   ` Kai Großjohann
2001-08-09 15:14     ` Jody Klymak
2001-09-04  9:06   ` Didier Verna
2001-08-09 18:51 ` Jody Klymak
2001-08-10 19:10   ` Dan Nicolaescu
2001-08-10 19:14     ` Karl Kleinpaste
2001-08-10 21:07       ` Dan Nicolaescu
2001-08-10 21:49       ` Kai Großjohann
2001-08-10 22:12       ` Kai Großjohann
2001-08-10 22:25         ` Jody Klymak [this message]
2001-08-10 22:31           ` Jody Klymak
2001-08-11  0:04           ` Kai Großjohann
2001-08-11  0:27             ` Jody Klymak
2001-08-11 12:13               ` Kai Großjohann
2001-08-11 18:10                 ` Jody Klymak
2001-08-11 20:04                   ` Jody Klymak
2001-08-11 20:54                     ` Kai Großjohann
2001-09-04  8:13                       ` Didier Verna
2001-09-04 12:29                         ` Kai Großjohann
2001-09-04 15:49                           ` Paul Jarc
2001-09-04  8:09                   ` Didier Verna
2001-08-11 18:51                 ` Amos Gouaux
2001-09-04  8:03               ` Didier Verna
2001-08-11 18:50             ` Amos Gouaux
2001-08-11 20:52               ` Kai Großjohann
2001-08-10 22:50         ` Dan Nicolaescu
2001-08-13 18:29         ` Dan Nicolaescu
2001-09-04  9:06     ` Didier Verna
2001-09-04  9:06   ` Didier Verna
2001-09-04 12:25     ` Kai Großjohann
2001-09-04 15:15     ` Jody Klymak
2001-09-04 16:37       ` Kai Großjohann
2001-08-24 19:55 ` [ANNOUNCE] NNDiary to diary Jody Klymak

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=3d6z5z8c.fsf@oce.orst.edu \
    --to=jklymak@oce.orst.edu \
    --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).