public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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: Tue, 23 Jan 2024 21:41:16 +0000	[thread overview]
Message-ID: <1955193.PYKUYFuaPT@rogueboard> (raw)
In-Reply-To: <ZbAO30Mxn2zEuDJT@waltdnes.org>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-23 21:41 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 [this message]
2024-01-24  2:19                   ` Walter Dnes
2024-01-24  9:32                     ` Michael

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=1955193.PYKUYFuaPT@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