I had exactly the same experience with the update package for Suse 6.3.
After I upgraded, Windows users where locked out, because their Netscape
version support APOP. Mac users did not experience a problem, because the
ydid not have APOP. (If this is an advantage, remains to be discussed :->)
Rainer
Simone Grabstein
Sent by: suse-security-return-2003-rhoerbe=netpromote.co.at@suse.com
26.06.00 20:13
To: suse-security@suse.com
cc:
Subject: [suse-security] qpopper and APOP (starting to bore, ah?!)
There has been a discussion (quite recently) about
QPOP and APOP support, and the whole thing seemed to
had been settled with the release of the
"pop-2000.6.7-0.i386.rpm" package.
Well, I confidently downloaded the above mentioned RPM
and upgraded a server of mine.
While tryng to create the /etc/pop.auth database, I
was STILL getting that boring "unable to open POP
authorization DB".
After browsing through several newsgroup and
mailing-list archives, I reached the conclusion that I
*HAD* to upgrade to QPOP 3.02.
Thus, I downloaded the sources from Qualcomm's site,
compiled and - enough said - popauth worked
seamlessly.
Did anybody else have analogue experiences?
(To Thomas Biege: did you have some positive feedback
about SuSE's update?).
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-security-unsubscribe@suse.com
For additional commands, e-mail: suse-security-help@suse.com
