overriding the sender header

overriding the sender header

[Steinar Bang]

Platform: Dell Inspiron 3500 laptop, SuSE linux 6.3, Xemacs 20.4, Gnus 5.8.3

Is the envelope header set from the sender: field?  Or is it set by
sendmail? 

I've been grepping through the emacs lisp code.

It looks like I have to defadvice message-make-sender or something, to 
be able to lose the Sender: header (which I do think is a good idea
anyways, no matter what FAQ Q2.15 says).

Is this a correct assumption or is there a smarter way?  A variable to 
set?

The reason I would like to change the envelope header, is that my
laptop has a different network address depending on which network it
is connected to, or if it's connected through a dial up, and the
address it has at the time of a bounce may be a different one that it
had when the message was sent, or it may not be connected at all.

Besides there is the annoyance with listserv.  I would prefer listserv 
to subscribe the address in the From: field as set by
gnus-posting-styles. 

Re: overriding the sender header

[Harry Putnam]

On Sat, Jan 29, 2000 at 01:59:28PM +0100, Steinar Bang wrote:
> Is this a correct assumption or is there a smarter way?  A variable to 
> set?
> 
Probably are smarter ways, but this line has appeared many times here
and in gnu.emacs.gnus and seems to do all that you want.

(setq message-syntax-checks '((sender . disabled)))

I keep it in .emacs

Re: overriding the sender header

[Kai Großjohann]

Steinar Bang <sb@metis.no> writes:

> Platform: Dell Inspiron 3500 laptop, SuSE linux 6.3, Xemacs 20.4, Gnus 5.8.3
> 
> Is the envelope header set from the sender: field?  Or is it set by
> sendmail? 

The default value of message-sendmail-f-is-evil means that Gnus uses
the -f option for sendmail to set something.  It may be the envelope
sender; I'm not sure.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: overriding the sender header

[Taso N. Devetzis]

from the (v8) man page:

     -fname
          Sets  the  name  of  the  ``from''  person  (i.e.,  the
          envelope  sender  of the mail).  -f should only be used
          by ``trusted'' users (normally root, daemon,  and  net-
          work)  or if the person you are trying to become is the
          same  as  the  person  you  are.   Otherwise,   an   X-
          Authentication-Warning header will be added to the mes-
          sage.

/taso

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Steinar Bang <sb@metis.no> writes:
> 
> > Platform: Dell Inspiron 3500 laptop, SuSE linux 6.3, Xemacs 20.4, Gnus 5.8.3
> > 
> > Is the envelope header set from the sender: field?  Or is it set by
> > sendmail? 
> 
> The default value of message-sendmail-f-is-evil means that Gnus uses
> the -f option for sendmail to set something.  It may be the envelope
> sender; I'm not sure.
> 
> kai
> -- 
> A large number of young women don't trust men with beards.  (BFBS Radio)

Re: overriding the sender header

[Karl Kleinpaste]

Harry Putnam <reader@newsguy.com> writes:
> (setq message-syntax-checks '((sender . disabled)))

Slightly better:
(add-to-list 'message-syntax-checks '(sender . disabled))

Re: overriding the sender header

[Sudish Joseph]

Taso N Devetzis writes:
> from the (v8) man page:

>      -fname 

If you're using qmail or switch to it, the Return-Path: header can be
used to set the envelope sender from the headers of outbound mail.

This is very convenient for multiple address handling with mailing
list manglers, for instance.  So much so that I have the following
helper routine bound to "\C-c\C-f\C-f" in message-mode.  It sets both
From: and Return-Path: to the same address.

You might wish to mangle this to fit your sendmail situation (if that
is what you use).

;; Make it easy to override both the envelope and header from addresses.
(defvar sj/mail-from-list '("Sudish Joseph <sudish@X>"
			    "Sudish Joseph <sudish@Y>"
			    "Sudish Joseph <sudish@Z>")
  "List of alternative From: headers.")

(defvar sj/mail-from-history sj/mail-from-list ; prime the history
  "History list for sj/mail-set-from.")

(defun sj/mail-set-from ()
  (interactive)
  (let* ((from
	  (completing-read "From address: "
			   (mapcar (lambda (x) (cons x nil)) sj/mail-from-list)
			   nil
			   nil
			   (cons (car sj/mail-from-list) 0)
			   'sj/mail-from-history))
	 (return-path
	  (when (message-mail-p)
	    (require 'mail-extr)
	    (car (cdr-safe (mail-extract-address-components from))))))
    (cond
     ((eql 0 (length from))
      (error "Empty address"))
     ((and (message-mail-p)
	   (null return-path))
      (error "Couldn't parse address: %s" from))
     (t
      (save-excursion
	(save-restriction
	  (message-narrow-to-headers)
	  (message-remove-header "From")
	  (message-remove-header "Return-Path")
	  ;; this is only useful if you use qmail, where return-path
	  ;; sets the envelope from address
	  (if (message-mail-p)
	      (message-add-header (format "Return-Path: <%s>" return-path)))
	  (message-add-header (format "From: %s" from))))))))

-- 
Sudish Joseph                                          MindSpring Enterprises

Re: overriding the sender header

[Robert Epprecht]

C-h v says
   message-sendmail-f-is-evil's value is
   t

   Documentation:
   *Non-nil means that "-f username" should not be added to the sendmail\
   command line.
   Doing so would be even more evil than leaving it out.

Why is that evil?
(I don't like thouse 'X-Authentication-Warning: ' headers)

Robert Epprecht

Re: overriding the sender header

[Steinar Bang]

>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann):

> Steinar Bang <sb@metis.no> writes:
>> Platform: Dell Inspiron 3500 laptop, SuSE linux 6.3, Xemacs 20.4, Gnus 5.8.3
>> 
>> Is the envelope header set from the sender: field?  Or is it set by
>> sendmail? 

> The default value of message-sendmail-f-is-evil means that Gnus uses
> the -f option for sendmail to set something.  It may be the envelope
> sender; I'm not sure.

Yes, but I think from looking at the code that it feeds the sender
address to -f if it is different from the from: field (which I guess,
is what triggers the sender in the first place).

I tested this yesterday, and 
	(setq message-sendmail-f-is-evil t)
got rid of the X-Authentication-Warning: header that sendmail puts in, 
but it didn't change the envelope header.

However 
	(setq message-syntax-checks '((sender . disabled)))
fixed that bit for me (I'll change this to add-to-list as Karl
Kleinpaste suffested).

So now I'm happy! :-)

Re: overriding the sender header

[John Prevost]

Robert Epprecht <epprecht@sunweb.ch> writes:

> Why is that evil?
> (I don't like thouse 'X-Authentication-Warning: ' headers)

The evil is actually from MMDF's sendmail program.  MMDF treats -f as
an instruction to replace the From address with one it knows is good.
This is not what Gnus is trying to do, hence -f is evil if you have
MMDF.

John.

Re: overriding the sender header

[Michael Sperber [Mr. Preprocessor]]

>>>>> "John" == John Prevost <prevost@maya.com> writes:

John> Robert Epprecht <epprecht@sunweb.ch> writes:

>> Why is that evil?
>> (I don't like thouse 'X-Authentication-Warning: ' headers)

John> The evil is actually from MMDF's sendmail program.  MMDF treats -f as
John> an instruction to replace the From address with one it knows is good.
John> This is not what Gnus is trying to do, hence -f is evil if you have
John> MMDF.

Why doesn't Gnus trust the From header generated by sendmail?  In our
setup, sendmail knows whereas Gnus guesses wrong.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla