<<< Date Index >>>     <<< Thread Index >>>

Re: trouble sending with 1.5.16



Thanks to those who suggest SASL.  I will try this.  I would rather not install 
yet more libraries if I don't have to.  A unix-'locate' search reveals that I 
have some "stuff" in the folder /usr/lib/sasl2 and some files 
/usr/lib/libsasl2*.dylib.  Does anyone know off the top of their heads if those 
will work?

Also, why is it that the new built-in smtp requires SASL (if in fact it does) 
while msmtp does not?

Thanks,
GMN


Thus spake Brendan Cully [06/15/07 @ 16.13.45 -0700]:
> Sounds like you need to enable SASL too.
> 
> On Friday, 15 June 2007 at 17:33, Greg Novack wrote:
> > I'm confused here.  I built 1.5.16 in order to try out the new built-in 
> > smtp 
> > support.  So I used --enable-smtp.  I can't send any mail now, and while 
> > trying to get things to work I've noticed the following:
> >
> > 1. When I use smtp_url=smtp://server.com:587, then mutt won't send mail and 
> > tells me "SMTP session failed: blah blah No AUTH command has been given".
> >
> > 2. When I add a letter and switch to smtp_url=smtps://server.com:587, mutt 
> > won't send mail and tells me "SSL failed: error: blah:SSL 
> > routines:blah:unknown protocol".
> >
> > 3. Adding my username to the smtp_url does not help.
> >
> > 4. I thought maybe I needed to specify an authentication method, but the 
> > variable 'smtp_authenticators' is not recognized (!) by 1.5.16; it gives me 
> > an "unknown variable" error when it tries to read that from my muttrc.
> >
> > Anybody know what's going on?  I checked the wiki and the docs, but to no 
> > avail.  For the record, my old version of mutt is 1.5.12, and I used msmtp 
> > without a hitch.
> >
> > Thanks,
> > GMN

-- 
Greg Novack
University of Wisconsin-Madison
gmnovack@xxxxxxxx
__