9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] A question on remotemail
Date: Tue,  8 Jul 2008 12:52:17 -0400	[thread overview]
Message-ID: <20080708165028.6E38E1E8C2B@holo.morphisms.net> (raw)
In-Reply-To: <20080708150047.GG29253@hermes.my.domain>

There are two different "From" addresses associated
with a particular mail message.  There is the RFC822
"From:" line and then there is the "MAIL FROM" return
address that is sent as part of the SMTP conversation.
(This is the address recorded in the "From " line at the
top of the Plan 9 mbox-format messages.  See thread
last month.)

The two are not always the same.  For example, this message
says it is From: <rsc@swtch.com>, but the SMTP return
address is something like 9fans+bounces+23450qc@9fans.net,
so that if a bounce comes back, it goes to the mailing list
software, which uses the last bit to determine which address
on the list is bouncing.

I would be a little surprised if your ISP is rejecting
based on the From: line rather than the SMTP return address,
but maybe spammers have driven them to that.
The /mail/box/$user/headers file sets RFC822 headers,
including the From: header.  The upas/smtp arguments set
the SMTP return address.

As for how to do it "right", editing remotemail sounds fine.
The nice thing about upas is you can understand the shell
scripts and edit them, instead of having to shoehorn
everything into some preordained config file.

Russ



  parent reply	other threads:[~2008-07-08 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 15:00 Christian Kellermann
2008-07-08 15:25 ` erik quanstrom
2008-07-08 15:56   ` Christian Kellermann
2008-07-08 16:05     ` erik quanstrom
2008-07-08 16:21       ` Christian Kellermann
2008-07-08 16:32         ` Christian Kellermann
2008-07-08 16:45           ` erik quanstrom
2008-07-08 16:52 ` Russ Cox [this message]
2008-07-08 18:28   ` Christian Kellermann

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=20080708165028.6E38E1E8C2B@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).