Post is tl;dr, but if anybody else thinks XEmacs really should get
raw SSL/TLS connections, please speak up, priorities can be changed.
Uwe Brauer writes:
I take your word. I am just wondering why thunderbird/seamonkey
associate port 587 with starttls and 465 with ssl,
I suspect that what happened was that port 465 was assigned as an
SSL-only version of SMTP, where the SSL connection is established
externally and SMTP is tunneled over that. Then the community
discovered that this wasn't a great idea, and developed the STARTTLS
RFC to address the problems.
and why GNU emacs smtpmail has the following
(defcustom smtpmail-stream-type nil
:type '(choice (const :tag "Possibly upgrade to STARTTLS" nil)
(const :tag "Always use STARTTLS" starttls)
(const :tag "Never use STARTTLS" plain)
(const :tag "Use TLS/SSL" ssl)))
The short answer is "GNU Emacs has 10x as many developers as we do and
Mozilla has 100x".
In Emacs, evidently until very recently this was implemented by
calling openssl or gnutls-cli to open the stream (rather than asking
the MTA to do STARTTLS negotiation, which is trivial to implement).
Then Ted Z implemented a direct call to gnutls in v24. Either way,
you then have to start talking to the remote MTA, and I'm not sure how
Since we can depend on gnutls-cli, I don't suppose it would be hard to
port enough of GNU Emacs's capabilities to allow XEmacs to talk to
dedicated SSL ports like https, nntps, and smtps. Unfortunately I
don't have time at the moment. But this would surely be good enough
for you since you evidently have gnutls installed (Emacs won't use
OpenSSL as a matter of principle).
> Are you sure that's not port 465?
oops my bad
No problem, just wanted to make sure it wasn't that simple. :-)
XEmacs-Beta mailing list