Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: asjo@koldfront.dk (Adam Sjøgren)
Cc: ding@gnus.org
Subject: Re: Snoozing a message in gnus?
Date: Mon, 10 Nov 2014 15:49:51 +0100	[thread overview]
Message-ID: <m2mw7zyusw.fsf@krugs.de> (raw)
In-Reply-To: <87zjbzdulx.fsf@topper.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Mon, 10 Nov 2014 14:59:38 +0100")

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]


First of all, it is great to get this discussion on this topic.

asjo@koldfront.dk (Adam Sjøgren) writes:

> Ted writes:
>
>> You can't add a header to most backends, especially IMAP, because they
>> don't support article editing.

Snoozing should work on all (probably except nntp as it is read only?)
backends. But what about the approach which Mailbox is using,
i.e. moving the messages from the inbox into another folder (called "Later"?), and storing
metadata (which folder the message is from, when it is due, ...) in the
registry? The querying of the registry could be timed (every x minutes),
and when due, the message could be moved back to it's original location.

The advantage of this approach is that snoozed messages can also be
checked from other mail programs (I am thinking about an imap backend
for gmail), although only with missing information on due dates / times.

Cheers,

Rainer

>
> How do you define "most"?
>
> Isn't nnimap and the special ones (nnvirtual, nnir, nnmairix) the only
> ones that don't?
>
> nnmbox, nnbabyl, nnmh, nnmaildir, nnfolder, and nnml all do, right?
>
>
>   Nit picking, as ever,
>
>     Adam

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]

  reply	other threads:[~2014-11-10 14:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  8:43 Rainer M Krug
2014-11-07 11:04 ` Eric Abrahamsen
2014-11-07 12:56   ` Ted Zlatanov
2014-11-11  2:27     ` Eric Abrahamsen
2014-11-07 15:09   ` Rainer M Krug
2014-11-07 11:12 ` Tassilo Horn
2014-11-07 13:07   ` Xavier Maillard
2014-11-07 15:37   ` Trevor Murphy
2014-11-07 22:20     ` Peter Münster
2014-11-10 13:49     ` Ted Zlatanov
2014-11-10 13:59       ` Adam Sjøgren
2014-11-10 14:49         ` Rainer M Krug [this message]
2014-11-12  1:00           ` Dan Christensen
2014-12-08 16:59             ` Ted Zlatanov
2014-11-10 14:06       ` Tassilo Horn
2014-11-10 20:04         ` Ted Zlatanov
2014-11-10 22:26           ` Trevor Murphy
2014-11-11  1:23             ` Ted Zlatanov
2014-11-10 23:33           ` Trevor Murphy
2014-11-11  2:13             ` Eric Abrahamsen
2014-11-10 22:27         ` Trevor Murphy
2015-01-26  4:34 ` Lars Ingebrigtsen
2015-01-26  8:39   ` Rainer M Krug
2015-01-27  0:56     ` Lars Ingebrigtsen
2015-01-27  1:53       ` Eric Abrahamsen
2015-01-27  8:12         ` Rainer M Krug

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=m2mw7zyusw.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=asjo@koldfront.dk \
    --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).