From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Email extensions/alternate emails
Date: Fri, 30 Nov 2007 12:05:27 +0000 [thread overview]
Message-ID: <1196423833-sup-2326@tomsk> (raw)
Hi -
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 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.
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.
What else do I need to do? Is it just a matter of extending the reply
mode code? To do this should I have to create a dummy account/person
object for the extension address to be able to use it (this seems to
be the case)? Is there a better way to handle extensions?
Thanks
Marcus
next reply other threads:[~2007-11-30 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 12:05 Marcus Williams [this message]
2007-12-08 22:00 ` William Morgan
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=1196423833-sup-2326@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