Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: Multi-SMTP
Date: Wed, 08 Feb 2012 12:15:39 +0000	[thread overview]
Message-ID: <11k43xmsgk.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87pqdq4o1h.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> 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).
>>
>> Sure.  Hm.  Should there be an explicit Message command for setting the
>> mail sending method, perhaps?
>>
>> But I do think it would make sense to make it easy to be able to
>> configure the outgoing method based on the To address.  Does either Gnus
>> or Message already have a thing for customising the Message buffer based
>> on that?  I couldn't see anything obvious...
>
> No idea.  I manage this by posting styles based on folders and splitting
> of emails to end up in the right folders.  If I get an email in a "work"
> folder, say, that I want to respond as a "personal" email, I manually
> move the original mail to a suitable folder and then respond.  Not ideal
> but it works...

Can you explain in more detail about why you would want smtp based on to
address as additional functionality? smtp is about sending so its clear
that from address/group drives this in the *normal* situation :
especially since some smtp services wont allow a different from address
to the account authorized user (gmail for example). I wonder if the
better work model would be to split incoming based on *from* address
when they're spooled in and then simply use gnus posting styles
attributes to indicate the smtp outgoing server line in authinfo to
utilise : therefore the development effort is curtailed to simply
outgoing smtp server selection : which really should be selectable by
gnus-posting-styles which is an existing proven, documented and
customisable method of guiding gnus.




  reply	other threads:[~2012-02-08 12:15 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   ` Multi-SMTP Richard Riley
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       ` Richard Riley [this message]
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=11k43xmsgk.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).