Re: pop(s),smtp(s)
On Mon, Nov 03, 2014 at 08:40:57PM -0500, DaleKelly wrote: > On 11/03/2014 05:18 PM, Grant Edwards wrote: > >You'll need to re-do the configure, build, install steps: > > > >[cd to mutt source directory] > > > >$ ./configure --enable-smtp > >$ make > >$ sudo make install > > previous errors are gone, but it now says smtp needs SASL You have to install the SASL package. It is used for authenticating your password (and maybe your userid, I forget) so you password is transmitted encrypted rather than as normal text. /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: do I need both SSL and SASL?
On Tue, Nov 04, 2014 at 12:45:37AM -0500, DaleKelly wrote: > for SMTPs and POPs? Maybe. SASL is a wrapper so that your email client can present your login credentials to your email server using encryption. Loosely (no pun intended) SSL is a wrapper around the emails your client sends so that only you and the mail server can see the contents. You usually don't have to use SSL but of course it is a good idea to use it whenever you can. > > SSL seems to go through the motions in mutt > > but SASL > SASL authentication failed > > have > set from = "d...@dalekelly.org" > set realname = "Dale" > set pop_pass="pass" > set pop_user="user" Likely should be set pop_user=u...@mail.server.com In other words your real email address. > set pop_host=pops://u...@pop.secureserver.net:995 This may work but in my configs I don't specifiy the user, set pop_host=pops:://pops.your.server > set smtp_url=smtps://u...@smtpout.secureserver.net:465 Should not be necessary to specify the port :465 but otherwise looks ok. > set smtp_user="user" This is not a valid variable in mutt and is not needed. The smtp_url has your userid specified. > set smtp_pass="pass" This is needed. > > > > I get > Error in /home/dale/.muttrc, line 348: smtp_user: unknown variable > when I set smtp user to > set smtp_user="user" > if I comment it out, I just get > SASL authentication failed > > do I need to configure SASL? No. There is a problem in one or more of the variables where you specify your login credentials. Please go over the examples carefully. Mutt's syntax appears to be non-uniform and that could be confusing. > > no error on > set pop_user="user" You can set it to whatever you want but that doesn't mean it will work ;-) Try set pop_user=you@real.email /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: pop(s),smtp(s)
On 11/04/2014 01:37 AM, John Niendorf wrote: Install from the repository and configure the .muttrc file (I would put that file in ~/) This should avoid any problems like mutt not being configured for SMTP. Ubuntu 14.04 LTS the repository doesn't work either I'm down to just: smtp_user SASL authentication error (if smtp_user is commented out) -- (my whereabouts below) http://www.dalekelly.org/
Re: pop(s),smtp(s)
On 11/04/2014 06:56 AM, John Long wrote: On Mon, Nov 03, 2014 at 08:40:57PM -0500, DaleKelly wrote: On 11/03/2014 05:18 PM, Grant Edwards wrote: You'll need to re-do the configure, build, install steps: [cd to mutt source directory] $ ./configure --enable-smtp $ make $ sudo make install previous errors are gone, but it now says smtp needs SASL You have to install the SASL package. It is used for authenticating your password (and maybe your userid, I forget) so you password is transmitted encrypted rather than as normal text. /jl sasl2 was already installed I put it in some configure statement too -- (my whereabouts below) http://www.dalekelly.org/
Re: pop(s),smtp(s)
The version of mutt available from the ubuntu 14.04 repos _DOES_ include smtp support. I am suing it now: jsmith@jsmith:~$ mutt -v | grep -i smtp Configure options: '--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' '--build' 'x86_64-linux-gnu' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2 -I/usr/include/qdbm' +USE_POP +USE_IMAP +USE_SMTP On Tue, Nov 04, 2014 at 07:49:45AM -0500, DaleKelly wrote: > On 11/04/2014 01:37 AM, John Niendorf wrote: > >Install from the repository and configure the .muttrc file (I would put > >that file in ~/) This should avoid any problems like mutt not being > >configured for SMTP. > > Ubuntu 14.04 LTS > > the repository doesn't work either > > I'm down to just: > smtp_user > SASL authentication error (if smtp_user is commented out) > > -- > (my whereabouts below) > http://www.dalekelly.org/ -- Joshua Smith Lead Systems Administrator WVNET (304)293-5192 x247
Re: pop(s),smtp(s)
On 11/04/2014 09:19 AM, Joshua Smith wrote: mutt -v | grep -i smtp I get this mutt -v | grep -i smtp Configure options: '--enable-pop' '--enable-smtp' '--with-sasl' '--with-ssl' +USE_POP -USE_IMAP +USE_SMTP -- (my whereabouts below) http://www.dalekelly.org/
Re: pop(s),smtp(s)
On Tue, Nov 04, 2014 at 12:31:26PM -0500, DaleKelly wrote: > On 11/04/2014 09:19 AM, Joshua Smith wrote: > >mutt -v | grep -i smtp > > I get this > > mutt -v | grep -i smtp > Configure options: '--enable-pop' '--enable-smtp' '--with-sasl' '--with-ssl' > +USE_POP -USE_IMAP +USE_SMTP Is that from the mutt you built by hand or the mutt from apt? At this point its not exactly clear what you've done with regards to installing from the repo or building from source. > > > -- > (my whereabouts below) > http://www.dalekelly.org/ -- Joshua Smith Lead Systems Administrator WVNET (304)293-5192 x247
Re: pop(s),smtp(s)
On 11/04/2014 12:37 PM, Joshua Smith wrote: On Tue, Nov 04, 2014 at 12:31:26PM -0500, DaleKelly wrote: >On 11/04/2014 09:19 AM, Joshua Smith wrote: > >mutt -v | grep -i smtp > >I get this > >mutt -v | grep -i smtp >Configure options: '--enable-pop' '--enable-smtp' '--with-sasl' '--with-ssl' >+USE_POP -USE_IMAP +USE_SMTP Is that from the mutt you built by hand or the mutt from apt? At this point its not exactly clear what you've done with regards to installing from the repo or building from source. the one from hand, I tried the repository but it didn't work and I removed it, and did my configure/make/make install of the source one over I think I need to investigate authentication settings in my ~/.muttrc file, and might have to configure SASL since it has a configuration file too SSL seems to work, but I get this error with SASL SASL authentication failed my be as easy as I don't have smtp_user smtp_pass set to the wrong user/pass, or might be the wrong usage of the statements haven't even got into POP yet, I want my messages left on the server -- (my whereabouts below) http://www.dalekelly.org/
Re: pop(s),smtp(s)
On Tue, Nov 04, 2014 at 06:33:10PM -0500, DaleKelly wrote: > On 11/04/2014 12:37 PM, Joshua Smith wrote: > >On Tue, Nov 04, 2014 at 12:31:26PM -0500, DaleKelly wrote: > >>>On 11/04/2014 09:19 AM, Joshua Smith wrote: > >mutt -v | grep -i smtp > >>> > >>>I get this > >>> > >>>mutt -v | grep -i smtp > >>>Configure options: '--enable-pop' '--enable-smtp' '--with-sasl' > >>>'--with-ssl' > >>>+USE_POP -USE_IMAP +USE_SMTP > >Is that from the mutt you built by hand or the mutt from apt? At this > >point its not exactly clear what you've done with regards to installing > >from the repo or building from source. > > > > the one from hand, I tried the repository but it didn't work and I removed > it, and did my configure/make/make install of the source one over > The repository version has been found to be suitable by many, many different users. No one has been able to get your hand built version to work. Please consider the likelyhood that your previous problems with the repository version were due to your unfamiliarity with mutt configuration. Using the repository version would eliminate one large source of uncertainty. BTW just to be sure, when you say you add things like "set pop_host=pop://u...@pop.secureserver.net:110" to your ~/.muttrc file, that is not literal is it? I.e. it contains your actual pop server's URL and your actual user name at that server, correct? Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
Re: pop(s),smtp(s)
On 11/04/2014 07:02 PM, Jon LaBadie wrote: The repository version has been found to be suitable by many, many different users. No one has been able to get your hand built version to work. Please consider the likelyhood that your previous problems with the repository version were due to your unfamiliarity with mutt configuration. Using the repository version would eliminate one large source of uncertainty. Jon, thanks for your recommendation I had the same configuration problems with the Ubuntu repository one, like the source I have to edit ~/.muttrc , kind of the same problems SSL seems to work SASL either isn't finding an authentication method, or I am not specifying my user/pass correctly in ~/.muttrc I am getting this digest-md5 authentication failed, trying next method SASL authentication failed I originally wanted to switch from Thunderbird since I was having freezes when I used my desktop switcher and mutt/slrn seemed to be some memory footprint I could gain going to put this on the back burner, I slimmed down my Thunderbird, thanks EVERYONE for all the help, and any future recommendations I find no freezes if I select an icon from the icon bar which takes me to the desktop it is on, rather than going to the desktop with the switcher moving a window to a different desktop is the worst freezer, so all I can do is configure my desktops and avoid it, or shut down the window and open it on a new desktop -- (my whereabouts below) http://www.dalekelly.org/
POODLE, SSLv3, TLSv1 and greater
Hi all, Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 and greater? Cheers, Rick -- Rick Valenzuela Videojournalist :: Photojournalist Phnom Penh, Cambodia
Re: pop(s),smtp(s)
* DaleKelly [11-04-14 20:43]: > On 11/04/2014 07:02 PM, Jon LaBadie wrote: > >The repository version has been found to be suitable by > >many, many different users. No one has been able to get > >your hand built version to work. > > > >Please consider the likelyhood that your previous problems > >with the repository version were due to your unfamiliarity > >with mutt configuration. > > > >Using the repository version would eliminate one large > >source of uncertainty. > > Jon, thanks for your recommendation > > I had the same configuration problems with the Ubuntu repository one, > like the source I have to edit ~/.muttrc , kind of the same problems Everyone who installs mutt *must* edit muttrc, it's the nature of the beast. > SSL seems to work > SASL either isn't finding an authentication method, or I am not > specifying my user/pass correctly in ~/.muttrc We will never be able to help you as you decline to give direct and specific answers to *all* of the questions we post. And your password does not have to reside in .muttrc, it will be questioned when necessary. Your claims of many years of linux history are very suspect. Much time is being wasted. :^( -- (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: POODLE, SSLv3, TLSv1 and greater
* Rick Valenzuela [11-04-14 21:12]: > Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 > and greater? ./configure --help -- (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: POODLE, SSLv3, TLSv1 and greater
On Tue, Nov 04, 2014 at 09:19:54PM -0500, Patrick Shanahan wrote: > * Rick Valenzuela [11-04-14 21:12]: > > Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 > > and greater? > > > ./configure --help Thanks, Patrick, but I've looked at that and through the documentation. I'm looking for a way to separate out TLS from SSL. Apparently it is not. What is your understanding of that line in the config help?? -- Rick Valenzuela Videojournalist :: Photojournalist Phnom Penh, Cambodia +855 92 470 702 :: r...@rickv.com GnuPG ID: 0xD5644029
Re: POODLE, SSLv3, TLSv1 and greater
* Rick Valenzuela [11-04-14 21:39]: > On Tue, Nov 04, 2014 at 09:19:54PM -0500, Patrick Shanahan wrote: > > * Rick Valenzuela [11-04-14 21:12]: > > > Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 > > > and greater? > > > > > > ./configure --help > > Thanks, Patrick, but I've looked at that and through the documentation. > I'm looking for a way to separate out TLS from SSL. Apparently it is > not. What is your understanding of that line in the config help?? Sorry, I cannot help here more. I use a packaged version, but have compiled in the past and that is how I determined how to add capabilities/ functions to mutt. I do not have a tar-ball source handy to compile. -- (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: pop(s),smtp(s)
On 11/04/2014 09:16 PM, Patrick Shanahan wrote: Your claims of many years of linux history are very suspect. I said I was a hack ... -- (my whereabouts below) http://www.dalekelly.org/
Re: POODLE, SSLv3, TLSv1 and greater
On Wednesday, 05 November 2014 at 09:09, Rick Valenzuela wrote: > Hi all, > > Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 and > greater? http://dev.mutt.org/doc/manual.html#ssl-use-sslv2
Re: POODLE, SSLv3, TLSv1 and greater
On Tue, Nov 04, 2014 at 09:06:46PM -0800, Brendan Cully wrote: > On Wednesday, 05 November 2014 at 09:09, Rick Valenzuela wrote: > > Hi all, > > > > Is there a way to compile Mutt not to use SSLv3 but instead only TLSv1.1 > > and greater? > > http://dev.mutt.org/doc/manual.html#ssl-use-sslv2 Solved! Thank you! Cheers, Rick -- Rick Valenzuela Videojournalist :: Photojournalist Phnom Penh, Cambodia