Gnus development mailing list
 help / color / mirror / Atom feed
From: hammond@csc.albany.edu (William F. Hammond)
Subject: Re: Return Receipts
Date: 08 Jan 2002 12:25:33 -0500	[thread overview]
Message-ID: <i7d70k21rm.fsf@pluto.math.albany.edu> (raw)
In-Reply-To: <iluwuyt67hz.fsf@extundo.com>

Simon Josefsson <jas@extundo.com> writes:

> hammond@csc.albany.edu (William F. Hammond) writes:
> 
> > Doesn't it pose risks if a user inadvertently opens spam?
> 
> DSN opens up to all kind of privacy threats, so it shouldn't be

DSN here corresponds to http://www.dsn.org/ , correct?

. . .

> >                               If so, the request needs to be made
> > plain to the user, but, pretty please, no prompt, or, at worst, a
> > user configurable return-receipt-request display-mode like 0=hide,
> > 1=show, 2=prompt.
> 
> Yes, a prompt like this could work.  A prompt is quite obtrusive
> though, maybe just a button that says the sender requested a
> notification, and you can press the button to send it.

I agree that an action-required prompt is very obtrusive.

A button would correspond to the value 1 below when emacs is running
with a viable mouse.  A more primitive form of 1 would be provided
for classical interactive terminals.

I intended to suggest a user-configurable variable such as this:

(defvar gnus-return-receipt-request-handling 0
"*Handling for DSN-related return-receipt requests in incoming items.
Meaning:  0 = Ignore all return-receipt requests.
          1 = Provide a styled display of the phrase
              \"Return Receipt Requested\"
              just after the displayed message headers and offer
              the function gnus-send-return-receipt in a non-obtrusive
              way.
          2 = Honor all return receipt requests.)


> One point of DSN is that the receipt is in machine readable format,
> multipart/report, a boiler-plate acknowledgement wouldn't achieve the
> same thing.

Agreed.

                                    -- Bill



  reply	other threads:[~2002-01-08 17:25 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 [this message]
2002-01-08 18:17                 ` Simon Josefsson
2002-01-19 20:58               ` Lars Magne Ingebrigtsen

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=i7d70k21rm.fsf@pluto.math.albany.edu \
    --to=hammond@csc.albany.edu \
    --cc=ding@gnus.org \
    --cc=hammond@math.albany.edu \
    /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).