Re: sending to fastmail with mutt
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 uses gnuTLS, and not OpenSSL I don't know if using gnuTLS could be a source of problems, maybe other readers of these list can comment. > I can get the hash, > but when trying to assemble the commands for the openssl tests, I can't > get everything set up using speech output and/or braille manipulating > cuts > and pastes > before the openssl times out > Is it relevant that I can read mail with ssl correctly? Ok, I will rephrase my former mail (I am not an english native speaker, so excuse if some part of my emails are not clear). After reading your mails, I understand you have problems accessing SMTP servers of fastmail.fm. But, you can use webmail interface of fastmail.fm (web browser using port 80 or port 443) without problems. With openssl test, you can check if conections to port 465 or port 587 (SMTP ports) of fastmail are blocked by your ISP: -if openssl test is successfull, you can asure the network path between your machine and fastmail servers is OK -if openssl test give your errors, the problem is in your network, not in mutt configuration Some evil ISPs block all ports, with the exception of HTTP/s ports (80 and 443). So, openssl is only a quick test to discard errors in your network. Of course, if you use other tools (msmtp or similar, Thunderbird ever) that make connections to ports 465 or 587 of fastmail, you don't have an evil ISP, and your network is good. > Don't understand what you mean by "fastmail control panel?" don't have > such I know of. Sorry, I don't know internal configuration of fastmail accounts. With "fastmail control panel" I wanted to define some place in your account, after you have logged with a web browser, when you maybe can enable/disable the use of SMTP service for your account. In Gmail control panel, you can enable/disable the access to your emails by IMAP and POP protocols changing the state of a buttom: if you configure it to "disabled" state, you can not use mutt/Thunderbird/whatever to read your mails, you can only use webmail access. Regards -- Javi
Re: again on mutt "sasl" problem with isp
* On 15 dic 2014, M. Fioretti wrote: > On 2014-11-16 00:20, David Champion wrote: > >* On 15 Nov 2014, M. Fioretti wrote: > >>Greetings, > >> > >>almost one year ago, I had a problem with mutt, so I asked for help > >>here, describing it in detail, see (1) below. It received one answer > >> > > > >For debugging, don't set smtp_pass at first. > > before I "forget" about this for another year... > > first of all, thanks to David and the others who answered, both this > and the first time. > [...] > > So, when I'll have the opportunity to visit again, I will surely > repeat the procedures as David suggested, checking what happens without > the password is the most viable option. For now, everything stays > on hold. > On one of your previous emails, you are using 'out.alice.it' as SMTP server. So I will assume that your friend's ISP is Telecom Italia, whose parameters can be found at: http://assistenzatecnica.telecomitalia.it/at/portals/assistenzatecnica.portal?_nfpb=true&_pageLabel=ProblemiBook&nodeId=/AT_REPOSITORY/348010&radice=consumer_root http://assistenzatecnica.telecomitalia.it/at/portals/assistenzatecnica.portal?_nfpb=true&_pageLabel=GuideBook&radice=consumer_root&nodeId=/AT_REPOSITORY/22041 SMTP: out.alice.it:587 username: yourfri...@alice.it password: >From my machine, I try connection to out.alice.it: $ nc out.alice.it 587 220 smtp201.alice.it ESMTP Service ready help 214-Valid SMTP commands: 214- HELO, EHLO, NOOP, RSET, QUIT, STARTTLS 214- MAIL, RCPT, DATA, VRFY, EXPN, HELP, ETRN 214-For more info, use HELP 214 end of help Similar answer from port 25. No response from 465 port. Let's try with openssl: $ openssl s_client -connect out.alice.it:587 CONNECTED(0003) 2074:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:618: Second try: $ openssl s_client -connect out.alice.it:587 -starttls smtp CONNECTED(0003) didn't found starttls in server response, try anyway... 2077:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:618: Strange (same command with "smtp.gmail.com:587" is successfull). Third try: $ openssl s_client -connect out.alice.it:587 -starttls smtp -debug [...output reformated to be clearer] 250-smtp202.alice.it 250-DSN 250-8BITMIME 250-PIPELINING 250-HELP 250-AUTH=LOGIN 250-AUTH LOGIN CRAM-MD5 DIGEST-MD5 PLAIN [...] STARTTLS 500 STAR command unrecognized Problem with STARTTLS?? Anyone can check it? Conclusion: try this sintax: smtp://yourfri...@alice.it@out.alice.it:587 or smtp://yourfri...@alice.it@out.alice.it:25 -- Javi
Re: Setting user variable in muttrc
* On 11 ene 2015, Danny wrote:
> Hi guys,
>
> I have setup a .muttrc in /etc/skel (Debian). My problem is that everytime I
> create a user and .muttrc is copied to the newly created user's home dir I
> still
> have to do some editing involving the user's name etc.
>
> What is the mutt variable for a user:
>
> For example : I want "set from = "u...@domain.com"" to be automatically set.
> I tried "%u...@domain.com" but that is not working ...
>
> Any pointers?
>
Some possible solutions:
#1
set from = `whoami`@domain.com # with backticks
#2
set from = $u...@domain.com # with environmental variables
set from = $logn...@domain.com
#3
set my_user = `whoami` # combination
set from = $my_u...@domain.com
Use additional double quotes ("bla bla") if some element has spaces
or other problematic characters.
Re: mutt for mailing list archive
* On 6 feb 2015, Honggyu Kim wrote: > Hi, > > I have started using mutt since a few days ago. > Is is possible to use mutt on mailing list archive? > Yes, it is possible > I would like to see the entire mailing list on lkml and gcc, etc. > I can only see what I have received since I subsciribed thoes mailing > list. There are two separate steps: STEP 1 - obtain the mailing list archives Some maillists give you archives in mbox format, compatible with mutt. For example: http://www.syslinux.org/archives/ or https://www.redhat.com/archives/fedora-list/ gives you maillist archives by month in downloadable versions (gzipped) Some times, access to mbox format is hidden: http://stackoverflow.com/questions/13097891/open-source-project-for-downloading-mailing-list-archives-preferably-in-python Other maillists consider maillist archives as "sensible data", and only gives you HMTL browseable archives; mbox format is only accesible by administrator. See: http://sourceforge.net/p/forge/documentation/Mailing%20List%20Archives/ For these maillists with "HTML-only" archives, there are some ugly tricks for converting to plain text: http://comments.gmane.org/gmane.mail.mailman.user/74089 https://github.com/luisibanez/CommunityAnalyzer/tree/master/lkml STEP 2 - using mutt to read maillist in mbox format mutt -f /path/to/mailist.txt Regards -- J
