From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Email extensions/alternate emails
Date: Sat, 08 Dec 2007 14:00:01 -0800 [thread overview]
Message-ID: <1197150436-sup-2569@south> (raw)
In-Reply-To: <1196423833-sup-2326@tomsk>
Hi Marcus,
Great questions and sorry for the delay in replying.
Excerpts from Marcus Williams's message of Fri Nov 30 04:05:27 -0800 2007:
> I've never quite figured out why I'd add alternate emails to my
> config/accounts. Last time I used them it appeared that emails coming
> into an alternate address used the default email address on that
> account to reply with - is this still the case?
I believe it was this way for a while, but only because of a bug. The
current behavior (reply-mode.rb circa line 144) is a sequence of three
steps:
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.
2. If not, if any of the addresses in To: or Cc: are an "account
address", the DEFAULT address for that account is used.
3. Failing either of those options, the default address of the default
account is used.
Step #1 is the most important, and I think it should capture what you
describe below. But that particular selection and sequence of headers
was determinted empirically, by me, so it may need adjustment.
So the alternate emails on an account aren't directly useful for
replies, since they won't ever be used as a From: unless they happen to
have come in on a Delivered-To/Envelope-To/etc header, in which case the
fact that they're an alternate email is irrelevant.
But they are used to determine when a message is to or cc you (the ">"
and "+" widgets you see in thread-index-mode).
> I ask because I'm trying to implement support for email extensions
> basically an email address like name-someotherid at domain.tld where
> -someotherid is the extension. I added an "extensions" config option
> that allowed me to add regexes for my extensions. I then extended
> account_for to return the correct account given an email that matched
> one of these extensions.
An excellent idea. There actually was something like that in Sup
much earlier, but was the victim of a refactor at some point.
> But... what I really wanted sup to do then was what I expected it to
> do with alternates, is to reply to an email that came in on one of
> these extensions with the same email address, not with the account
> email address.
Does it not do this in recent SVN checkouts? If not, is there a header
like Delivered-To: in the incoming email that contains the address?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-12-08 22:00 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 [this message]
2007-12-09 21:18 ` Marcus Williams
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=1197150436-sup-2569@south \
--to=wmorgan-sup@masanjin.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