From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Envelope sender lost from sending after gnus-draft-edit-message
Date: Sun, 02 Mar 2003 17:47:05 +0100 [thread overview]
Message-ID: <m3vfz1zpfa.fsf@defun.localdomain> (raw)
In-Reply-To: <l6v4r6ml1zt.fsf@williams.mc.vanderbilt.edu>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
"Andrew A. Raines" <drew@poured.net> writes:
> How did earlier Gnuses handle this issue?
Basically the same way as now: It passes the envelope sender to sendmail
with '-f' on the command line.
If `message-sendmail-envelope-from' is nil (the default), nothing should
have changed -- it'll use `message-make-address' in the envelope.
> It seems like this only started recently.
I don't see how `message-sendmail-envelope-from' could make anything
different with the default setting. But you could try this patch and
see if it changes anything:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: message.el.diff --]
[-- Type: text/x-patch, Size: 473 bytes --]
--- gnus/lisp/message.el Sat Mar 1 15:28:48 2003
+++ message.el Sun Mar 2 17:28:12 2003
@@ -3559,7 +3559,7 @@
;; But some systems are more broken with -f, so
;; we'll let users override this.
(if (null message-sendmail-f-is-evil)
- (list "-f" (message-sendmail-envelope-from)))
+ (list "-f" (message-make-address)))
;; These mean "report errors by mail"
;; and "deliver in background".
(if (null message-interactive) '("-oem" "-odb"))
[-- Attachment #3: Type: text/plain, Size: 346 bytes --]
Hmm, maybe your sendmail just doesn't like the '-f' option -- the
comment in message.el suggests that this is sometimes the case:
;; Always specify who from,
;; since some systems have broken sendmails.
;; But some systems are more broken with -f, so
;; we'll let users override this.
Does '-f' work if you use sendmail from the command line?
next prev parent reply other threads:[~2003-03-02 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 23:46 Jesper Harder
2003-03-02 0:25 ` Andrew A. Raines
2003-03-02 0:50 ` Jesper Harder
2003-03-02 6:24 ` Andrew A. Raines
2003-03-02 16:47 ` Jesper Harder [this message]
2003-03-02 21:13 ` Proper Gnus rebuilding technique? (was: Envelope sender lost from sending after gnus-draft-edit-message) Andrew A. Raines
2003-03-02 22:19 ` Proper Gnus rebuilding technique? Jesper Harder
2003-03-02 23:32 ` Frank Haun
2003-03-02 23:47 ` Jesper Harder
2003-03-03 0:47 ` Michael Shields
2003-03-03 22:24 ` Frank Haun
2003-03-31 17:48 ` Lars Magne Ingebrigtsen
2003-03-03 0:01 ` Frank Haun
-- strict thread matches above, loose matches on Subject: below --
2003-02-11 17:03 Envelope sender lost from sending after gnus-draft-edit-message Drew Raines
2003-02-22 21:00 ` Lars Magne Ingebrigtsen
2003-02-23 21:14 ` Andrew A. Raines
2003-02-23 21:35 ` Jesper Harder
2003-02-24 5:29 ` Andrew A. Raines
2003-03-01 22:11 ` Andrew A. Raines
2003-02-24 7:03 ` Kai Großjohann
2003-02-24 16:58 ` Andrew A. Raines
2003-02-24 19:09 ` Andrew A. Raines
2003-02-24 19:42 ` Kai Großjohann
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=m3vfz1zpfa.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).