eliana and all; Have tried all the .muttrc configs suggested with same results: find below .muttdebug1 file, no help. mutt -v shows everything wanted to be in the compile. this is a precompiled debian package. sendmail and so on seem to be where needed. I think I'm going to go get a fresh new .muttrc and re-configure it as best i can, possibly with all my thrashing, I've set some contradictory things or the like. here's the debug file thanks especially eliana, Peter and Paul [2014-08-21 19:24:27] Mutt/1.5.21 (2010-09-15) debugging at level 1 [2014-08-21 19:24:27] Reading imaps://mail.messagingengine.com/... [2014-08-21 19:24:27] Looking up mail.messagingengine.com... [2014-08-21 19:24:27] Connecting to mail.messagingengine.com... [2014-08-21 19:24:29] SSL/TLS connection using TLS1.2 (DHE-RSA/AES-256-CBC/SHA256) [2014-08-21 19:24:30] Authenticating (DIGEST-MD5)... [2014-08-21 19:24:30] Logging in... [2014-08-21 19:24:30] Selecting INBOX... [2014-08-21 19:24:30] Unknown right: n [2014-08-21 19:24:30] Fetching message headers... 0/12 (0%) [2014-08-21 19:24:31] Fetching message headers... 10/12 (83%) [2014-08-21 19:24:31] Sorting mailbox... [2014-08-21 19:24:48] Fetching message... [2014-08-21 19:24:48] Fetching message... 0K/8.4K (0%) [2014-08-21 19:24:48] Fetching message... 0K/8.4K (0%) [2014-08-21 19:24:48] WEED is Set [2014-08-21 19:25:23] Include message in reply? ([yes]/no): [2014-08-21 19:25:25] Including quoted message... [2014-08-21 19:29:20] Sending message... [2014-08-21 19:29:20] Mail sent. [2014-08-21 19:29:20] mutt_free_body: unlinking /tmp/mutt-qlf-1000-3519-1811076840113830389. [2014-08-21 19:29:41] 12 kept, 0 deleted. [2014-08-21 19:29:41] Closing connection to mail.messagingengine.com...
Tom Fowle [email protected] On Thu, Aug 21, 2014, at 01:34 AM, Eliana wrote: > 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
