From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id EF1F915838C for ; Tue, 23 Jan 2024 15:47:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 230A2E2AB1; Tue, 23 Jan 2024 15:47:15 +0000 (UTC) Received: from barracuda.ebox.ca (barracuda.ebox.ca [96.127.255.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BA920E2AAC for ; Tue, 23 Jan 2024 15:47:14 +0000 (UTC) X-ASG-Debug-ID: 1706024833-0c856e713e186dc40001-LfjuLa Received: from smtp.ebox.ca (smtp.ebox.ca [96.127.255.82]) by barracuda.ebox.ca with ESMTP id ZXZPe6QCHU8oZlBS (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 23 Jan 2024 10:47:13 -0500 (EST) X-Barracuda-Envelope-From: waltdnes@waltdnes.org X-Barracuda-RBL-Trusted-Forwarder: 96.127.255.82 Received: from waltdnes.org (unknown [198.58.217.37]) by smtp.ebox.ca (Postfix) with SMTP id 6A5A1441B21 for ; Tue, 23 Jan 2024 10:47:13 -0500 (EST) Date: Tue, 23 Jan 2024 10:47:28 -0500 X-Barracuda-RBL-IP: 198.58.217.37 X-Barracuda-Effective-Source-IP: 198-58-217-37.on.cable.ebox.net[198.58.217.37] X-Barracuda-Apparent-Source-IP: 198.58.217.37 From: Walter Dnes To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [SOLVED] [OT] Anyone running mutt outbound smtp on port 587? Message-ID: X-ASG-Orig-Subj: Re: [gentoo-user] [SOLVED] [OT] Anyone running mutt outbound smtp on port 587? References: <22161767.EfDdHjke4D@rogueboard> <2594403.Lt9SDvczpP@rogueboard> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2594403.Lt9SDvczpP@rogueboard> X-Barracuda-Connect: smtp.ebox.ca[96.127.255.82] X-Barracuda-Start-Time: 1706024833 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: https://96.127.255.19:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Virus-Scanned: by bsmtpd at ebox.ca X-Barracuda-Scan-Msg-Size: 1974 X-Barracuda-Spam-Score: 0.50 X-Barracuda-Spam-Status: No, SCORE=0.50 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=WEIRD_PORT X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.119834 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.50 WEIRD_PORT URI: Uses non-standard port number for HTTP X-Archives-Salt: 001d9aad-d7be-4f84-9868-aba55a205494 X-Archives-Hash: f88062ef40c3f84e31bd05df03001eac On Tue, Jan 23, 2024 at 09:36:13AM +0000, Michael wrote > Since gnutls is playing up with mutt, you can try setting USE="-gnutls" > and re-emerge mutt to see if it succeeds establishing a connection. If I emerge mutt with USE="-gnutls" and comment out "set ssl_starttls=no", email fails... [2024-01-23 09:38:07] Looking up smtp.ebox.ca... [2024-01-23 09:38:07] Connecting to smtp.ebox.ca... [2024-01-23 09:38:07] Connected to smtp.ebox.ca:587 on fd=4 [2024-01-23 09:38:07] 4< 220 smtp.ebox.ca ESMTP Postfix (Debian/GNU) [2024-01-23 09:38:07] 4> EHLO waltdnes.org [2024-01-23 09:38:07] 4< 250-smtp.ebox.ca [2024-01-23 09:38:07] 4< 250-PIPELINING [2024-01-23 09:38:07] 4< 250-SIZE 20000000 [2024-01-23 09:38:07] 4< 250-VRFY [2024-01-23 09:38:07] 4< 250-ETRN [2024-01-23 09:38:07] 4< 250-STARTTLS [2024-01-23 09:38:07] 4< 250-ENHANCEDSTATUSCODES [2024-01-23 09:38:07] 4< 250-8BITMIME [2024-01-23 09:38:07] 4< 250 DSN [2024-01-23 09:38:07] 4> STARTTLS [2024-01-23 09:38:07] 4< 220 2.0.0 Ready to start TLS [2024-01-23 09:38:07] ssl_load_certificates: loading trusted certificates [2024-01-23 09:38:07] mutt_ssl_starttls: Error loading trusted certificates [2024-01-23 09:38:07] SSL failed: error:0A000102:SSL routines::unsupported protocol [2024-01-23 09:38:08] Could not negotiate TLS connection ssl_starttls (and ssl_force_tls) default to "yes" in muttrc. If ssl_starttls and ssl_force_tls are not explicitly set to "no", mutt *WILL* attempt a TLS connection if advertised. Whem mutt is built with USE="-gnutls" and attempts a TLS connection, let's just say "it does not end well". tldr; It's easier for me to build in gnutls support and then (un)comment one or two lines in ~/.mutt/muttrc as needed rather than... * pop up an xterm * su - (and enter password to root) * emerge mutt with appropriate flag(s) * exit to regular user -- Roses are red Roses are blue Depending on their velocity Relative to you