From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Multi-SMTP
Date: Thu, 02 Feb 2012 08:54:46 -0500 [thread overview]
Message-ID: <87liolpcgp.fsf@lifelogs.com> (raw)
In-Reply-To: <878vkl4azc.fsf@gnus.org>
On Thu, 02 Feb 2012 14:32:23 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> 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
LI> Hm... But we consult auth-source anyway to get the credentials, so why
LI> would the user want to put the user name/password into the
LI> parameters?
You're right, never mind. In that case there's at most 2 parameters,
right? machine and port?
LI> Are there any use cases for sending messages via the same smtp server,
LI> but with different user names?
Yes, GMail. We must support that case, it's much more common now than
it used to be.
LI> I'd like to keep the header somewhat human-readable...
OK, if there's just the two parameters :)
Ted
next prev parent reply other threads:[~2012-02-02 13:54 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 ` Ted Zlatanov [this message]
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=87liolpcgp.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).