On Mon, Nov 10, 2014 at 08:41:05PM -0600, Russell Harris wrote: > On Mon, November 10, 2014 5:29 pm, DaleKelly wrote: > > On 11/10/2014 05:58 PM, DaleKelly wrote: > > > >> Login failed. Command USER is not supported by server. > >> > > > > APOP authentication failed.
Where is this coming out? Only on debug output or somewhere else? > > proceeds the above error > > > > although it works!!! > > don't like errors, any help appreciated much So don't try authenticating with APOP. You should not be specifying any pop_authenticators unless you specifically need to. That doesn't happen often. OTOH if you didn't mess this up with some config error then perhaps it is normal as mutt tries various authentication methods (see doc) from most secure to least secure. > > If I recall correctly, POP interface was added to Mutt as an afterthought. > A search on "mutt retrieve pop" reveals that others have found Mutt in the > role of retrieving messages from a POP server to be problematic. I use Mutt with POP heavily (few thousand mails per week from mailing lists) and it works absolutely fine, no issues. I've used it over the years with at least 5 email providers. People just seem to have problems setting up email clients, I don't think mutt is any harder than usual. I mean getting mutt to do exactly what you want is harder but the mail server connection stuff is pretty much the same with every client. Even MS Outhouse needs to have your creds and mail server addresses. > But why waste time with a Mutt function which is questionable, when a good > POP solution is available in getmail? Switch to getmail and be done with > it. Please, Russell ;-) Remember who we're talking to. Simple is good. And mutt's pop support is totally fine. /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
