Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Multi-SMTP
Date: Thu, 02 Feb 2012 07:56:21 -0500	[thread overview]
Message-ID: <87y5slpf62.fsf@lifelogs.com> (raw)
In-Reply-To: <87k44576et.fsf@gnus.org>

On Thu, 02 Feb 2012 13:42:50 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> I'm wondering how the multi-SMTP stuff should work.
LI> One approach would be to use group parameters, and add tokens like
LI> (smtp (smtpmail "smtp.gmail.com" 583)) or something.

Use a plist, please.  The tokens should be either

(smtp (smtpmail :machine "smtp.gmail.com" :port 583 :user "cafe" :password "mocha"))

which would then call to auth-source if the user name or password are
not provided, or 

(smtp 'function-or-symbol) ;; eval to get the plist, for easy auth-source integration

The latter format would have 'sendmail as a special case.  The function
call would get enough parameters to determine the right thing to do.

LI> Message would then put this info into a header that would be saved, so
LI> that saving to drafts/queues etc would work.

LI> So that would be

LI> X-Message-Outgoing-SMTP: smtpmail smtp.gmail.com 583

LI> If you want sendmail, then that would be

LI> X-Message-Outgoing-SMTP: sendmail

LI> That would be a pretty flexible mechanism, and allow for easy
LI> customisations by users.

Works for me, though the first one should be a plist.

LI> On the Gnus side, one could then add "intelligent" rules for determining
LI> where to send mail, although I'm not sure just how.  :-)  If the
LI> Received line of the message you're answering contains smtp.work.com,
LI> then use that as the outgoing MTA for your work email?  Hm...

Group/topic parameters should be sufficient IMO.

Ted




  reply	other threads:[~2012-02-02 12:56 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 ` Ted Zlatanov [this message]
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       ` 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=87y5slpf62.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).