Gnus development mailing list
 help / color / mirror / Atom feed
From: Joseph Barillari <jbarilla@princeton.edu>
Subject: Re: DSN [PATCH]
Date: Wed, 24 Apr 2002 09:43:21 -0400	[thread overview]
Message-ID: <m33cxl1abq.fsf@washer.barillari.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204241523350.656-100000@yxa.extundo.com> (Simon Josefsson's message of "Wed, 24 Apr 2002 15:26:40 +0200 (CEST)")

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

>>>>> "SJ" == Simon Josefsson <jas@extundo.com> writes:

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

    SJ> I think everyone agress with this.  However, Gnus should be
    SJ> able to support DSN/DNT if the user wants to enable it for a
    SJ> certain message (or for all outgoing messages).  But it should
    SJ> not be the default.

That's what mutt does. The option is off by default, but can be
enabled by editing .muttrc. From `man muttrc`:

       dsn_notify
              Type: string
              Default: ""

              Note:  you  should  not  enable this unless you are
              using Sendmail 8.8.x or greater.

              This variable sets the request for  when  notifica­
              tion  is  returned.  The string consists of a comma
              separated list (no spaces!) of one or more  of  the
              following:  never,  to  never request notification,
              failure, to request  notification  on  transmission
              failure,  delay,  to be notified of message delays,
              success, to be notified of successful transmission.

              Example: set dsn_notify="failure,delay"

       dsn_return
              Type: string
              Default: ""

              Note:  you  should  not  enable this unless you are
              using Sendmail 8.8.x or greater.

              This variable controls how much of your message  is
              returned  in DSN messages.  It may be set to either
              hdrs to return just the message header, or full  to
              return the full message.

              Example: set dsn_return=hdrs

--Joe

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

  reply	other threads:[~2002-04-24 13:43 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 [this message]
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=m33cxl1abq.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).