From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Use of gnutls-cli breaks new verizon setting
Date: Fri, 06 Jan 2012 00:28:58 -0500 [thread overview]
Message-ID: <847h15ielh.fsf@davestoy.home> (raw)
Verizon recently (finally!) announced support, soon to be required, for SSL on POP3 and SMTP. However things are weird. I did not have gnutls-cli on my system, so the pop3 setting found openssl and that worked fine. Smtpmail seems to insist on using gnutls-cli, with no option for openssl. So I installed gnutls-cli and things break.
For pop3, it's called as
gnutls-cli -p 995 --insecure incoming.verizon.net
And for some reason, I get an error that my user is invalid. But if I set a debug-on-entry for pop3-logon and step through, it works fine. Seems like some odd race condition.
For smtpmail, it's called as
gnutls-cli -s -p 465 outgoing.verizon.net
and this just hangs. If I do that at the command line, I see why - it connects to the server and prints a message saying "simple client mode" but no banner from the server. If I remove the -s, I get the banner from the server. However the -s is hardcoded into starttls.el. Why? Do I need it? While I'd prefer to not have a locally hacked file or function definition, if that's what I have to do I will but if that can be made optional, it would be nice.
For what it's worth, I am on
emacs-version is a variable defined in `version.el'.
Its value is "23.1.1"
on Ubuntu 10.04.
Thanks for any advice.
--
Dave Goldberg
david.goldberg6@verizon.net
next reply other threads:[~2012-01-06 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 5:28 Dave Goldberg [this message]
2012-01-06 21:05 ` Lars Magne Ingebrigtsen
2012-01-07 14:38 ` Dave Goldberg
2012-01-07 16:39 ` Andreas Schwab
2012-01-07 20:57 ` Dave Goldberg
2012-01-26 19:13 ` Lars Ingebrigtsen
2012-01-26 19:30 ` Lars Ingebrigtsen
2012-01-27 3:57 ` Dave Goldberg
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=847h15ielh.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--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).