From: Joseph Barillari <jbarilla@princeton.edu>
Subject: Re: DSN [PATCH]
Date: Tue, 23 Apr 2002 16:28:42 -0400 [thread overview]
Message-ID: <m37kmy6txh.fsf_-_@washer.barillari.org> (raw)
In-Reply-To: <m3hem5uoqv.fsf@washer.barillari.org> (Joseph Barillari's message of "Sun, 21 Apr 2002 10:10:00 -0400")
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
I've attached the DSN patch w.r.t. the latest Gnus source in CVS,
including documentation. How might I go about adding a control to
quickly switch the option on or off at composition time, as Simon
Josefsson suggested? I leave it on all the time, because I catch the
flood of receipts with procmail, but I assume this isn't everybody's
preferred behavior.
--Joe
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1: DSN patch --]
[-- Type: text/x-patch, Size: 3484 bytes --]
diff -urN -x CVS gnus/lisp/message.el mygnus/lisp/message.el
--- gnus/lisp/message.el Sat Apr 20 22:42:45 2002
+++ mygnus/lisp/message.el Tue Apr 23 16:06:03 2002
@@ -265,6 +265,26 @@
:group 'message-mail
:type 'boolean)
+(defcustom message-sendmail-use-dsn-failure nil
+ "If this variable is non-nil, ask the MTA for notification by mail
+ of failed delivery. Note that only some MTAs (namely recent versions
+ of Sendmail) support Delivery Status Notification."
+ :group 'message-sending
+ :type 'boolean)
+
+(defcustom message-sendmail-use-dsn-delay nil
+ "If this variable is non-nil, ask the sendmail for notification by mail of
+ delayed delivery."
+ :group 'message-sending
+ :type 'boolean)
+
+(defcustom message-sendmail-use-dsn-success nil
+ "If this variable is non-nil, ask sendmail for notification by mail
+ of successful delivery."
+ :group 'message-sending
+ :type 'boolean)
+
+
(defcustom message-generate-new-buffers 'unique
"*Non-nil means create a new message buffer whenever `message-setup' is called.
If this is a function, call that function with three parameters: The type,
@@ -3005,6 +3025,20 @@
;; we'll let users override this.
(if (null message-sendmail-f-is-evil)
(list "-f" (message-make-address)))
+ ;; Insert DSN-related command line arguments
+ (if (or message-sendmail-use-dsn-failure
+ message-sendmail-use-dsn-delay
+ message-sendmail-use-dsn-success)
+ (list
+ (concat "-N"
+ (if message-sendmail-use-dsn-failure "failure")
+ (if (and message-sendmail-use-dsn-failure
+ message-sendmail-use-dsn-delay ) ",")
+ (if message-sendmail-use-dsn-delay "delay")
+ (if (and message-sendmail-use-dsn-success
+ message-sendmail-use-dsn-delay ) ",")
+ (if message-sendmail-use-dsn-success "success")
+ )))
;; These mean "report errors by mail"
;; and "deliver in background".
(if (null message-interactive) '("-oem" "-odb"))
diff -urN -x CVS gnus/texi/message.texi mygnus/texi/message.texi
--- gnus/texi/message.texi Mon Apr 8 17:58:00 2002
+++ mygnus/texi/message.texi Tue Apr 23 15:56:57 2002
@@ -1242,6 +1242,27 @@
The lower bound of message size in characters, beyond which the message
should be sent in several parts. If it is nil, the size is unlimited.
+@item message-sendmail-use-dsn-failure
+@vindex message-sendmail-use-dsn-failure
+Set this to non-@code{nil} to tell Sendmail to request downstream MTAs
+to generate DSN (RFC 1891) response messages if delivery fails. Note
+that this does not work with all versions of Sendmail. Support from
+downstream MTAs varies by vendor and product.
+
+@item message-sendmail-use-dsn-success
+@vindex message-sendmail-use-dsn-success
+Set this to non-@code{nil} to tell Sendmail to request downstream MTAs
+to generate DSN (RFC 1891) response messages if delivery
+succeeds. Note that this does not work with all versions of
+Sendmail. Support from downstream MTAs varies by vendor and product.
+
+@item message-sendmail-use-dsn-delay
+@vindex message-sendmail-use-dsn-delay
+Set this to non-@code{nil} to tell Sendmail to request downstream MTAs
+to generate DSN (RFC 1891) response messages if delivery is
+delayed. Note that this does not work with all versions of
+Sendmail. Support from downstream MTAs varies by vendor and product.
+
@end table
[-- Attachment #2.2: Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2002-04-23 20:28 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 ` Joseph Barillari [this message]
2002-04-24 11:31 ` DSN [PATCH] 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
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=m37kmy6txh.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).