From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: `send-mail-function' default change
Date: Wed, 06 Jul 2011 19:36:10 +0200 [thread overview]
Message-ID: <m3wrfv1fcl.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <83box7pbg2.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 06 Jul 2011 20:26:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Please add to NEWS a detailed description of how to move the old
> smtpmail setup to the brave new world.
[...]
> I think my setup is very similar of Óscar's, btw. I have the
> following variables defined:
>
> smtpmail-smtp-server
> smtpmail-smtp-service
> smtpmail-auth-credentials
>
> The latter defines my username and password for logging into my ISP's
> SMTP server. I don't currently use STATTLS.
Ok, perhaps we can work out a text here?
---------------
** smtpmail has been largely rewritten to upgrade to STARTTLS if
possible, and uses the auth-source framework for getting credentials.
The rewrite should be largely compatible with previous versions of
smtpmail, but there are two major incompatibilities:
** `smtpmail-auth-credentials' no longer exists. That variable used to
be be either ~/.authinfo (in which case you're fine -- you won't see any
difference), but if it were a direct list of user names and passwords,
you will be prompted for the user name and the password instead, and
they will then be saved to ~/.authinfo.
If you wish to copy over all the credentials from
`smtpmail-auth-credentials' to your ~/.authinfo file manually, instead
of letting smtpmail prompt you for these values, that's also possible.
If you had, for instance,
(setq smtpmail-auth-credentials
'(("mail.example.org" 25 "jim" "s!cret")))
then the equivalent line in ~/.authinfo would be
machine mail.example.org port 25 login jim password s!cret
** Similarly, `smtpmail-starttls-credentials' no longer exists. If
you had thet set, then then you need to put
machine smtp.whatever.foo port 25 key "~/.my_smtp_tls.key" cert "~/.my_smtp_tls.cert"
in your ~/.authinfo file instead.
---------------
Would that do?
But it strikes me here that perhaps there should just be a function like
`M-x smtpmail-save-old-credentials' that would do this for you. It
would be utterly trivial to write. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-06 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 15:38 `send-mail-function' default change Lars Magne Ingebrigtsen
2011-07-06 17:26 ` Eli Zaretskii
2011-07-06 17:36 ` Lars Magne Ingebrigtsen [this message]
2011-07-06 17:56 ` Eli Zaretskii
2011-07-06 20:13 ` Stefan Monnier
2011-07-07 11:19 ` Lars Magne Ingebrigtsen
2011-07-07 0:33 ` Richard Stallman
2011-07-07 20:31 ` Stefan Monnier
2011-07-07 20:56 ` Lars Magne Ingebrigtsen
2011-07-07 21:24 ` Stefan Monnier
2011-07-09 3:26 ` Tim Cross
2011-07-10 5:01 ` Tim Cross
2011-07-08 0:07 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wrfv1fcl.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).