On Tuesday, 23 January 2024 19:09:19 GMT Walter Dnes wrote:
> On Tue, Jan 23, 2024 at 04:12:05PM +0000, Michael wrote
> 
> > You can also try to set deprecated TLS protocols in ~/.muttrc
> > to see if this will allow for a successful connection:
> > 
> > http://mutt.org/doc/manual/#ssl-use-tlsv1
> 
>   Thanks.  I commented out the "no" lines.  TLS 1.1 failed, but TLS 1.0
> seems to work...
> 
> # set ssl_starttls=no
> # set ssl_force_tls=no
> set ssl_use_tlsv1=yes
> set smtp_url=smtp://smtp.ebox.ca:587
> 
> > You had a good crack at this, but TBH it would be easier and safer to
> > find an email hosting company who use up to date TLS certificates. ;-)
> 
>   I currently use cotse.net to handle incoming email.  It's served me
> well, allowing me to keep the same email address over the years as I've
> changed ISPs.  I could do outbound email through them, but I don't like
> webmail interfaces.  Notice the mention of "mutt" in the subject.

 O_O

STOP RIGHT THERE!

http://cotse.net/support.html

They offer SMTP on any number of ports AND require TLS authentication.  No 
need to dance around deprecated hash algos and certificates.

Remove the 'ssl_use_tlsv1=yes' directive.

For SMTP server use: 

set smtp_url = "smtp://Your_User_Name@www.cotse.net:465"

You can use port 465 without STARTTLS.  Mutt will negotiate an encrypted 
connection over TLS right off the bat.

Use your username and password to login, as you do for POP3/IMAP4.  Job done.


>   This post is coming to you via port 587 *VIA FIBRE*... wheeeee!  The
> support desk phoned this morning, and we went spelunking through the
> config menus of the fibre modem, and set it up.

It doesn't matter what connection/IP address you use to authenticate on cotse 
to receive and send messages.  They appear to be running a more up to date 
professional setup.