Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: Who sets Sender:?
Date: Sat, 25 May 2002 00:55:24 +0200	[thread overview]
Message-ID: <87wuttrw9v.fsf@doohan.bang.priv.no> (raw)
In-Reply-To: <873cwld3aw.fsf@nwalsh.com>

>>>>> Norman Walsh <ndw@nwalsh.com>:

> Ok, fair enough. So this presents an interesting conundrum. In my
> case, the "local machine" has no name. I'm on a laptop behind a
> firewall attached to a cable provider that generates a "random" IP
> address via DHCP.

Been there.

> So, on my local subnet (192.168.1.*), "mercury" is this laptop. But
> there's no global name for it.

Been there too, when my laptop was at home.

> I can't claim that it's 'mercury.nwalsh.com' because no such machine
> exists in DNS.

What I do is to make sure Gnus doesn't create a Sender: header by
having
	;; Avoid setting the sender header, and by this use the From: address
	;; as the envelope address
	(add-to-list 'message-syntax-checks '(sender . disabled))
in my ~/.gnus.el.

Then I make sure exim sets the From line of the envelope to be the same
as the From: field, by setting the return_path of outgoing SMTP
messages in /etc/exim/exim.conf:
	remote_smtp:
	  driver = smtp
	  return_path = ${local_part:$reply_address}@${domain:$reply_address}

(this is on debian testing).



  parent reply	other threads:[~2002-05-24 22:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 20:19 Norman Walsh
2002-05-20 21:24 ` Stainless Steel Rat
2002-05-21 13:43   ` Norman Walsh
2002-05-21 14:25     ` Stainless Steel Rat
2002-05-21 14:38       ` Paul Jarc
2002-05-24 22:55     ` Steinar Bang [this message]
2002-05-26 13:48     ` Barry Fishman
2002-05-26 14:33       ` Harry Putnam
2002-05-26 17:17         ` Barry Fishman
2002-05-20 22:12 ` Matt Armstrong
2002-05-21  1:58   ` Stainless Steel Rat
2002-05-21 14:14     ` Paul Jarc
2002-05-21 15:04       ` Stainless Steel Rat
2002-05-21 15:27         ` Paul Jarc
2002-05-21 16:27           ` Stainless Steel Rat
2002-05-21 16:56             ` Paul Jarc
2002-05-21 18:33               ` Stainless Steel Rat
2002-05-21 18:50                 ` Paul Jarc
2002-05-21 19:04                   ` Matt Armstrong
     [not found]                     ` <84g00lma45.fsf@rjk.greenend.org.uk>
2002-05-21 22:07                       ` Paul Jarc
2002-05-22 12:05                         ` Richard Kettlewell
2002-05-21 19:46                   ` Stainless Steel Rat
2002-05-21 20:13                     ` Paul Jarc
2002-05-21 21:16                       ` Stainless Steel Rat
2002-05-21 21:51                         ` Paul Jarc
2002-05-22  0:02                           ` Stainless Steel Rat
2002-05-22 15:23                             ` Paul Jarc
2002-05-22 15:54                               ` Stainless Steel Rat
2002-05-22 16:03                                 ` Paul Jarc
2002-05-22 17:04                                   ` Stainless Steel Rat
2002-05-22 17:25                                     ` Paul Jarc
2002-05-22 17:56                                       ` Stainless Steel Rat
2002-05-22 17:38                                     ` Bjørn Mork
2002-05-22 18:04                                       ` Stainless Steel Rat
2002-05-21 17:52     ` Matt Armstrong
2002-05-21 18:48       ` Stainless Steel Rat

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=87wuttrw9v.fsf@doohan.bang.priv.no \
    --to=sb@dod.no \
    /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).