On 20140817_2138-0700, Tom Fowle wrote:
Hi Brendan,
I'd tried that, and did so again, same results
connection refused sasl authentication failed.
thanks anyhow.
tom
Tom Fowle
wa6iv...@fastmail.fm
On Sun, Aug 17, 2014, at 08:51 PM, Brendan Desmond wrote:
On 2014-08-17, Tom Fowle
Hello,
On Sun, Aug 17, 2014 at 01:59:52PM -0500, Russ
Urquhart wrote:
Is there a way to disable mutt from trying to do
this authentication? I know the
smtp_authenticators is a list of methods to try
but does someone know the entire list mutt
enabled SMTP tries? I could maybe list all BUT
On Sun, Aug 17, 2014 at 08:25:30PM -0700, Tom Fowle wrote:
#
# NOTE: to get this to work, I had to install the libsasl2-modules
package
#set smtp_url =smtps://$my_user:$my_pass@$my_smtp_server:465/
set smtp_url = smtps://wa6iv...@mail.messagingengine.com:realpass:465/
Looks to me like
Tom Fowle wa6iv...@fastmail.fm writes:
Same results, sasl authentication failed on both while sending.
I just use this for sending:
set smtp_url=smtps://$my_u...@smtps-proxy.messagingengine.com:80
Seems to work.
-pd
On Mon, Aug 18, 2014 at 07:18:23AM -0700,
Alexander Gattin wrote:
IIRC CRAM and other MD5 auth types work via SASL
because they are not built in mutt.
You can get list of available SASL methods via
e.g. Tcl (you need both tcl and tcllib packages
installed AFAIU):
xrgtn@x505:~$ tclsh
%
On Sun, Aug 17, 2014 at 01:59:52PM -0500, Russ Urquhart wrote:
Hi,
I have Verizon and have been using mutt to send email without problems. As I
understand it, as of 8/1, the Verizon SMTP servers are advertising that
cram-md5 is available when in fact it isn't and this is causing me to
On Mon, Aug 18, 2014 at 06:47:00PM -0700, Bob Holtzman wrote:
Does your ~/.msmtprc file have an auth on entry? If so, is it
commented out? If it's there and not commented out, what does
commenting it out do?
I don't think i have a .msmtprc file, what program is that associated with?
I
