Re: trying repository mutt again
On 11/09/2014 10:53 PM, David Champion wrote: * On 09 Nov 2014, DaleKelly wrote: On 11/09/2014 09:37 PM, David Champion wrote: Debug output might help us figure it out. how can I do this? You need +DEBUG enabled: mutt -v | grep DEBUG it shows +DEBUG This command: mutt -d4 creates ~/.muttdebug0. If you run again, .muttdebug0 is renamed to .muttdebug1, etc. So try against port 465, with your smtp_url set to include your email address as a user name, and show us the contents of .muttdebug0 (or put it on pastebin.org, etc). Your password will be scratched out of the debug file but other personal details may appear -- nothing you haven't shared already though, I think. I just tried it before debug, it works, don't know why it didn't before I'm a hack ... at least I know how to debug it now solution was probably adding the double quotes around the smtp_url=string, and putting my username in the smtp_url THANKS AGAIN, apologies for being such a hack, my attention span isn't as good as it used to be -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
* On 09 Nov 2014, DaleKelly wrote: > On 11/09/2014 09:37 PM, David Champion wrote: > >Debug output > >might help us figure it out. > > how can I do this? You need +DEBUG enabled: mutt -v | grep DEBUG This command: mutt -d4 creates ~/.muttdebug0. If you run again, .muttdebug0 is renamed to .muttdebug1, etc. So try against port 465, with your smtp_url set to include your email address as a user name, and show us the contents of .muttdebug0 (or put it on pastebin.org, etc). Your password will be scratched out of the debug file but other personal details may appear -- nothing you haven't shared already though, I think. -- David Champion • d...@bikeshed.us
Re: trying repository mutt again
On 11/09/2014 09:37 PM, David Champion wrote: Debug output might help us figure it out. how can I do this? -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
* On 09 Nov 2014, DaleKelly wrote: > On 11/09/2014 07:42 PM, DaleKelly wrote: > >got it to work without SSL/TLS in my smtp_url > > the caveats might have been > installing everyone related before ubuntu version > adding "" around the string for smtp_url > no SSL/TSL, and using port 80 instead of 25 I would not advise authenticating without SSL (encryption). Your login credentials have been exposed in cleartext. Port 465 is TLS/SSL with encryption right off the bat, no negotation. Port 587 is usually negotiated TLS (STARTTLS), but this can be offered over port 25. There is no reasonable explanation for SMTP working over port 80. It does appear that your server provides SMTP on port 80, so... ok then. But this is clearly a wacky thing specific to your provider. Virtually nobody does this. It's not normal. I guess they do it to allow customers to relay mail through firewalls that allow port 80 (HTTP) but block SMTP (or think they do). That said, it's clear that they also honor port 465: [1220/1]$ openssl s_client -connect smtpout.secureserver.net:465 -quiet depth=2 C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority verify return:1 depth=1 C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", OU = http://certificates.starfieldtech.com/repository, CN = Starfield Secure Certification Authority, serialNumber = 10688435 verify return:1 depth=0 C = US, ST = AZ, L = Scottsdale, O = "Special Domain Services, Inc.", CN = smtpout.secureserver.net verify return:1 220 p3plsmtpa07-01.prod.phx3.secureserver.net ESMTP quit 221 p3plsmtpa07-01.prod.phx3.secureserver.net closing connection And port 25: [1224/130]$ telnet smtpout.secureserver.net 25 Trying 173.201.192.229... Connected to smtpout.secureserver.net. Escape character is '^]'. 220 p3plsmtpa07-09.prod.phx3.secureserver.net ESMTP starttls 500 command unrecognized quit 221 p3plsmtpa07-09.prod.phx3.secureserver.net closing connection Since port 25 doesn't negotiate TLS, you might continue trying to get 465 to work. I think you're having problems with the SASL authentication here, not with the connectivity itself. Debug output might help us figure it out. -- David Champion • d...@bikeshed.us
Re: trying repository mutt again
On 11/09/2014 06:36 PM, DaleKelly wrote: On 11/09/2014 05:28 PM, JaviMicro wrote: Hi, echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable source: errors in /home/dale/.muttrc SMTP session failed: 530 authentication required Could not send the message. I have needed some days to understand your problem. All we need read carefully the error: smtp_user: unknown variable After reading manual pages of both stable and devel mutt releases: http://www.mutt.org/doc/manual/manual-6.html http://www.mutt.org/doc/devel/manual.html we can see that both imap_user pop_user are valid variables, BUT PLEASE NOTE THAT smtp_user is_not_a_valid_variable!. Please use both email address and SMTP server combined in one line, something like: set smtp_url="smtps://myusern...@dalekelly.org@smtpout.secureserver.net:465" set smtp_pass="MYPASSWORD" Regards -- Javi new errors! thanks much tried this with a fresh install of my ubuntu version mutt 1.5.21-6.4ubuntu2 (I uninstall the dev, and the old ubuntu one, first) I get no errors with echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org (and other emails tried) but no emails received if I use the mutt terminal interface I get SMTP session failed: 550 Sender Rejected - MAIL FROM must be a valid domain added set realname="Dale" set from="d...@dalekelly.org" and get SMTP session failed: 550 Sender Rejected - MAIL FROM must be a valid domain when I install Mutt from the Ubuntu Software Center it says it has ESMTP support and not SMTP the Ubuntu wiki for Mutt says mutt needs an MTA and is Postfix by default, then goes on with SSMTP instructions isn't sendmail a MTA? I know I can't use sendmail with my ISP again, Thunderbird works in both SSL/TLS and no SSL/TLS maybe I will have to try the dev version, 1.5.23 it has documentation of SMTP without mention of MTA got it to work without SSL/TLS in my smtp_url smtp, not smtps the caveats might have been installing everyone related before ubuntu version adding "" around the string for smtp_url no SSL/TSL, and using port 80 instead of 25 I think I might have muddled around this except the url "" THANKS AGAIN EVERYONE -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 07:42 PM, DaleKelly wrote: got it to work without SSL/TLS in my smtp_url the caveats might have been installing everyone related before ubuntu version adding "" around the string for smtp_url no SSL/TSL, and using port 80 instead of 25 I think I might have muddled around this except the url "" THANKS AGAIN EVERYONE -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 07:28 PM, Patrick Shanahan wrote: * DaleKelly [11-09-14 18:59]: On 11/09/2014 06:36 PM, DaleKelly wrote: set from="d...@dalekelly.org" also tried set from="www.dalekelly.org" Why on earth? You didn't try set from="Walt Kelly draws Pogo" Perhaps you should. got it to work without SSL/TLS in my smtp_url THANKS EVERYONE now I'm off to POP want all my SMTP sends saved want all my read POP saved, and left on the server -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
* DaleKelly [11-09-14 18:59]: > On 11/09/2014 06:36 PM, DaleKelly wrote: > >set from="d...@dalekelly.org" > > also tried > set from="www.dalekelly.org" Why on earth? You didn't try set from="Walt Kelly draws Pogo" Perhaps you should. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: trying repository mutt again
On 11/09/2014 06:36 PM, DaleKelly wrote: set from="d...@dalekelly.org" also tried set from="www.dalekelly.org" -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 05:28 PM, JaviMicro wrote: Hi, echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable source: errors in /home/dale/.muttrc SMTP session failed: 530 authentication required Could not send the message. I have needed some days to understand your problem. All we need read carefully the error: smtp_user: unknown variable After reading manual pages of both stable and devel mutt releases: http://www.mutt.org/doc/manual/manual-6.html http://www.mutt.org/doc/devel/manual.html we can see that both imap_user pop_user are valid variables, BUT PLEASE NOTE THAT smtp_user is_not_a_valid_variable!. Please use both email address and SMTP server combined in one line, something like: set smtp_url="smtps://myusern...@dalekelly.org@smtpout.secureserver.net:465" set smtp_pass="MYPASSWORD" Regards -- Javi new errors! thanks much tried this with a fresh install of my ubuntu version mutt 1.5.21-6.4ubuntu2 (I uninstall the dev, and the old ubuntu one, first) I get no errors with echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org (and other emails tried) but no emails received if I use the mutt terminal interface I get SMTP session failed: 550 Sender Rejected - MAIL FROM must be a valid domain added set realname="Dale" set from="d...@dalekelly.org" and get SMTP session failed: 550 Sender Rejected - MAIL FROM must be a valid domain when I install Mutt from the Ubuntu Software Center it says it has ESMTP support and not SMTP the Ubuntu wiki for Mutt says mutt needs an MTA and is Postfix by default, then goes on with SSMTP instructions isn't sendmail a MTA? I know I can't use sendmail with my ISP again, Thunderbird works in both SSL/TLS and no SSL/TLS maybe I will have to try the dev version, 1.5.23 it has documentation of SMTP without mention of MTA -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 04:36 PM, Nathan Stratton Treadway wrote: On Sat, Nov 08, 2014 at 23:59:47 -0500, DaleKelly wrote: * DaleKelly [11-08-14 21:35]: I am using Ubuntu 14.04 LTS mutt 1.5.21-6.4ubuntu2 is the version in the repository [...] here is my error echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /etc/Muttrc, line 145: smtp_user: unknown variable source: errors in /etc/Muttrc SMTP session failed: 530 authentication required Could not send the message. The Ubuntu package includes the manual that goes with that particular version of Mutt; you can read it with $ zless /usr/share/doc/mutt/manual.txt.gz , or by hitting F1 from within Mutt. I looked in that manual on a 14.04 LTS system and found that it does not mention "smtp_user" anywhere. However, a search of the document for "smtp_url" and "URL Syntax" turn up a few sections of the manual that explain how to specify the username as part of the SMTP URL string. Nathan thanks much, I will archive this post so I can get to the docs I seemed to be getting a new error, see my response to Javi -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On Sat, Nov 08, 2014 at 23:59:47 -0500, DaleKelly wrote: > >* DaleKelly [11-08-14 21:35]: > >>I am using Ubuntu 14.04 LTS > >>mutt 1.5.21-6.4ubuntu2 is the version in the repository [...] > here is my error > echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org > Error in /etc/Muttrc, line 145: smtp_user: unknown variable > source: errors in /etc/Muttrc > SMTP session failed: 530 authentication required > Could not send the message. The Ubuntu package includes the manual that goes with that particular version of Mutt; you can read it with $ zless /usr/share/doc/mutt/manual.txt.gz , or by hitting F1 from within Mutt. I looked in that manual on a 14.04 LTS system and found that it does not mention "smtp_user" anywhere. However, a search of the document for "smtp_url" and "URL Syntax" turn up a few sections of the manual that explain how to specify the username as part of the SMTP URL string. Nathan
Re: trying repository mutt again
Hi, > echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org > Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable > source: errors in /home/dale/.muttrc > SMTP session failed: 530 authentication required > Could not send the message. I have needed some days to understand your problem. All we need read carefully the error: smtp_user: unknown variable After reading manual pages of both stable and devel mutt releases: http://www.mutt.org/doc/manual/manual-6.html http://www.mutt.org/doc/devel/manual.html we can see that both imap_user pop_user are valid variables, BUT PLEASE NOTE THAT smtp_user is_not_a_valid_variable!. Please use both email address and SMTP server combined in one line, something like: set smtp_url="smtps://myusern...@dalekelly.org@smtpout.secureserver.net:465" set smtp_pass="MYPASSWORD" Regards -- Javi
Re: trying repository mutt again
On 11/09/2014 02:45 PM, John Niendorf wrote: Is there a reason you do not want to use SSL? SSL wasn't working with my tries at mutt dev, so I tried without it (both work with THunderbird) tried with and without SSL/TLS same error echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable source: errors in /home/dale/.muttrc SMTP session failed: 530 authentication required Could not send the message. will mutt/slrn/bitchx really save me any memory footprint over Thunderbird? my main issue is that sometimes the desktop switcher is slow or freezes when a lot of things are open, I don't even try moving apps across desktops any more with thunderbird I have forwarded my different emails to one I have trimmed down my newsgroups I have set the newsgroups to expire things quicker -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
Interesting. I see on their support web page they say: Outgoing Port Without SSL - one of the following 25, 80, 3535 With SSL - 465 Is there a reason you do not want to use SSL? John On 11/09/2014 08:26 PM, DaleKelly wrote: > On 11/09/2014 03:40 AM, John Niendorf wrote: >> >> The references I found were not mutt specific, but tend to point to a >> problem with GoDaddy in general. > > Thunderbird works fine, with SSL/TLS or without > (have to use port 80 instead of 25 for SMTP without SSL/TLS) >
Re: trying repository mutt again
On 11/09/2014 03:40 AM, John Niendorf wrote: The references I found were not mutt specific, but tend to point to a problem with GoDaddy in general. Thunderbird works fine, with SSL/TLS or without (have to use port 80 instead of 25 for SMTP without SSL/TLS) -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 03:29 AM, John Long wrote: Stepping into the quicksand again for no good reason: On Sat, Nov 08, 2014 at 11:59:47PM -0500, DaleKelly wrote: echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /etc/Muttrc, line 145: smtp_user: unknown variable source: errors in /etc/Muttrc Weird. Very weird. set from = "d...@dalekelly.org" set realname = "Dale" This should not be in your /etc/muttrc! Your global muttrc in /etc or /etc/mutt is supposed to set very few defaults. Everything else is commented out. You are expected to copy that and make whatever customizations are necessary for each mutt user. You don't save your credentials in /etc. got it to recognize mu ~/.muttrc my removing duplicate expressions, still the same error echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable source: errors in /home/dale/.muttrc SMTP session failed: 530 authentication required Could not send the message. set smtp_url=smtp://smtpout.secureserver.net:80 Why are you using port 80 for SMTP? If you are trying to get past an ISP imposed firewall this won't work anyway. It will get you out from your ISP but you will be trying to send email through secureservers webserver. I don't know if it is a workaround but port 25 doesn't work in THunderbird, I have to use port 80 for no SSL/TLS I don't know why you are trying so many versions of mutt. The version you compiled looked fine. It is clearly a problem of authentication, if you have shown us all the messages you are getting. seems like it now, in the Ubuntu wiki it says I need a MTA (mail transport agent), it says it installs Postfix as default, then goes on to configuration of sSMTP MTA the Ubuntu software center says it supports SMTP with ESMTP MTA And I don't know why you are changing so many things at one time instead of taking an orderly step by step approach. I've gone through the variations step by step, I just didn't communicate it that well And now that you have compiled mutt yourself and also installed from packages it is likely you have multiple muttrc files in /etc too. no, I removed the dev version with sudo make uninstall, first I only have one Muttrc and one .muttrc Why don't you make a backup copy of the muttrc in your /home directory and modify the original to contain the bare minimum info needed to specify your userid password and mail server? Get that working first and then start worrying about customizing mutt later. There is a huge pile of crap here and no sign of being able to wade through it. that is what I am working off of /jl -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On 11/09/2014 12:44 AM, Jon LaBadie wrote: On Sat, Nov 08, 2014 at 11:59:47PM -0500, DaleKelly wrote: >On 11/08/2014 10:15 PM, Patrick Shanahan wrote: > >* DaleKelly [11-08-14 21:35]: > >>I am using Ubuntu 14.04 LTS > >>mutt 1.5.21-6.4ubuntu2 is the version in the repository > > [...] much removed > > > >grep -v ^# ~/.muttrc > > > >there is no need of including lines not being actually used! > > > >mutt is not looking at my ~/.muttrc >it is using the global /etc/Muttrc >I don't yet know how to change this > >here is my error > echo "Test" | /usr/bin/mutt -s hellod...@dalekelly.org >Error in /etc/Muttrc, line 145: smtp_user: unknown variable >source: errors in /etc/Muttrc >SMTP session failed: 530 authentication required >Could not send the message. > > More likely mutt is using both. First reading the system's /etc/Muttrc and then your local ~/.muttrc for any personalization. When it encounters an error it may abort and not go furthern. Thus errors in /etc/Muttrc could mean it never gets to ~/.muttrc. I got it to recognize my ~/.muttrc file by removing duplicate expressions, still get echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable source: errors in /home/dale/.muttrc SMTP session failed: 530 authentication required Could not send the message. -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
On Sun, Nov 09, 2014 at 09:40:58AM +0100, John Niendorf wrote: > Having said that, it appears after searching the web that many many > people have trouble sending mail with a GoDaddy account. > Specifically, authentication seems to be problematic. Didn't look at the google reference but the first one has some useful stuff if you ignore the post itself- the guy is a complete idiot for suggesting godaddy's dns resolution is broken given that is the whole purpose for godaddy to exist in the first place. The suggestion that people find out the IP of the mail server and use that instead of the name is just totally ignorant. This is fixing symptoms instead of causes. If you skip past the beginnin there is some good stuff in the responses. The users point out there are sometimes bogus settings in the godaddy control panels for their domains. If Dale got it working through Thunderbird it proves name resolution is not the issue and theoretically he has all the info he needs to get mutt to work as far as credentials go...suggesting it is settings, and nothing else is wrong. Please remove any auth stuff in all copies of your muttrc that tells the mail server what authentication to use and just take the defaults. Your userid and password and the mail server name should be all you need to specify. Mutt works for me on a bunch of mail providers without any confusion or complications. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: trying repository mutt again
John Long raises some good points. It seems pretty haphazard the way things are now. I think I would purge Mutt and Postfix and then start over in an orderly fashion. Having said that, it appears after searching the web that many many people have trouble sending mail with a GoDaddy account. Specifically, authentication seems to be problematic. The references I found were not mutt specific, but tend to point to a problem with GoDaddy in general. http://www.computerrepairhouston.net/wpress/blog/godaddy-smtp-server-problem-get-530-error-cant-authenticate-to-smtpout-secureserver-net/ https://www.google.se/webhp?tab=ww&ei=wiVfVNqmBZDcaqP1gJAC&ved=0CAkQ1S4#q=authentication+error+godaddy+email -- John
Re: trying repository mutt again
Stepping into the quicksand again for no good reason: On Sat, Nov 08, 2014 at 11:59:47PM -0500, DaleKelly wrote: > echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org > Error in /etc/Muttrc, line 145: smtp_user: unknown variable > source: errors in /etc/Muttrc Weird. Very weird. > set from = "d...@dalekelly.org" > set realname = "Dale" This should not be in your /etc/muttrc! Your global muttrc in /etc or /etc/mutt is supposed to set very few defaults. Everything else is commented out. You are expected to copy that and make whatever customizations are necessary for each mutt user. You don't save your credentials in /etc. > set smtp_url=smtp://smtpout.secureserver.net:80 Why are you using port 80 for SMTP? If you are trying to get past an ISP imposed firewall this won't work anyway. It will get you out from your ISP but you will be trying to send email through secureservers webserver. I don't know why you are trying so many versions of mutt. The version you compiled looked fine. It is clearly a problem of authentication, if you have shown us all the messages you are getting. And I don't know why you are changing so many things at one time instead of taking an orderly step by step approach. And now that you have compiled mutt yourself and also installed from packages it is likely you have multiple muttrc files in /etc too. Why don't you make a backup copy of the muttrc in your /home directory and modify the original to contain the bare minimum info needed to specify your userid password and mail server? Get that working first and then start worrying about customizing mutt later. There is a huge pile of crap here and no sign of being able to wade through it. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: trying repository mutt again
On Sat, Nov 08, 2014 at 11:59:47PM -0500, DaleKelly wrote: > On 11/08/2014 10:15 PM, Patrick Shanahan wrote: > >* DaleKelly [11-08-14 21:35]: > >>I am using Ubuntu 14.04 LTS > >>mutt 1.5.21-6.4ubuntu2 is the version in the repository > > [...] much removed > > > >grep -v ^# ~/.muttrc > > > >there is no need of including lines not being actually used! > > > > mutt is not looking at my ~/.muttrc > it is using the global /etc/Muttrc > I don't yet know how to change this > > here is my error > echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org > Error in /etc/Muttrc, line 145: smtp_user: unknown variable > source: errors in /etc/Muttrc > SMTP session failed: 530 authentication required > Could not send the message. > > More likely mutt is using both. First reading the system's /etc/Muttrc and then your local ~/.muttrc for any personalization. When it encounters an error it may abort and not go furthern. Thus errors in /etc/Muttrc could mean it never gets to ~/.muttrc. > anyways, here is the result of what you asked for my /etc/Muttrc > > grep -v ^# /etc/Muttrc > > ignore * > unignore from: subject to cc date x-mailer x-url user-agent > hdr_order date from to cc subject > bind editor"\e"kill-word > bind editor"\e" kill-word > bind editor delete-char > set sort=threads > unset bounce_delivered > set mixmaster="mixmaster-filter" > set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt" > macro index \eb "~b " "search in message bodies" > macro index,pager,attach,compose \cb "\ > set my_pipe_decode=\$pipe_decode pipe_decode\ > urlview\ > set pipe_decode=\$my_pipe_decode; unset > my_pipe_decode" \ > "call urlview to extract URLs out of a message" > macro generic,pager " zcat > /usr/share/doc/mutt/manual.txt.gz | sensible-pager" "show Mutt > documentation" > macro index,pager y "?" "show incoming > mailboxes list" > bind browser y exit > mime_lookup application/octet-stream > set time_inc=250 > attachments +A */.* > attachments -A text/x-vcard application/pgp.* > attachments -A application/x-pkcs7-.* > attachments +I text/plain > attachments -A message/external-body > attachments -I message/external-body > source /usr/lib/mutt/source-muttrc.d| > set from = "d...@dalekelly.org" > set realname = "Dale" > > > > set smtp_url=smtp://smtpout.secureserver.net:80 > set smtp_user=d...@dalekelly.org > > > -- > (my whereabouts below) > http://www.dalekelly.org/ >>> End of included message <<< -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
Re: trying repository mutt again
On 11/08/2014 10:15 PM, Patrick Shanahan wrote: * DaleKelly [11-08-14 21:35]: I am using Ubuntu 14.04 LTS mutt 1.5.21-6.4ubuntu2 is the version in the repository [...] much removed grep -v ^# ~/.muttrc there is no need of including lines not being actually used! mutt is not looking at my ~/.muttrc it is using the global /etc/Muttrc I don't yet know how to change this here is my error echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org Error in /etc/Muttrc, line 145: smtp_user: unknown variable source: errors in /etc/Muttrc SMTP session failed: 530 authentication required Could not send the message. anyways, here is the result of what you asked for my /etc/Muttrc grep -v ^# /etc/Muttrc ignore * unignore from: subject to cc date x-mailer x-url user-agent hdr_order date from to cc subject bind editor"\e"kill-word bind editor"\e" kill-word bind editor delete-char set sort=threads unset bounce_delivered set mixmaster="mixmaster-filter" set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt" macro index \eb "~b " "search in message bodies" macro index,pager,attach,compose \cb "\ set my_pipe_decode=\$pipe_decode pipe_decode\ urlview\ set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \ "call urlview to extract URLs out of a message" macro generic,pager " zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager" "show Mutt documentation" macro index,pager y "?" "show incoming mailboxes list" bind browser y exit mime_lookup application/octet-stream set time_inc=250 attachments +A */.* attachments -A text/x-vcard application/pgp.* attachments -A application/x-pkcs7-.* attachments +I text/plain attachments -A message/external-body attachments -I message/external-body source /usr/lib/mutt/source-muttrc.d| set from = "d...@dalekelly.org" set realname = "Dale" set smtp_url=smtp://smtpout.secureserver.net:80 set smtp_user=d...@dalekelly.org -- (my whereabouts below) http://www.dalekelly.org/
Re: trying repository mutt again
* DaleKelly [11-08-14 21:35]: > I am using Ubuntu 14.04 LTS > mutt 1.5.21-6.4ubuntu2 is the version in the repository [...] much removed grep -v ^# ~/.muttrc there is no need of including lines not being actually used! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
trying repository mutt again
I am using Ubuntu 14.04 LTS mutt 1.5.21-6.4ubuntu2 is the version in the repository after not getting the 1.5.1.23 dev version off mutt.org to work, I am trying the one in the Ubuntu repository there is a discrepancy for SMTP the Ubuntu Spftware Center says it has EMSTP support the ubuntu wiki says the MTA defaults to a Postfix installation, and gives instructions for sSMTP mutt -v shows +USE_SMTP (I removed postfix,ssmtp,mutt in that order) then installed ssmtp and mutt in that order I get the same error as with the dev package echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org SMTP session failed: 530 authentication required Could not send the message. it is looking at the default config file, /etc/Muttrc included below I configured the ssmtp.conf file included below and the output of mutt -v included below # # System configuration file for Mutt # # Default list of header fields to weed when displaying. # Ignore all lines by default... ignore * # ... then allow these through. unignore from: subject to cc date x-mailer x-url user-agent # Display the fields in this order hdr_order date from to cc subject # emacs-like bindings bind editor"\e"kill-word bind editor"\e" kill-word # map delete-char to a sane value bind editor delete-char # some people actually like these settings #set pager_stop #bind pager previous-line #bind pager next-line # Specifies how to sort messages in the index menu. set sort=threads # The behavior of this option on the Debian mutt package is # not the original one because exim4, the default SMTP on Debian # does not strip bcc headers so this can cause privacy problems; # see man muttrc for more info #unset write_bcc # Postfix and qmail use Delivered-To for detecting loops unset bounce_delivered set mixmaster="mixmaster-filter" # System-wide CA file managed by the ca-certificates package set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt" # imitate the old search-body function macro index \eb "~b " "search in message bodies" # simulate the old url menu macro index,pager,attach,compose \cb "\ set my_pipe_decode=\$pipe_decode pipe_decode\ urlview\ set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \ "call urlview to extract URLs out of a message" # Show documentation when pressing F1 macro generic,pager " zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager" "show Mutt documentation" # show the incoming mailboxes list (just like "mutt -y") and back when pressing "y" macro index,pager y "?" "show incoming mailboxes list" bind browser y exit # If Mutt is unable to determine your site's domain name correctly, you can # set the default here. (better: fix /etc/mailname) # # set hostname=cs.hmc.edu # If your sendmail supports the -B8BITMIME flag, enable the following # # set use_8bitmime # Use mime.types to look up handlers for application/octet-stream. Can # be undone with unmime_lookup. mime_lookup application/octet-stream # Upgrade the progress counter every 250ms, good for mutt over SSH # see http://bugs.debian.org/537746 set time_inc=250 ## ## *** DEFAULT SETTINGS FOR THE ATTACHMENTS PATCH *** ## ## ## Please see the manual (section "attachments") for detailed ## documentation of the "attachments" command. ## ## Removing a pattern from a list removes that pattern literally. It ## does not remove any type matching the pattern. ## ## attachments +A */.* ## attachments +A image/jpeg ## unattachments +A */.* ## ## This leaves "attached" image/jpeg files on the allowed attachments ## list. It does not remove all items, as you might expect, because the ## second */.* is not a matching expression at this time. ## ## Remember: "unattachments" only undoes what "attachments" has done! ## It does not trigger any matching on actual messages. ## Qualify any MIME part with an "attachment" disposition, EXCEPT for ## text/x-vcard and application/pgp parts. (PGP parts are already known ## to mutt, and can be searched for with ~g, ~G, and ~k.) ## ## I've added x-pkcs7 to this, since it functions (for S/MIME) ## analogously to PGP signature attachments. S/MIME isn't supported ## in a stock mutt build, but we can still treat it specially here. ## attachments +A */.* attachments -A text/x-vcard application/pgp.* attachments -A application/x-pkcs7-.* ## Discount all MIME parts with an "inline" disposition, unless they're ## text/plain. (Why inline a text/plain part unless it's external to the ## message flow?) ## attachments +I text/plain ## These two lines make Mutt qualify MIME containers. (So, for example, ## a message/rfc822 forward will count as an attachment.) The first ## line is unnecessary if you already have "attach-allow */.*", of ## course. These are off by default! The MIME elements contained ## within a message/* or multipart/* are still examined, even if the ## containers themselves don't qualify. ## #attachments +A message/.* multipart/.* #attachments +I message/.* multipart/.* #