Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Email extensions/alternate emails
Date: Sun, 09 Dec 2007 21:18:34 +0000	[thread overview]
Message-ID: <1197234773-sup-132@tomsk> (raw)
In-Reply-To: <1197150436-sup-2569@south>

On 8.12.2007, William Morgan wrote:
> 1. First, if the message contains an Envelope-To, X-Original-To, or
>    Delivered-To header (in that order of precedence), the address
>    in that header is used.

Ah. That might be all I needed to know. I'll make sure I'm getting one
of these headers and see if that makes the difference. That also
explains why some of my mail goes out from the wrong address even when
I have got an account set up for it.

Will update once I've played a bit more.

Marcus


  reply	other threads:[~2007-12-09 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 12:05 Marcus Williams
2007-12-08 22:00 ` William Morgan
2007-12-09 21:18   ` Marcus Williams [this message]
2007-12-09 21:42     ` William Morgan
2007-12-10 15:28       ` Marcus Williams
2007-12-10 17:37         ` William Morgan
2007-12-10 22:28           ` Marcus Williams
2007-12-10 22:36             ` Marcus Williams
2007-12-14  1:03               ` William Morgan
2007-12-14 10:10                 ` Marcus Williams
2008-01-06 19:46             ` William Morgan
2008-01-07 12:35               ` Marcus Williams

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=1197234773-sup-132@tomsk \
    --to=marcus-sup@bar-coded.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