From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Clarification about Rmail over SSL
Date: Tue, 23 Apr 2024 09:43:12 +0300 [thread overview]
Message-ID: <86o7a04m0v.fsf@gnu.org> (raw)
In-Reply-To: <8734rdxkf5.fsf@RISEUP> (message from BP25 on Mon, 22 Apr 2024 20:32:46 +0100)
> From: BP25 <bp25@riseup.net>
> Date: Mon, 22 Apr 2024 20:32:46 +0100
>
> The manual says:
>
> --8<---------------cut here---------------start------------->8---
> Mailutils movemail supports TLS encryption. If you wish to use it, add
> the ‘--tls’ flag to rmail-movemail-flags.
> --8<---------------cut here---------------end--------------->8---
>
> But then what's the difference with setting pop3-stream-type to 'ssl ,
> or even simply using the remote mailbox url pops:// ?
Are you using pop3.el for fetching email? Or are you using the
'movemail' program (from Mailutils, I presume)? I think
pop3-stream-type is only relevant if you use pop3.el.
prev parent reply other threads:[~2024-04-23 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 19:32 Clarification about Rmail over SSL BP25
2024-04-23 6:43 ` Eli Zaretskii [this message]
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=86o7a04m0v.fsf@gnu.org \
--to=eliz@gnu.org \
--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).