From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] [OT] Anyone running mutt outbound smtp on port 587?
Date: Wed, 24 Jan 2024 09:32:16 +0000 [thread overview]
Message-ID: <10410253.nUPlyArG6x@rogueboard> (raw)
In-Reply-To: <MTAwMDAzMS53ZG5lc2RheQ.1706062760@quikprotect>
[-- Attachment #1: Type: text/plain, Size: 2557 bytes --]
On Wednesday, 24 January 2024 02:19:29 GMT Walter Dnes wrote:
> I'm back after several minutes backing up to two USB drives.
>
> On Tue, Jan 23, 2024 at 09:41:16PM +0000, Michael wrote
>
> > For SMTP server use:
> >
> > set smtp_url = "smtp://Your_User_Name@www.cotse.net:465"
>
> Just one change... change "smtp://" to "smtps://", otherwise mutt
> won't connect...
>
> set smtp_pass="cotse_password"
> set smtp_url="smtps://cotse_userID@www.cotse.net:465"
Yes, my bad. The prefix smtps:// is needed to indicate an explicit TLS
connection.
> Sending a test message I got a prompt...
>
> This certificate belongs to:
> Sectigo RSA Domain Validation Secure Server CA
> Sectigo Limited
>
> Salford Greater Manchester GB
> yada, yada, yada
This is the intermediate certificate the server's certificate is signed with:
$ openssl s_client -connect www.cotse.net\:465 -showcerts
CONNECTED(00000003)
depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network,
CN = USERTrust RSA Certification Authority
verify return:1
depth=1 C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN
= Sectigo RSA Domain Validation Secure Server CA
verify return:1
depth=0 CN = www.cotse.net
verify return:1
The "Sectigo RSA Domain Validation Secure Server CA" is an intermediate CA
certificate and as it happens it is not available in the OS certificate store
/etc/ssl/certs/ where trusted Root CAs reside. Theoretically, mutt via gnutls
should check the issuer of the intermediate certificate which is "USERTrust
RSA Certification Authority", find this certificate in the OS' store of
trusted Root CAs and consequently accept as trusted any certificates in the
chain signed by this Root CA.
I don't know why this doesn't function as I describe above. Practically it
seems mutt may need to be directed to accept all certificates in a chain as
trusted.
http://www.mutt.org/doc/manual/#certificate-file
You could try copying the "USERTrust RSA Certification Authority" in your
local mutt certificates directory, or copying just the intermediate CA
certificate "Sectigo RSA Domain Validation Secure Server CA".
> It asked whether I wanted to (r)eject, accept (o)nce, accept (a)lways
> and I chose always.
Your 'accept (a)lways' command would have stored this certificate in your
local mutt certificates directory.
> This post is coming to you via port 587 via fibre and via cotse.net.
> Thank you very much. I couldn't have done it without your deatailed help.
Glad you got it sorted. :-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-24 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 19:01 [gentoo-user] [OT] Anyone running mutt outboung smtp on port 587? Walter Dnes
2024-01-09 19:54 ` Philip Webb
2024-01-10 4:59 ` Walter Dnes
2024-01-18 17:02 ` Walter Dnes
2024-01-18 18:42 ` Michael
2024-01-21 4:23 ` Walter Dnes
2024-01-21 12:05 ` Michael
2024-01-21 16:09 ` Walter Dnes
2024-01-21 16:29 ` Jack
2024-01-21 19:27 ` Michael
2024-01-22 20:24 ` Walter Dnes
2024-01-22 21:52 ` [gentoo-user] [SOLVED] " Walter Dnes
2024-01-22 22:08 ` Michael
2024-01-23 4:21 ` Walter Dnes
2024-01-23 9:36 ` Michael
2024-01-23 15:47 ` [gentoo-user] [SOLVED] [OT] Anyone running mutt outbound " Walter Dnes
2024-01-23 16:12 ` Michael
2024-01-23 19:09 ` Walter Dnes
2024-01-23 21:41 ` Michael
2024-01-24 2:19 ` Walter Dnes
2024-01-24 9:32 ` Michael [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10410253.nUPlyArG6x@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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