From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: Multi-SMTP
Date: Sat, 04 Feb 2012 14:12:40 +0000 [thread overview]
Message-ID: <frk4428z6v.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87bopfkhx8.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> I'm wondering how the multi-SMTP stuff should work.
>
> [...]
>
>> On the Gnus side, one could then add "intelligent" rules for determining
>> where to send mail, although I'm not sure just how. :-) If the
>> Received line of the message you're answering contains smtp.work.com,
>> then use that as the outgoing MTA for your work email? Hm...
>
> No, I would prefer explicit control of what smtp server to use as I
> frequently respond to emails that have come into one account as if they
> had come into another account (e.g. I receive personal emails on my work
> account but would rather carry on the conversation on my personal
> email).
>
> Obviously, as a default in the absence of anything else, what you are
> suggesting is fine.
I like the idea of setting the smtp to use "token" (machine name in
authinfo) using gnus-posting styles. Easy then to set group/from specific.
next prev parent reply other threads:[~2012-02-04 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 12:42 Multi-SMTP Lars Ingebrigtsen
2012-02-02 12:56 ` Multi-SMTP Ted Zlatanov
2012-02-02 13:32 ` Multi-SMTP Lars Ingebrigtsen
2012-02-02 13:54 ` Multi-SMTP Ted Zlatanov
2012-02-02 14:04 ` Multi-SMTP Lars Ingebrigtsen
2012-02-02 15:49 ` Multi-SMTP Johann 'Myrkraverk' Oskarsson
2012-02-03 16:20 ` Multi-SMTP Eric S Fraga
2012-02-04 14:12 ` Richard Riley [this message]
2012-02-05 21:02 ` Multi-SMTP Memnon Anon
2012-02-06 9:05 ` Multi-SMTP Eric S Fraga
2012-02-06 23:33 ` Multi-SMTP Lars Ingebrigtsen
2012-02-07 16:16 ` Multi-SMTP Eric S Fraga
2012-02-08 12:15 ` Multi-SMTP Richard Riley
2012-02-08 16:04 ` Multi-SMTP Eric S Fraga
2012-02-08 18:58 ` Multi-SMTP Richard Riley
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=frk4428z6v.fsf@news.eternal-september.org \
--to=rileyrg@gmail.com \
--cc=ding@gnus.org \
/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).