• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

QMAIL and CRAM-MD5

F

Freelander

Guest
hello,

i have a big problem, i updated plesk via the updater 2 days ago and i think in this update qmail was updated´.

since the update CRAM-MD5 authentication via smtp wont work.

login via telnet on port 25 says:

220 XXXX.com ESMTP
EHLO test
250-XXXX.com
250-AUTH LOGIN CRAM-MD5 PLAIN
250-AUTH=LOGIN CRAM-MD5 PLAIN
250-STARTTLS
250-PIPELINING
250 8BITMIME
AUTH CRAM-MD5
334 PDE3NzYyLjEwNjk5Mzc3MTNAbG9jYWxob3N0Pg==


all mail-client i use say when i send a mail "authentication failiure" only when i use cram-md5, because i think its more safe. plain there iss no problem.

so i used the CRAM-MD5 authentication tester from http://www.net-track.ch/opensource/cmd5/ and generated the md5 hash and its a other then i find in the file called /var/qmail/user/passwd.

if i try to login with the md5 hash from /var/qmail/user/passwd (i used copy & paste) i have no problems and he says "mailformed input". so it seems to work.

but why are in /var/qmail/user/passwd other md5 hashs?
.. i think this is the problem, the different hashs.

has anybody a solutions?

sorry for my bad english. ;-)

BTW: i used plesk 8 on a SuSE 9.3 -64 edition
 
Hi all,

i still have the same problem.
Yet in my case it only concerns several domains...

I would be glad for a solution
 
the only solution i found was to use smtp after pop - IMHO you can only use cram -md5 if you have a passwd file in plain text, but its encoded and so its in my opinion impossible to use cram-md5.
 
Back
Top