Gnus development mailing list
 help / color / mirror / Atom feed
From: Joseph Barillari <jbarilla@princeton.edu>
Cc: ding@gnus.org
Subject: Re: DSN [PATCH]
Date: Wed, 24 Apr 2002 12:17:50 -0400	[thread overview]
Message-ID: <m38z7dt6j5.fsf@washer.barillari.org> (raw)
In-Reply-To: <vafofg9jfb3.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 24 Apr 2002 17:18:24 +0200")

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

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
    >>  This is actually not more than a header in the mail, and I had
    >> seen somewhere in the changelog of Gnus that a function
    >> inserting it had already been introduced a few month ago.

    KG> Hm.  The code I saw invoked sendmail with various options,
    KG> depending on some Emacs variables.  No message headers
    KG> appeared to be involved.

    KG> If it is possible to speficy that I want DSN by including a
    KG> header in the outgoing message, then surely Gnus should use
    KG> that, rather than kludging in the DSN command line arguments
    KG> when invoking sendmail.  Right?

Matthieu Moy pointed me to the following entry in the changelog:
2002-01-05  Simon Josefsson  <jas@extundo.com>
            (snip)
        (message-insert-disposition-notification-to): New function.

According to the manual, this is:
*Disposition Notifications - RFC 2298*
     Message Mode is able to request notifications from the receiver.
     (and)
`C-c M-n'
     Insert a request for a disposition notification.
     (`message-insert-disposition-notification-to').  This means that
     if the recipient support RFC 2298 she might send you a
     notification that she received the message.


Disposition-Notification-To, according to RFC 2298, is implemented by
inserting a standard RFC822 header into the message. It is therefore
the responsibility of the MUA.

Conversely, according to [0], DSN can be requested from sendmail
either in a commandline argument or in the SMTP conversation. I don't
think it can be activated by inserting a header -- DSN is invoked at
the mail transport level, not by the message content.

--Joe

[0] http://www.sendmail.org/~ca/email/sm8.8.new.html

[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]

  reply	other threads:[~2002-04-24 16:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 11:07 DSN Joseph Barillari
2002-04-21 13:16 ` DSN Simon Josefsson
2002-04-21 14:10   ` DSN Joseph Barillari
2002-04-23 20:28     ` DSN [PATCH] Joseph Barillari
2002-04-24 11:31       ` Kai Großjohann
2002-04-24 12:04         ` Matthieu Moy
2002-04-24 12:35           ` Joseph Barillari
2002-04-24 15:57             ` Simon Josefsson
     [not found]               ` <m38z7dawqy.fsf@washer.barillari.org>
2002-04-24 17:50                 ` Simon Josefsson
2002-04-24 19:50                   ` Joseph Barillari
2002-04-24 20:28                     ` Simon Josefsson
2002-04-24 20:40                       ` Joseph Barillari
2002-04-24 20:52                         ` Simon Josefsson
2002-04-24 21:07                           ` Joseph Barillari
2002-04-24 13:26           ` Simon Josefsson
2002-04-24 13:43             ` Joseph Barillari
2002-04-24 15:18           ` Kai Großjohann
2002-04-24 16:17             ` Joseph Barillari [this message]
2002-04-24  9:21 ` DSN Matthieu Moy

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=m38z7dt6j5.fsf@washer.barillari.org \
    --to=jbarilla@princeton.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).