Re: My typical .muttrc frustrations
Erik Christiansen wrote: On 17.04.17 22:34, Charles E Campbell wrote: Here's the result: ... Could not send the message. Well, it's never occurred to me to pause to figure out how to use mutt to send email on the command line, because the MUA I used before mutt was traditional unix "mail"¹, and it is infinitely easier to just apt-get that. A "man mail" shows that it's: bsd-mailx - simple mail user agent that I'm using ATM. As /usr/bin/bsd-mailx is only 92 kB in size, it doesn't add much ballast to mutt 1.8.0 at 2.46 MB. Mind you, it may just be that running an MTA here (postfix these days) is what avoids your problems. That was easy to set up after the first effort, given that I keep a few notes to avoid excessive brow furrowing next time round. ¹ It was what we had on HP-UX and Solaris boxes back in the 1980s, and it still works the same. Hello, Erik: I tried both mail and mailx. Both fail silently when I attempt to send an email off my machine (didn't try mailx, but mail will send email to accounts on the same machine), although I suppose its possible they're still re-trying somewhere in the background and won't get a failure email for a few days. That's why I had been using mutt until recently. I have two potential smtp(s) targets, but neither works with mutt. For example, both smtp targets fail with: SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-SHA) digest-md5 authentication failed, trying next method external authentication failed, trying next method anonymous authentication failed, trying next method SASL authentication failed Could not send the message. Regards and thank you for looking into this, Chip Campbell
Re: My typical .muttrc frustrations
lilydjwg wrote: On Sun, Apr 16, 2017 at 06:48:34PM -0400, Charles E Campbell wrote: Hello: It was tricky, but I got my .muttrc working so that I could send stuff out via the command line. Until about two weeks ago, where mutt suddenly stopped sending out email and started complaining instead. To shorten the story: this is what I use with Seamonkey. Works fine. Description : astronaut Server Name : outgoing.verizon.net Port : 465 Connection Security : SSL/TLS Authentication Method : Normal password User Name : astronaut Of course, there is a password involved and its stored in Seamonkey's passwords file. Now, on to .muttrc: [...] You can see my some of my attempts at getting mutt to talk via smtp and messing around with smtp authenticators. None of them work. Would someone please help? Try this one? set smtp_url="smtps://astron...@verizon.net@outgoing.verizon.net:465" Here's the result: cec/ fsp#06 djinni? tstmutt.cfb SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-GCM-SHA384) external authentication failed, trying next method anonymous authentication failed, trying next method plain authentication failed, trying next method Connection to outgoing.verizon.net closed digest-md5 authentication failed, trying next method No authenticators available Could not send the message. That's better than what I had been getting: (after a long pause) Connection to outgoing.verizon.net closed SMTP session failed: read error Could not send the message. Thank you, Chip Campbell
My typical .muttrc frustrations
Hello: It was tricky, but I got my .muttrc working so that I could send stuff out via the command line. Until about two weeks ago, where mutt suddenly stopped sending out email and started complaining instead. To shorten the story: this is what I use with Seamonkey. Works fine. Description : astronaut Server Name : outgoing.verizon.net Port : 465 Connection Security : SSL/TLS Authentication Method : Normal password User Name : astronaut Of course, there is a password involved and its stored in Seamonkey's passwords file. Now, on to .muttrc: #set smtp_url="smtp://smtp.verizon.net:465" #set smtp_url="smtps://astron...@smtp.verizon.net:465" #set smtp_url="smtps://astron...@outgoing.verizon.net:465" #set smtp_url="smtp://astron...@outgoing.verizon.net:465" #set smtp_url="smtp://outgoing.verizon.net:465" set smtp_url="smtp://outgoing.verizon.net:465/" set smtp_pass="ELIDED" set from="astron...@verizon.net" set realname="C Campbell" set editor="gvim" set move=no set smtp_authenticators="external:anonymous:plain:otp:skey:digest-md5:scram:ntlm:gssapi:browserid-aes128:eap-aes128" ignore "Authentication-Results:" ignore "DomainKey-Signature:" ignore "DKIM-Signature:" hdr_order Date From To Cc alternative_order text/plain text/html * set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set smart_wrap=yes set sort='threads' set sort_aux='last-date-received' # vim: ft=muttrc You can see my some of my attempts at getting mutt to talk via smtp and messing around with smtp authenticators. None of them work. Would someone please help? Thank you, Chip Campbell
Re: got mutt to compile, but won't authenticate
Cameron Simpson wrote: On 04Jan2014 20:30, Tom Furie t...@furie.org.uk wrote: On Sat, Jan 04, 2014 at 12:28:46PM -0500, Charles E Campbell wrote: However, mutt still doesn't recognize header_cache or certificatg_file (again, undefined variables), and it still won't send mail. I'm not very familiar with this side of mutt, but are you sure that certificatg_file isn't a typo? Looks like a typo to me. Also, it seems worth pointing out that: ./configure --help usually lists the app specific options. You may need to have a patched mutt source for some options; not sure. Yes, there was a typo: its actually set certificate_file=~/.mutt/certificates and the mutt with my latest configuration settings does accept it. I'm still getting cec/ djinni? tstmutt.verizon Certificate host check failed: certificate owner does not match hostname smtp.campbellfamily.biz Memory fault(coredump) where tstmutt.verizon is a script: #! /bin/ksh mutt -s [testing] tstmutt astron...@verizon.net -EOM Hello! This is a test using my tstmutt script. Does it work? Regards, Me EOM So far I am unable to join with the mutt world... Regards, Chip Campbell
got mutt to compile, but won't authenticate
Hello! I used David Champion's suggestion to compile mutt with: --enable-smtp so at least its not complaining about smtp_pass and smtp_url being undefined variables (Thanks!). However, mutt still doesn't recognize header_cache or certificatg_file (again, undefined variables), and it still won't send mail. Here's my .muttrc: set smtp_url=smtp://myusern...@verizon.net@smtp.verizon.net:465 set smtp_pass=MYPASSWORD set from=myusern...@verizon.net set realname=MYNAME set editor=gvim ignore Authentication-Results: ignore DomainKey-Signature: ignore DKIM-Signature: hdr_order Date From To Cc alternative_order text/plain text/html * #set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies #set certificatg_file=~/.mutt/certificates set smart_wrap=yes set sort='threads' set sort_aux='last-date-received' WIth this, mutt hangs for several minutes, finally issuing: Connection to smtp.verizon.net closed SMTP session failed: read error Could not send the message. I've also tried it with set smtp_url=smtp://myusern...@smtp.verizon.net:465 ...same... and got the same message. BTW, the port number, etc is correct, and is what I'm using with Seamonkey's email. Of course, I can't use the latter via the command line. Help would be appreciated! Regards, Charles Campbell
Re: got mutt to compile, but won't authenticate
Suvayu Ali wrote: On Sat, Jan 04, 2014 at 12:28:46PM -0500, Charles E Campbell wrote: Hello! I used David Champion's suggestion to compile mutt with: --enable-smtp so at least its not complaining about smtp_pass and smtp_url being undefined variables (Thanks!). However, mutt still doesn't recognize header_cache or certificatg_file (again, undefined variables), and it still won't send mail. You are probably missing a few other flags; I used to call configure like this: $ ./configure --datarootdir=/usr/share --sysconfdir=/etc \ --enable-dependency-tracking --enable-fcntl --disable-flock \ --enable-hcache --with-tokyocabinet --enable-smtp --enable-pop \ --enable-imap --with-gss --with-gnutls --with-sasl --with-curses \ --disable-external-dotlock --enable-gpgme; Hope this helps, It has helped, but the problem isn't quite solved as yet: at least the complaints about header_cache and certificate_file variables have gone away. Thank you! I wasn't able to use --enable-gpgme or --with-tokyocabinet; configure complained. Also, --enable-dependency-tracking was not found. May I note that I have two email accounts (the one associated with this email and the one I mentioned in my earlier note). The verizon one continues to give me Connection to smtp.verizon.net closed SMTP session failed: read error Could not send the message. However, the second one yielded me a core dump: Core was generated by `mutt -s [testing] tstmutt astron...@verizon.net'. Program terminated with signal 11, Segmentation fault. #0 menu_redraw_full (menu=0xe5c780) at menu.c:168 168 SETCOLOR (MT_COLOR_NORMAL); Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-13.el6.x86_64 db4-4.7.25-17.el6.x86_64 glibc-2.12-1.132.el6.x86_64 gnutls-2.8.5-10.el6_4.2.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-10.el6_4.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 libgcrypt-1.4.5-11.el6_4.x86_64 libgpg-error-1.7-4.el6.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-5.3.el6.x86_64 libtasn1-2.3-3.el6_2.1.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64 nss-softokn-freebl-3.14.3-3.el6_4.x86_64 zlib-1.2.3-29.el6.x86_64 Regards, Charles Campbell P.S. I got some warnings during the compilation process (they didn't look serious): || keymap.c: In function ‘km_dokey’: keymap.c|455 warning| label ‘gotkey’ defined but not used || keymap.c: In function ‘init_extended_keys’: keymap.c|689 warning| passing argument 1 of ‘tigetstr’ discards qualifiers from pointer target type || /usr/include/ncursesw/ncurses.h:792: note: expected ‘char *’ but argument is of type ‘const char *’ main.c|73 warning| string length ‘558’ is greater than the length ‘509’ ISO C90 compilers are required to support || mbox.c: In function ‘mbox_reset_atime’: mbox.c|693 warning| unused variable ‘i’ || lib.o: In function `mutt_mkwrapdir': lib.c|569 warning| the use of `mktemp' is dangerous, better use `mkstemp' || lib.o: In function `mutt_mkwrapdir': lib.c|569 warning| the use of `mktemp' is dangerous, better use `mkstemp'
Re: got mutt to compile, but won't authenticate
Suvayu Ali wrote: On Sat, Jan 04, 2014 at 12:28:46PM -0500, Charles E Campbell wrote: Hello! I used David Champion's suggestion to compile mutt with: --enable-smtp so at least its not complaining about smtp_pass and smtp_url being undefined variables (Thanks!). However, mutt still doesn't recognize header_cache or certificatg_file (again, undefined variables), and it still won't send mail. You are probably missing a few other flags; I used to call configure like this: $ ./configure --datarootdir=/usr/share --sysconfdir=/etc \ --enable-dependency-tracking --enable-fcntl --disable-flock \ --enable-hcache --with-tokyocabinet --enable-smtp --enable-pop \ --enable-imap --with-gss --with-gnutls --with-sasl --with-curses \ --disable-external-dotlock --enable-gpgme; May I mention a few more things: * the configure command I'm currently using: ./configure \ --datarootdir=/usr/share \ --sysconfdir=/etc \ --disable-external-dotlock \ --enable-debug \ --enable-fcntl \ --disable-flock \ --enable-hcache \ --enable-imap \ --enable-pop \ --enable-smtp \ --with-curses \ --with-gnutls \ --with-gss \ --with-sasl \ --with-ssl * With my other email, with suitable changes to smtp_user and smtp_password, I'm getting: Certificate host check failed: certificate owner does not match hostname smtp.campbellfamily.biz Memory fault(coredump) and gdb says: #0 menu_redraw_full (menu=0x1766bf0) at menu.c:168 168 SETCOLOR (MT_COLOR_NORMAL); I see that SETCOLOR is a macro which expands to attrset(ColorDefs[MT_COLOR_NORMAL]) and gdb further says: (gdb) p ColorDefs[MT_COLOR_NORMAL] $2 = 0 (gdb) p ColorDefs[6] $3 = 0 I have a number of routines which use curses, so -lcurses on the link line works (ldd says mutt is using libncursesw.so.5). Regards, Charles Campbell
core dumps and can't build
Hello! I've been trying to use mutt from my home computer (it works ok from my work computer). Both use Scientific Linux 6.3. All I get on my home computer is core dumps. Here's my test: echo TESTING | mutt -s '[testing] 1-2-3' drchip-@-campbell-family-biz (in the email: remove first three -s, change last one to a period). along with a .muttrc: set smtp_pass=ELIDED set smtp_url=smtp://smtp.campbellfamily.biz:587 set from=drchip-@-campbell-family-biz set realname=C Campbell set editor=gvim set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set smart_wrap=yes set sort='threads' set sort_aux='last-date-received' The core dumps don't do me much good; the mutt I'm using came via a yum install, so it uses hex addressing. ~/.mutt/cache exists, but no headers, bodies, or certificates. I tried commenting out sort, header_cache, message_cachedir, and certificate_file but that doesn't stop the core dumping. I tried building mutt myself (mutt 1.5.21); it builds, but blesses me with: Error in /home/cec/.muttrc, line 1: smtp_pass: unknown variable Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable source: errors in /home/cec/.muttrc sh: /usr/local/bin/mutt_dotlock: No such file or directoryError in /home/cec/.muttrc, line 1: smtp_pass: unknown variable Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable source: errors in /home/cec/.muttrc sh: /usr/local/bin/mutt_dotlock: No such file or directory Couldn't lock /home/cec/sent Could not send the message. I'd appreciate some help! Thank you, Chip Campbell Couldn't lock /home/cec/sent Could not send the message.
mutt's refusal to write files
Hello! I've been having a bit of a problem with mutt-1.0.1-us ; its been refusing to save mail. At first it was refusing to write (ie. append) email via symbolic links to files; lately its been refusing to save at all. Elm doesn't have this problem (which I fire up just to save email), so its nothing to do with permissions, etc. Just in case its something I've done in my .muttrc, I've included a uuencoded/gzipped copy of it. Thank you for looking into this! Dr C - begin 600 .muttrc.gz M'XL(`%=T+3D``UU206[,`P\QZ\@LH=ZFX_X`?TD$O;0P\!`EFBUVPDT2"E MW1@H\O92=EPTT40-.1P..*I.\/50LF\)PGNE1QA3C#1!%A8H'6DIWZBPN MX.1J+!!)"_`$,[J`8I$8@T)AN"$N,V8(9`NT:V4+Y9*E\R"#\))[@'08]T MM4@K6#"7'A(E[*\HV@IK:4JO/1OAX2J[H(]A8-(,;Z@A,*9H]JQU(E]XLK MLZG+J$TN)3(A#(C`R6YL3/_AAA:EFW]KLDO/"0$;X`H\XPJ?SJVTM72G% M^G]^E6ABGV?XT?X8\B5\/9XT"VF5SY"G6(!-[*4IYH3!S+?PK`VK1L2RE3 MWUX/7])9OKVTBE7\0COWRP`Q66X4IINVXEAVA;5?/R[IQMXL9SA*,]L%1 M/'OTW'DK_XX?O]=USBVO_D78^:T$'K^!M]:79XCBSZN?V[-TF*W6E[`A1A MN;NS?RS2S`P!SDF!B_N@QCK/^2S#SRSAJ`G?CK%G*@RFS30/86C%OEFN J\\\';(*3BPV%BZ!-VTYQPHMV184V^:/L#[6+6UPSOW7\,,JL)`P`` ` end --------- -- Charles E Campbell, Jr, PhD_ __ __ Goddard Space Flight Center / /_/\_\_/ / [EMAIL PROTECTED] /_/ \/_//_/ PGP public key: http://www.erols.com/astronaut/pgp.html/
attempt to build mutt-1.3i failed
Hello! I tried to build mutt-1.3i on an old Indigo^2 (SGI, Irix 5.3). It failed because a number of files attempt to include mbyte.h which doesn't exist on my machine. Regards, Dr C -- Charles E Campbell, Jr, PhD_ __ __ Goddard Space Flight Center / /_/\_\_/ / [EMAIL PROTECTED] /_/ \/_//_/ PGP public key: http://www.erols.com/astronaut/pgp.html/
