[Dovecot] fetchmail can't talk to dovecot
Hello,
I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have:
protocols = imap imaps pop3,
so why should pop3 or imap fail? Where should I look?
(I'll fix the certificates problem after I've managed to get in successfully with plain imap or pop3)
Thanks,
Marcofetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.server fetchmail: my.server key fingerprint: ... fetchmail: Server certificate verification error: self signed certificate fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> USER user_name fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. fetchmail: Authorization failure on user_name@my.server fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed fetchmail: Query status=3 (AUTHFAIL) fetchmail: Writing fetchids file. fetchmail: normal termination, status 3 fetchmail: Writing fetchids file.
if I try with IMAP the part after the certificate verification error is:
fetchmail: IMAP> A0003 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 fetchmail: IMAP< A0003 OK Capability completed. fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP> A0004 LOGIN "user_name" * fetchmail: IMAP< A0004 NO Authentication failed. fetchmail: IMAP> A0005 * fetchmail: Authorization failure on user_name@my.server fetchmail: IMAP> A0006 LOGOUT fetchmail: IMAP< A0005 BAD Error in IMAP command received by server. fetchmail: IMAP< * BYE Logging out
and I don't see any error message related to this in the server log.
It looks like fetchmail is sending the wrong password....
M. Fioretti [mfioretti@mclink.it] wrote:
Hello,
I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have:
protocols = imap imaps pop3,
so why should pop3 or imap fail? Where should I look?
(I'll fix the certificates problem after I've managed to get in successfully with plain imap or pop3)
Thanks,
Marco
fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.server fetchmail: my.server key fingerprint: ... fetchmail: Server certificate verification error: self signed certificate fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> USER user_name fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. fetchmail: Authorization failure on user_name@my.server fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed fetchmail: Query status=3 (AUTHFAIL) fetchmail: Writing fetchids file. fetchmail: normal termination, status 3 fetchmail: Writing fetchids file.
if I try with IMAP the part after the certificate verification error is:
fetchmail: IMAP> A0003 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 fetchmail: IMAP< A0003 OK Capability completed. fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP> A0004 LOGIN "user_name" * fetchmail: IMAP< A0004 NO Authentication failed. fetchmail: IMAP> A0005 * fetchmail: Authorization failure on user_name@my.server fetchmail: IMAP> A0006 LOGOUT fetchmail: IMAP< A0005 BAD Error in IMAP command received by server. fetchmail: IMAP< * BYE Logging out
and I don't see any error message related to this in the server log.
-- "Do you even send e-mails?" "I told you, I'm from the Wild West. I write by hand." -- Chuck Norris
On Thu, Sep 28, 2006 17:21:31 PM -0700, Chris Cappuccio (chris@nmedia.net) wrote:
It looks like fetchmail is sending the wrong password....
I have the password stored in the browser, so I don't have to type it every time I check email with squirrelmail. I have looked at what firefox transmits thanks to the live http headers extension.
The same password which, sent to squirrelmail via the form, works, doesn't work if I copy it (correcting urlencoding, of course) into the fetchmail script...
What else could it be?
TIA, Marco
Hello,
I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have:
protocols = imap imaps pop3,
so why should pop3 or imap fail? Where should I look?
(I'll fix the certificates problem after I've managed to get in successfully with plain imap or pop3)
Thanks,
Marco
fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.server fetchmail: my.server key fingerprint: ... fetchmail: Server certificate verification error: self signed certificate fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> USER user_name fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. fetchmail: Authorization failure on user_name@my.server fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed fetchmail: Query status=3 (AUTHFAIL) fetchmail: Writing fetchids file. fetchmail: normal termination, status 3 fetchmail: Writing fetchids file.
if I try with IMAP the part after the certificate verification error is:
fetchmail: IMAP> A0003 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 fetchmail: IMAP< A0003 OK Capability completed. fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP> A0004 LOGIN "user_name" * fetchmail: IMAP< A0004 NO Authentication failed. fetchmail: IMAP> A0005 * fetchmail: Authorization failure on user_name@my.server fetchmail: IMAP> A0006 LOGOUT fetchmail: IMAP< A0005 BAD Error in IMAP command received by server. fetchmail: IMAP< * BYE Logging out
and I don't see any error message related to this in the server log.
-- "Do you even send e-mails?" "I told you, I'm from the Wild West. I write by hand." -- Chuck Norris
-- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/
Never let your sense of morals prevent you from doing what is right Salvor Hardin , "Foundation"
On Sat, Sep 30, 2006 17:46:16 PM +0200, io (mfioretti@mclink.it) wrote:
I have the password stored in the browser, so I don't have to type it every time I check email with squirrelmail. I have looked at what firefox transmits thanks to the live http headers extension.
The same password which, sent to squirrelmail via the form, works, doesn't work if I copy it (correcting urlencoding, of course) into the fetchmail script...
Some more details about this, after checking on the server:
When I log in via squirrelmail, with password XYX (controlled through http headers as above) everything is fine.
dovecot.conf contains the section:
protocol imap {
}
POP3 specific settings
protocol pop3 {
Support for dynamically loadable plugins. mail_plugins is a space separated
list of plugins to load.
#mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/pop3
}
Authentication processes
auth_verbose = yes auth_debug = yes
In case of password mismatches, log the passwords and used scheme so the
problem can be debugged. Requires auth_debug=yes to be set.
auth_debug_passwords = yes
auth default { mechanisms = plain digest-md5
passwd-like file with specified location
passdb passwd-file { args = /etc/my_virtual_users #args = }
passwd-like file with specified location
userdb passwd-file { args = /etc/my_virtual_users #args = }
and the only (for now) line in my_virtual_users is:
login_name@the.server:{PLAIN}XYZ:5000:5000::/path/to/virtual/mailboxes
so, if I type login_name@the.server and XYZ in the squirrelmail login window, I am accepted by dovecot. but when I use the same parameters via fetchmail:
poll the.server proto imap user login_name there with pass "XYX" is marco here keep
I am not recognized. Why? Using login_name@the.server in fetchmail, instead of just login_name, doesn't make any difference.
Thanks in advance for any feedback, I'm really going mad over this. If you need excerpts from the log, just ask, but please tell me which lines would be relevant.
Ciao, Marco
-- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/
Non si vive se non il tempo che si ama. C. A. Helvetius
participants (2)
-
Chris Cappuccio
-
M. Fioretti