Gnus development mailing list
 help / color / mirror / Atom feed
From: Joseph Barillari <jbarilla@princeton.edu>
Subject: Re: DSN [PATCH]
Date: Wed, 24 Apr 2002 08:35:24 -0400	[thread overview]
Message-ID: <m3sn5lb7g3.fsf@washer.barillari.org> (raw)
In-Reply-To: <vpqn0vtl2v8.fsf@montrose.imag.fr> (Matthieu Moy's message of "Wed, 24 Apr 2002 14:04:11 +0200")

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

>>>>> "MM" == Matthieu Moy <Matthieu.Moy@imag.fr> writes:
    >>  I guess the solution is to write some commands for each of the
    >> boolean variables.  For the variable foo, it could be the
    >> command toggle-foo,

    MM> This is actually not more than a header in the mail, and I had
    MM> seen somewhere in the changelog of Gnus that a function
    MM> inserting it had already been introduced a few month ago.

What was it called? I grepped ChangeLog for "Return-Receipt-To" and
"DSN" and couldn't find it.

    MM> If you want this permanent, add this header like any other
    MM> (X-Face, ...) with posting-styles, gnus-pers, or any other.

Should I add the header as an internal note? That is to say,
something that Gnus will strip out before it sends the message? (As
with the <\# part type ...> tags that Gnus inserts when files are attached?

    MM> Please, do not make something that will post DSN to mailing
    MM> lists :-(.

I believe the MTAs are responsible for making sure the DSN-requester
doesn't get flooded with messages. The Exim FAQ cited the ambiguities
in the DSN-related RFCs on this matter as their reason for not
including it. [0] 

As empirical `proof,' I have not, to my knowledge, received a flood of
receipts by posting to a mailing list with DSN enabled -- yet.

[0] <http://exim.directnet.ru/exim-html-4.00/doc/html/FAQ_6.html>

--Joe

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

  reply	other threads:[~2002-04-24 12:35 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 [this message]
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
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=m3sn5lb7g3.fsf@washer.barillari.org \
    --to=jbarilla@princeton.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).