On 20.11.14 14:09, Will Fiveash wrote:
If you are using vim you may want to add vim settings specific to
editing mail from within mutt to a file like
~/.vim/ftplugin/mail/mail-settings.vim. vim will assign by default
the filetype mail to mutt editor files and look for plugins in
Javin,
Here's the output of the printf
linux-gate.so.1 = (0xb7767000)
libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5
(0xb771f000)
libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xb76ff000)
libgssapi_krb5.so.2 =
Update:
Javin,
I hope I assembled the openssl test into an ssh script
the result ended with (about)
return code 0 O.K.
so, it appears I do have proper ssl connection with fastmail, now I
guess
back to why my .muttrc doesn't send.
Guess I'll try setting up msmtp with example provided here.
thanks
Hi Tom,
Reading the output of ldd $(which mutt) executed on your machine,
I can not see nothing wrong. Relevant lines:
libgnutls.so.26 = /usr/lib/i386-linux-gnu/libgnutls.so.26
libsasl2.so.2 = /usr/lib/i386-linux-gnu/libsasl2.so.2
show us that:
-libSASL is accesible,
-your mutt
Hi Erik!
On Fr, 21 Nov 2014, Erik Christiansen wrote:
On 20.11.14 14:09, Will Fiveash wrote:
If you are using vim you may want to add vim settings specific to
editing mail from within mutt to a file like
~/.vim/ftplugin/mail/mail-settings.vim. vim will assign by default
the filetype
Hi Javi,
thanks for the clarifications, I believe I follow what you're saying
now.
So it appears, if I've done things correctly that I can get ssl connect
on
port 465
but I may have to run through tests again to be sure I've done them
correctly.
Will have to call our isp to see what ports they
