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
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, -- Suvayu Open source is the future. It sets us free.
mutt native SMPT support vs Postfix?
Recent posts made me aware of the fact, that mutt supports SMPT. So far I have been using postfix for mail transport. Which way is better, and why? Thanks for advice, ulrich
Re: mutt native SMPT support vs Postfix?
On 2014-01-04 19:35:19 +0100, Ulrich Lauther wrote: > Recent posts made me aware of the fact, that mutt supports SMPT. > So far I have been using postfix for mail transport. > Which way is better, and why? "Better" is subjective. Using Postfix for this is pretty heavy duty over using a purpose-built MTA. Some argue that having an SMTP client in Mutt is against the Unix philosophy, and that by default Mutt should only manipulate local storage. I am not part of this camp, but I understand it, at least. If by "better" you mean "simpler", I would put a vote in for the latter. That way you have all of your e-mail configuration in one place. pgpBVVL4gi6qA.pgp Description: PGP signature
Re: mutt native SMPT support vs Postfix?
El día Sunday, January 05, 2014 a las 02:50:12AM +0800, Chris Down escribió: > On 2014-01-04 19:35:19 +0100, Ulrich Lauther wrote: > > Recent posts made me aware of the fact, that mutt supports SMPT. > > So far I have been using postfix for mail transport. > > Which way is better, and why? > > "Better" is subjective. Using Postfix for this is pretty heavy duty over > using a purpose-built MTA. > > ... I'm using mutt (right now by typing) on my FreeBSD netbook, connected via UMTS WAN to my ISP. My mutt drops the mail (this mail) to the local MTA (sendmail) and this takes care for the transport to the next MX hop, even if the WAN link is down; the mail gets queued until the link comes up again. I think this, queuing, is a big advantage over talking SMTP directly by mutt. matthias -- Sent from my FreeBSD netbook Matthias Apitz, , http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
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
Re: got mutt to compile, but won't authenticate
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? Cheers, Tom -- Reporter: "What would you do if you found a million dollars?" Yogi Berra: "If the guy was poor, I would give it back." signature.asc Description: Digital signature
Syncing settings, different folder-hooks on different machines
Hi, I sync my settings between different machines via Dropbox. I have settings for several accounts and each in its own file. When I open a specific inbox via a macro like macro index 'imaps://acco...@mailserver.com/INBOX' I use a folder-hook to source a specific account file folder-hook 'mailserver.com' 'source ~/.mutt/account.mailserver.com' (while .mutt is a symlink to a folder in my Dropbox) Since those account-files are in my Dropbox-account, I don't have passwords saved in there. But when using mutt from my personal laptop, I'd like to source the following file: ~/.mutt_local/account.mailserver.com because in there I have set the passwords. Because I already have special settings for my personal laptop I have a .muttrc on my personal laptop that sources all the appropriate files, instead of relying solely on the muttrc in the Dropbox It looks right now like this: source ~/Dropbox/Dotfiles/mutt/muttrc source ~/Dropbox/Dotfiles/mutt/sidebar source ~/Dropbox/Dotfiles/mutt/gpg.rc source ~/Dropbox/Dotfiles/mutt/gpg_special auto_view text/html I thought now that I could fit in a special file with folder-hooks that overwrites the folder-hooks in ~/Dropbox/Dotfiles/mutt/muttrc by adding source ~/.mutt_local/local_folderhooks right after sourcing ~/Dropbox/Dotfiles/mutt/muttrc but it doesn't work. Any ideas how I could solve this? I mean synced settings for different machines but having on one machine separate folder-hooks for the accounts, so account-files with passwords get sourced. Thanks, Niels pgppShE0JZbLf.pgp Description: PGP signature
Re: got mutt to compile, but won't authenticate
On 04Jan2014 20:30, Tom Furie 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. Cheers, -- Cameron Simpson Hit the button Chewie! - Han Solo
Re: mutt native SMPT support vs Postfix?
On 04Jan2014 20:01, Matthias Apitz wrote: > El día Sunday, January 05, 2014 a las 02:50:12AM +0800, Chris Down escribió: > > On 2014-01-04 19:35:19 +0100, Ulrich Lauther wrote: > > > Recent posts made me aware of the fact, that mutt supports SMPT. > > > So far I have been using postfix for mail transport. > > > Which way is better, and why? > > > > "Better" is subjective. Using Postfix for this is pretty heavy duty over > > using a purpose-built MTA. > > I'm using mutt (right now by typing) on my FreeBSD netbook, connected > via UMTS WAN to my ISP. My mutt drops the mail (this mail) to the local > MTA (sendmail) and this takes care for the transport to the next MX hop, > even if the WAN link is down; the mail gets queued until the link comes > up again. I think this, queuing, is a big advantage over talking SMTP > directly by mutt. I agree. I'm running postfix on my Mac (it ships with postfix installed). Local queuing. Automatic retry accordidng to a sensible policy. AND:... All the local systems that send email (eg cron and innumerable shell scripts) can send email via the UNIX standard "sendmail" executable. Use a real mail system locally. A win. Cheers, -- Cameron Simpson I swear to god, officer, I'm fixing this bridge. Just go divert traffic.
Re: mutt native SMPT support vs Postfix?
On 2014-01-04 20:01:56 +0100, Matthias Apitz wrote: > I'm using mutt (right now by typing) on my FreeBSD netbook, connected > via UMTS WAN to my ISP. My mutt drops the mail (this mail) to the local > MTA (sendmail) and this takes care for the transport to the next MX hop, > even if the WAN link is down; the mail gets queued until the link comes > up again. I think this, queuing, is a big advantage over talking SMTP > directly by mutt. Well, that's exactly what I was recommending -- using something like sendmail over something which is designed for far more (Postfix). I typically don't use my computer when offline, so having a local mail queue would not be a big win for me over occasionally having to save outgoing e-mails to a local file when offline (which has happened about twice in the last two years). pgprWIxXP9cTU.pgp Description: PGP signature
