Encrypted password auth does not work after update to plesk 10.4.4

[Mick Fish]

Has there been a fix to this as I now have the same problem after an update to 10.4.4 ?

 

[SebastianHeld]

I've the same problem.

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Linux lvps178-77-103-72.dedicated.hosteurope.de 2.6.18-028stab092.1 #1 SMP Wed Jul 20 19:47:12 MSD 2011 x86_64 GNU/Linux
10.4.4 Ubuntu 10.04 1013111102.18

PROBLEM DESCRIPTION
pop3d-ssl announces it supports CRAM-MD5, while it doesn't (or not correctly)

STEPS TO REPRODUCE
Our Intranator Appliance uses fetchmail to retrieve emails. The first attempt always fails (CRAM-MD5) and the second (without CRAM-MD5) succeeds.

ACTUAL RESULT
Error messages in logs and a reject of CRAM-MD5 auth requests.

EXPECTED RESULT
no errors and a correct implementation of CRAM-MD5


A log snippet from /var/log/mail.err

May 2 16:20:56 lvps178-77-103-72 pop3d-ssl: LOGIN FAILED, ip=[::ffff:178.15.21.10]
May 2 16:20:56 lvps178-77-103-72 pop3d-ssl: 1335968456.791047 LOGOUT, [email protected], ip=[::ffff:178.15.21.10], top=0, retr=0, time=0, rcvd=12, sent=39, maildir=/var/qmail/mailnames/lvps178-77-103-72.dedicated.hosteurope.de/sebastian_held/Maildir

The fetchmail log:

fetchmail: 6.3.18 querying mail.sim-gmbh.de (protocol POP3) at Wed, 02 May 2012 15:43:04 +0200 (CEST): poll started
fetchmail: Trying to connect to 178.77.103.72/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Parallels
fetchmail: Issuer CommonName: Parallels Panel
fetchmail: Subject CommonName: Parallels Panel
fetchmail: Server CommonName mismatch: Parallels Panel != mail.sim-gmbh.de
fetchmail: mail.sim-gmbh.de key fingerprint: BC:B5:8A:A6:25:19:08:92:81:EF:BB:AC:B4:00:0F:93
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=US/ST=Virginia/L=Herndon/O=Parallels/OU=Parallels Panel/CN=Parallels Panel/[email protected]) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Parallels
fetchmail: Issuer CommonName: Parallels Panel
fetchmail: Subject CommonName: Parallels Panel
fetchmail: Server CommonName mismatch: Parallels Panel != mail.sim-gmbh.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Hello there. <[email protected]>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Here's what I can do:
fetchmail: POP3< SASL LOGIN CRAM-MD5 PLAIN
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< LOGIN-DELAY 10
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION Courier Mail Server
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< + PDlFNkUzMDgxOTRDQUM1NkE3NjIwRUExOThDQTE0QzRDQGx2cHMxNzgtNzctMTAzLTcyLmRlZGljYXRlZC5ob3N0ZXVyb3BlLmRlPg==
fetchmail: decoded as <9E6E308194CAC56A7620EA198CA14C4C@lvps178-77-103-72.dedicated.hosteurope.de>
fetchmail: POP3> c2ViYXN0aWFuX2hlbGRAbHZwczE3OC03Ny0xMDMtNzIuZGVkaWNhdGVkLmhvc3RldXJvcGUuZGUgZmQxMDZiM2EzYThiNjI4NzYwNTdkZTM0YzNmODg4ZjI=
fetchmail: POP3< -ERR Login failed.
fetchmail: Login failed.
fetchmail: POP3> USER [email protected]
fetchmail: POP3< +OK Password required.
fetchmail: POP3> PASS *
fetchmail: POP3< +OK logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for [email protected] at mail.sim-gmbh.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Bye-bye.
fetchmail: 6.3.18 querying mail.sim-gmbh.de (protocol POP3) at Wed, 02 May 2012 15:43:10 +0200 (CEST): poll completed

The fetchmail log clealy shows, that the password and username are correct (the second login attempt after USER), but that the first try with CRAM-MD5 does not succeed.

 

[Mick Fish]

Mate of mine fixed the problem by making a change to the auth tools that are used ..
the auth tools used no longer supported in php 5.3 so i had to change the Tools it used to auth
'protocol' => 'imap/ssl/novalidate-cert', 'port' => 993,
'protocol' => 'imap/ssl/novalidate-cert', 'port' => 143

'protocol' => 'imap/notls', 'port' => 143,
'protocol' => 'imap/notls', 'port' => 143, 'maildomain'

Just make sure your Horde has it like that and it should work.. Hope this helps

cheers
Mick

 

[SebastianHeld]

Hello Mick,

Horde is not the problem; we use fetchmail to retrieve the mail from the plesk based server.
So this bug remains open.

Kind regards,
Sebastian

 

[Mick Fish]

I believe the problem was the imap not horde sorry.. it should show in your logs where the problem is ..
I will do some more research and see if I can get an easier answer to work with

cheers
Mick

 

[JaimeD]

Any news about this issue?

Are there any news regarding this issue?

I am having exactly the same problem for 2 days now. I have tried everything (even upgrading Plkesk to 11.0.9) with no results. Here is extended information:

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
plesk 11.0.9, CentOS release 5.7 (Final), x64

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
After upgrading from plesk 10.3 to plesk 10.4.4 mail users cannot authenticate in their mail clients. After upgrading from 10.4.4 to 11.0.9 same result.

ACTUAL RESULT
After the plesk upgrade all mail users get a password popup box telling them that they have entered the wrong password. No way to authenticate.

EXPECTED RESULT
The mail server should work.

ANY ADDITIONAL INFORMATION
Just a note that our MTA is set to use qmail now but it was set to Postfix with the same result.

Jul 6 19:18:09 s15391702 /var/qmail/bin/relaylock[9136]: /var/qmail/bin/relaylock: mail from 195.20.253.6:63865 (hosting33.monitoring.1and1.com)
Jul 6 19:41:27 s15391702 pop3d-ssl: Connection, ip=[::ffff:188.76.173.141]
Jul 6 19:41:32 s15391702 pop3d-ssl: IMAP connect from @ [::ffff:188.76.173.141]ERR: LOGIN FAILED, ip=[::ffff:188.76.173.141]
Jul 6 19:41:34 s15391702 pop3d-ssl: Connection, ip=[::ffff:188.76.173.141]
Jul 6 19:41:39 s15391702 pop3d-ssl: IMAP connect from @ [::ffff:188.76.173.141]ERR: LOGIN FAILED, ip=[::ffff:188.76.173.141]
Jul 6 19:41:43 s15391702 pop3d-ssl: Connection, ip=[::ffff:188.76.173.141]
Jul 6 19:41:48 s15391702 pop3d-ssl: IMAP connect from @ [::ffff:188.76.173.141]ERR: LOGIN FAILED, ip=[::ffff:188.76.173.141]
Jul 6 19:42:01 s15391702 imapd: Connection, ip=[::ffff:195.20.253.6]
Jul 6 19:42:01 s15391702 imapd: 1341596521.991544 DISCONNECTED, ip=[::ffff:195.20.253.6], headers=0, body=0, rcvd=0, sent=292, maildir=/etc/rc.d/init.d
Jul 6 19:42:01 s15391702 pop3d: Connection, ip=[::ffff:195.20.253.6]
Jul 6 19:42:02 s15391702 imapd-ssl: Unexpected SSL connection shutdown.
Jul 6 19:42:02 s15391702 pop3d-ssl: Unexpected SSL connection shutdown.
Jul 6 19:42:02 s15391702 /var/qmail/bin/relaylock[9330]: /var/qmail/bin/relaylock: mail from 195.20.253.6:60556 (hosting33.monitoring.1and1.com)

this is the second "big" problem that I have with Plesk Panel and I am considering seriously changing to another solution. The lack of support is exasperating.

 

[IgorG]

http://kb.parallels.com/en/114260

 

[JaimeD]

Thank you for your help IgorG but that's not the problem. All my mailboxes are lowercase.

I have already solved the problem restoring a previous backup (prior to the plesk upgrade) because I couldn't stay any longer without email.