From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Multiple email accounts
Date: Wed, 27 May 2009 19:51:06 +0100 [thread overview]
Message-ID: <1243449836-sup-6622@tomsk> (raw)
In-Reply-To: <1243440902-sup-4117@entry>
On 27.5.2009, William Morgan wrote:
> > Great, that's 99% of what I need. The last 1% is, can Sup auto-detect
> > what From line to send based on the source of the message, if the To:
> > header is not intact? (This is commonly the case for mailing lists.
>
> You can use the reply-from hook to set it automatically however you
> want. Try adding something like the following (completely untested!) to
> ~/.sup/hooks/reply-from.rb:
[snip]
Note also that you might be able to do what you want with the regexen
options in config.yaml - so for instance Sup works out that I reply to
the sup talk mail list with marcus-sup at .... It uses the envelope-to
header to figure this out I seem to remember (coupled with the regexen
settings).
So under one of my accounts I have:
:regexen:
- marcus-.*(at)mydomain.com
(where (at) is replaced with @, and mydomain.com is replaced with the
obvious).
This make sup recognise all incoming emails to my email extensions
that all begin with "marcus-" and unlike the :alternative: settings
are used by sup to figure out what address to reply with. Works well
for all the mailing lists I'm using.
The only problem is they dont get used for sending new addresses (but
I recently sent an email about how I get around that).
HTH
Marcus
prev parent reply other threads:[~2009-05-27 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 23:32 Edward Z. Yang
2009-05-23 23:57 ` Iain
2009-05-25 18:18 ` Edward Z. Yang
2009-05-27 16:22 ` William Morgan
2009-05-27 18:51 ` Marcus Williams [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=1243449836-sup-6622@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