Re: [Logicmail-users] LogicMail 1.9.1.213
Brought to you by:
octorian
Menu
▾
▴
Re: [Logicmail-users] LogicMail 1.9.1.213
|
From: Peter P. <plp...@ya...> - 2010-10-15 18:16:18
|
Ok, I got the problem. Weird, but it screwed up other clients too. Alpine is one of the few which handle it right. I think that one has to implement the \r\n line termination detection required by RFCs, and not rely on \n alone in headers. Although that IS weird nowadays. Strange godaddy are not exactly script kiddies. Maybe it's a temporary bug introduced by an update, but I do not believe to be the only one to have noticed it.
Thanks for answering, looking forward to a solution.
-- Peter
--- On Fri, 10/15/10, Derek Konigsberg <dko...@lo...> wrote:
Yes, and testing now. It looks like you have a very weird POP
server. I'll mention details here, in case anyone else is curious.
With a normal POP server, the login sequence is like such:
----
+OK <12...@fo...> mail.foo.com [CR][LF]
USER jdoe[CR][LF]
+OK[CR][LF]
PASS password[CR][LF]
+OK Mailbox locked and ready[CR][LF]
----
But with your POP server, it looks like this:
----
+OK <12...@ba...>[CR][LF]
USER jdoe[CR][LF]
+OK[CR][LF]
PASS password[CR][LF]
+OK qmail-pop3d-gemini 1766: auth_init: login=jdoe,
authdata=password[LF][LF]
+OK qmail-pop3d-gemini 1766: Pod 7 Gemini_POP, country: '' found in
the auth database[LF][LF]
+OK[CR][LF]
----
That awkwardly terminated/separated multi-line response to the PASS
command is what's screwing up LogicMail. I now need to fix my
line-termination-handler code to detect and work around this
situation.
-Derek
|
