Home > Could Not > Could Not Decode Base64 Challenge Fetchmail

Could Not Decode Base64 Challenge Fetchmail

Loaded symbols for /libexec/ld-elf.so.1 #0 0x0807651f in unicodeToString (p=0xe4da729b

of bounds>, len=13049) at smbutil.c:108 108 buf[i] = *p & 0x7f; [New Thread 2887d300 (LWP 100677/fetchmail)] (gdb) backtrace full Chances are that asking NASA's IT helpdesk might provide insights what to use, hint them to losses along the way of migration; chances are that Kerberos support is in place (the fetchmail: POP3> PASS fetchmail: POP3< +OK xxxxxxx has 0 visible messages (0 hidden) in 0 octets. If so, then the > behavior above is correct. http://jessriegel.com/could-not/could-not-decode-a-text-frame-as-utf-8.html

fetchmail.confset postmaster "postmaster"set daemon 1800set logfile /var/log/fetchmail.logset no bouncemaildefaultsproto POP3timeout 90limit 10096000warnings 86400no fetchallpoll mail.domain.deuser "userxx" password "passxx" is "klaus"fetchallpoll mail.domain.deuser "useryy" password "passyy" is "claudia"...=09cu Juergen--=20Mail: ***@telejeck.dePGP Key available--- Juergen Now everything worked fine. Toggle useless messagesView this report as an mbox folder, status mbox, maintainer mbox Report forwarded to [email protected], Benjamin Drieu : Bug#198274; Package fetchmail. Message #29 received at [email protected] (full text, mbox, reply): From: Benjamin Drieu To: Elmar Hoffmann Cc: [email protected], [email protected]n.org Subject: Re: Bug#198274: fetchmail: "could not decode BASE64 challenge" log messages https://www.mhonarc.org/archive/html/fetchmail-friends/2003-05/msg00018.html

Debian bug tracking system administrator . fetchmail: 6.3.21 querying imap02.ndc.nasa.gov (protocol IMAP) at Tue Aug 14 08:27:15 2012: poll completed Merged UID list from imap02.ndc.nasa.gov: fetchmail: Query status=3 (AUTHFAIL) fetchmail: normal termination, status 3 So, it Juergen Edner -- Email: juergen(_dot_)edner(_at_)telejeck(_dot_)de PGP key available --- [Morewiththissubject...] [fetchmail] Re: fetchmail - could not decode BASE64 challenge, Juergen Edner<= Re: [fetchmail] Re: fetchmail - could not Full text and rfc822 format available.

Benjamin Drieu (supplier of updated fetchmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators fetchmail: Issuer CommonName: Entrust Certification Authority - L1C fetchmail: Subject CommonName: Autodiscover.nasa.gov fetchmail: Subject Alternative Name: Autodiscover.nasa.gov fetchmail: Subject Alternative Name: Webmail.nasa.gov fetchmail: Subject Alternative Name: imap02.ndc.nasa.gov fetchmail: Subject Alternative Name: Perhaps a side effect of capabilities > improvements in 6.2.2. If the same problem occursthen you've found a bug, otherwise there's a problem with the binary you'reusing (and you don't say where you got it from).Please DO NOT send me ANY

SSL trusted certificate directory: /usr/local/share/certs Server nonresponse timeout is 300 seconds (default). I upgraded the OpenSSL library from version 0.9.7 toversion 0.9.7.a=20Post by Rob MacGregorCan you provide details of the options you usedfor configure, the first line of "fetchmail -V",the system (OS version To disable NTLM authentication, try adding "auth gssapi" or "auth password" to your rc file. https://forums.gentoo.org/viewtopic-t-57258-start-0.html nl> Date: 2003-07-13 10:14:59 [Download message RAW] Hello, While fetching mail from one of my pop accounts the following message is generated: fetchmail: POP3< +OK ready fetchmail: POP3> CAPA fetchmail: POP3<

fetchmail: POP3> AUTH CRAM-MD5 fetchmail: POP3< -ERR Unknown authentication mechanism: CRAM-MD5 fetchmail: could not decode BASE64 challenge fetchmail: POP3> USER xxxxxxx fetchmail: POP3< +OK Password required for xxxxxxx. Full text and rfc822 format available. You can experiment a bit, by specifying the > username for NTLM authentication in "[email protected]" form, like: > > poll imap02.ndc.nasa.gov proto imap > ...user "[email protected]" ... > > on the Full text and rfc822 format available.

If so, then the > behavior above is correct. http://fetchmail-users.berlios.narkive.com/AZ78X3pN/fetchmail-could-not-decode-base64-challenge Who could help me? They are unneeded as long as the server is trustworthy (or at least assumed not to be malicious), but 6.3.22 will have a more thorough fix against forged replies. > $ Please don't fill out this field.

If the same problem occurs then you've found a bug, otherwise there's a problem with the binary you're using (and you don't say where you got it from). this contact form Old messages will not be flushed before message retrieval (--flush off). fetchmail: IMAP< A0003 OK LOGOUT completed. The issue is that fetchmail does not handle the tagged "A0002 NO ..." response properly, and mistakes it for an NTLM protocol exchange, which it is not.

If he forces Fetchmail to fetch mail from his 10 POP3 accounts the following error message appears for every account (see log excerpt) For debug purposes we enabled debug logging and Acknowledgement sent to [email protected]: Extra info received and forwarded to list. Some things are conceivable as reason, and possibly one is that you need to specify the domain (often called a Windows domain by the responsible IT staff). http://jessriegel.com/could-not/gstreamer-error-could-not-decode-stream.html This is free software, and you are welcome to redistribute it under certain conditions.

Copyright (C) 2002, 2003 Eric S. That's the easy way. :) Re: [fetchmail-users] Fetchmail suddenly started segfaulting with Exchange From: J. There's probably some organizational policy as to how the clients (possibly MS Outlook 2010) are supposed to access the Exchange servers.

Has anything else changed?1.

Message #15 received at [email protected] (full text, mbox, reply): From: Benjamin Drieu To: [email protected] Cc: [email protected] Subject: Re: Bug#198274: Further info - Bug#198274: (fetchmail: BASE64 challenge) Date: Sat, 21 Jun Full text and rfc822 format available. Message #53 received at [email protected] (full text, mbox, reply): From: Elmar Hoffmann To: Benjamin Drieu Cc: [email protected] Subject: Re: Bug#198274: fetchmail: "could not decode BASE64 challenge" log messages Date: Message #48 received at [email protected] (full text, mbox, reply): From: Elmar Hoffmann To: Benjamin Drieu Cc: [email protected] Subject: Re: Bug#198274: fetchmail: "could not decode BASE64 challenge" log messages Date:

Tags added: pending Request was from Benjamin Drieu to [email protected] Full text and rfc822 format available. If the same problemoccurs then you've found a bug, otherwise there's a problem with thebinary you're using (and you don't say where you got it from).I compiled both versions from source Check This Out fetchmail: Certificate chain, from root to peer, starting at depth 2: fetchmail: Issuer Organization: Entrust.net fetchmail: Issuer CommonName: Entrust.net Certification Authority (2048) fetchmail: Subject CommonName: Entrust.net Certification Authority (2048) fetchmail: Certificate

It's starting to get weird, while the messages did go away at first, fetchmail after some hours consumed a lot of CPU (probably all of it, if there weren't other things It ends up base64 decoding the error response, which should > not succeed either, and then processing it, which causes the segfault. > > You are right that fetchmail must not Terms Privacy Opt Out Choices Advertise Get latest updates about Open Source Projects, Conferences and News. Acknowledgement sent to Benjamin Drieu : Extra info received and forwarded to list.

[email protected] DA1 3LN URL http://cbc.homelinux.com/stats ================================= Information stored: Bug#198274; Package fetchmail. fetchmail: 6.2.2 querying pop.ntlworld.com (protocol POP3) at Sun Jul 6 12:31:43 2003: poll completed fetchmail: 6.2.2 querying pop.ntlworld.com (protocol auto) at Sun Jul 6 12:31:43 2003: poll completed fetchmail: not swapping It seems to be an error which only appears if Fetchmail is fetching mail from his providers mail server (Qpopper v4.0.3) I'm using the same Fetchmail binary to fetch mail from