unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: BP25 <bp25@riseup.net>
To: help-gnu-emacs@gnu.org
Subject: Clarification about forced TLS connections with remote mailboxes and smtp
Date: Tue, 23 Apr 2024 16:57:19 +0100	[thread overview]
Message-ID: <875xw8cbs0.fsf@RISEUP> (raw)

Hello,

I have a few questions. Is there a kind soul who would clarify a few
things for me please?

1. I use Rmail to fetch my messages from remote mailboxes. Do you know
if using the url starting with pops:// or imaps:// always forces the
connection to be encrypted via TLS over SSL?

1a. Then what happens when only the Emacs movemail is available? I think
that no encrypted connection is supported for the POP protocol then.

1b. Suppose we're using instead the Mailutils movemail: does the --tls
flag only affect connections with URL starting by pop:// or imap://, and
doesn't affect connections whose URL starts by pops:// or imaps://?

2. I read on the movemail manual ``The deprecated POP3S protocol is also
supported. It is enabled by an URL beginning with pops:// instead of
pop://'' but I read on the Emacs manual ``If using Mailutils movemail,
you may wish to use ‘pops’ in place of ‘pop’.'' therefore I'm confused
on whether this syntax is obsolete or recommended!

I use Message and I send emails by using smtpmail-send-it. I also set
variables smtpmail-smtp-service 465 and smtpmail-stream-type 'ssl.

3a. Does setting either one of these last two varibales already force
the connection to happen via TLS over SSL?

3b. If neither of the two variables is set but the SMTP server I use
says that:

--8<---------------cut here---------------start------------->8---
 ``If your mail client does not support secure SMTP, you cannot use our
server as your SMTP. You might have the option of choosing either TLS or
SSL for the secure connection. Both protocols work, but most ISPs will
block port 25 (used by TLS), so we recommend that you choose SSL'' and
later adds that ``For security reasons, we no longer support SSL.''
--8<---------------cut here---------------end--------------->8---

then does it mean that I cannot have accidentally exposed my login
details or other information by initiating a nonencrypted connection?

3c. Do you agree that the quoted information from my SMTP server above
is confusing?



             reply	other threads:[~2024-04-23 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 15:57 BP25 [this message]
2024-04-23 16:24 ` Clarification about forced TLS connections with remote mailboxes and smtp BP25
2024-04-24  2:02   ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-24  5:20   ` Eli Zaretskii
2024-04-24  5:52 ` Eli Zaretskii

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=875xw8cbs0.fsf@RISEUP \
    --to=bp25@riseup.net \
    --cc=help-gnu-emacs@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.
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).