Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: Changing Return-Path
Date: 11 Nov 1998 14:03:53 -0500	[thread overview]
Message-ID: <vxkd86u2grq.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Matt Armstrong's message of "11 Nov 1998 10:14:52 -0800"

Anders Melchiorsen <and@kampsax.dtu.dk> writes:
>> What I was wondering was whether the Return-Path: should be my
>> e-mail address or the account I am posting from (which is
>> unreachable due to a firewall).

Matt Armstrong <matta@geoworks.com> writes:
> The Return-Path: is not set by Gnus, but by sendmail

This is similar to the difficulty some of us have with Gnus'
generation of Sender.

This one is partly Gnus' "fault", if you can call it that.  sendmail
is invoked with `"-f" (user-login-name)' in message.el, to set the
origin user positively; a typical sendmail installation will then
adjust that to be your-name@your.host.where.you.sent.the.mail.  For
many (most?) of us, that's not really quite desirable, since (e.g.) my
Return-Path (which is the envelope origin from SMTP Mail From:<>,
converted to a header upon delivery) shows karl@pocari-sweat.jprc.com
but my normal address is karl@jprc.com.

The only way to hack around this is to modify the function
message-send-mail-with-sendmail from message.el, to substitute the
"-f" argument with a string that's more appropriate for you.

With regard to the standards for Return-Path, RFC822 observes that it
should be a _route_ back to the originator, i.e., it should show relay
hops; RFC1123 in turn says that failure notifications should be sent
back to the originator with the route information deleted, that is,
"If the address is an explicit source route, it SHOULD be stripped
down to its final hop."  ???  Then what's the point of providing the
source route in the first place?

It seems to me that Return-Path's value has become very limited in an
environment where source-routed mail is vastly deprecated, and just
plain not supported by many.  I know that, when I did serious sendmail
work years ago, I shot all source routes on sight.

You could very well substitute the use of (user-login-name) for the
"-f" argument in message-send-mail-with-sendmail with the variable
user-mail-address; the result should give the effect you need, and not
create any interoperability problems -- mail will still show a proper
way to return to you.

That said, this mailing list's requirement of matching Return-Path is
indeed pretty peculiar.

--karl


      reply	other threads:[~1998-11-11 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-10 22:01 Anders Melchiorsen
1998-11-11  9:16 ` Matt Armstrong
1998-11-11 11:48   ` Anders Melchiorsen
1998-11-11 16:06     ` Frank D. Cringle
1998-11-11 18:14     ` Matt Armstrong
1998-11-11 19:03       ` Karl Kleinpaste [this message]

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=vxkd86u2grq.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.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).