On Wed, Aug 20, 2014 at 09:53:30PM -0700, Tom Fowle wrote: > Eliana and all, > You are correct I'd missed the 'My_server" in the smtp url, but that > didn't > fix the basic problem.
I have not automated sending with mutt, I do it by invoking msmtp separately, and also do not use IMAP, but the basics of debugging I think would include making sure you have enabled IMAP and sending the same way on both ends. > I've tried every combination of imap smtp sending setups people have > reccommended and nothing works. > I get either "connection refused" or an apparrent send with no errors > wherein the message just doesn't arrive. I do not understand the difference between SSL and SASL but I know that I had to declare the correct location of my SSL certificates file(s) in my msmtprc for things to work with my setup. Possibly you did not reinstall the certificate file, or the name or location or permissions changed with the upgrade. So make sure you have checked that in the appropriate rc file. Again, I do not send directly with mutt, so I declared that in my msmtprc file. > Should I start a trace or some such of a sending attempt, and if so how > do I > go about that? starting mutt with strace would show system calls, but I am not sure if it would show you what you need to know. The man page for my Mutt says that for debugging, you can start it with a -d option but only if you compiled in that option, did you? > Also, is it necessary when upgrading mutt to start with a new copy of > the > current muttrc file and modify that? or will .rc files that work with a > slightly older version work with the latest stable release? The same as with any application, it really depends on whether approved syntaxes and file locations have changed. eliana
