From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Return Receipts
Date: Sat, 19 Jan 2002 21:58:16 +0100 [thread overview]
Message-ID: <m3elkmukgn.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <iluwuyt67hz.fsf@extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> DSN opens up to all kind of privacy threats, so it shouldn't be
> enabled by default. OTOH I think it might be useful in some
> situations (especially if you are in a Windows environment where
> someone expects you to return a receipt).
I've given RFC2298 a quick glance, and I thought about it a few
seconds more, and I just don't feel that this is something that users
will want to use. I certainly wouldn't. So I'm not going to
implement this, but if you (or someone else :-) wants to implement
this, it'd be fine by me.
(Just to make sure you hadn't already implemented this, I grepped
through the sources for "notification", and I see there's a function
for inserting a Disposition-Notification-To header, but not much
more. When fetching mail, Gnus should probably be parsing these
receipts, and marking, er, archived messages as having received
notification that they have been received? Or something?)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-01-19 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86pu4r5cd4.fsf@jamestown.21stcentury.net>
[not found] ` <ilur8p7xe2h.fsf@extundo.com>
[not found] ` <86pu4q3ilk.fsf@jamestown.21stcentury.net>
[not found] ` <m3d70qznth.fsf@quimbies.gnus.org>
[not found] ` <ilug05lvpzl.fsf@extundo.com>
2002-01-05 17:42 ` Lars Magne Ingebrigtsen
2002-01-07 23:18 ` William F. Hammond
2002-01-07 23:55 ` Simon Josefsson
2002-01-08 17:25 ` William F. Hammond
2002-01-08 18:17 ` Simon Josefsson
2002-01-19 20:58 ` Lars Magne Ingebrigtsen [this message]
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=m3elkmukgn.fsf@quimbies.gnus.org \
--to=larsi@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).