WONDERFUL,NEWS!!!!!!

I have just downloaded and installed 4.61, and all these problems are solved.

Thank you very much to David and the rest of the team.

Now looking forward for version 5.

Best Regards

Miguel

A site has changed server - and now I can not download selcetive mails - I got the headers ok. But when selecting for download (without delete!) I got nothing!

The following is the log:

20:06:36.673 >> 0016 +OK logged in.\0D\0A
20:06:36.673 << 0006 STAT\0D\0A
20:06:36.705 >> 0013 +OK 6 36896\0D\0A
20:06:36.705 << 0006 LIST\0D\0A
20:06:36.736 >> 0055 +OK POP3 clients that break here, they violate STD53.\0D\0A
20:06:36.736 >> 0008 1 1387\0D\0A
20:06:36.736 >> 0008 2 1962\0D\0A
20:06:36.736 >> 0009 3 29580\0D\0A
20:06:36.736 >> 0008 4 2505\0D\0A
20:06:36.736 >> 0007 5 885\0D\0A
20:06:36.736 >> 0007 6 577\0D\0A
20:06:36.736 >> 0003 .\0D\0A
20:06:36.736 << 0008 UIDL 1\0D\0A
20:06:36.767 >> 0103 +OK 1 1296591655.M338753P12274V0000000000000014I00000000008DD5A3.pemlinmail01.tdcw.opa.tdch.dk,S=1351\0D\0A
20:06:36.767 << 0008 UIDL 2\0D\0A
20:06:36.783 >> 0101 +OK 2 1296605980.M601600P2553V0000000000000012I00000000008DD5A4.pemlinmail03.tdcw.opa.10n.dk,S=1910\0D\0A
20:06:36.783 << 0008 UIDL 3\0D\0A
20:06:36.814 >> 0104 +OK 3 1296638662.M696143P19004V0000000000000014I00000000008DD5A5.pemlinmail01.tdcw.opa.tdch.dk,S=29062\0D\0A
20:06:36.814 << 0008 UIDL 4\0D\0A
20:06:36.845 >> 0102 +OK 4 1296687125.M864307P15599V0000000000000012I00000000008DD5A6.pemlinmail03.tdcw.opa.10n.dk,S=2437\0D\0A
20:06:36.845 << 0008 UIDL 5\0D\0A
20:06:36.876 >> 0100 +OK 5 1296733561.M602862P7202V0000000000000013I00000000005CBF4F.PEMLINMAIL02.tdcw.opa.10n.dk,S=866\0D\0A
20:06:36.876 << 0008 UIDL 6\0D\0A
20:06:36.907 >> 0023 +OK 6 UID6-1296735540\0D\0A
20:06:36.907 << 0006 QUIT\0D\0A
20:06:36.923 >> 0014 +OK Bye-bye.\0D\0A
20:06:36.923 --- Connection closed normally at Thu, 03 Feb 2011 20:06:36. ---\0A\0A
 

Normally the UIDL responce would be

"+OK 1 xxx\0D\0A"

where xxx is a session msg id. The length of the string shall be less than 70 bytes... This is longer!

Could that cause Pmail to just not send a "RETR" command?

 Or is it the STD53 violation that in some way is disturbing Pmail?

I can get the mail with Outlook - and all my other Pmail accounts works ok. As seen from the log this could not be caused by what OS is used or some other such cause.

The new server is at "qmail.tdcwebmore.se" if any help...

Anyone that knows the inside of Pmail?

/ArneLj

I have found another site where 2 of 4 mails had longer UIDL lines than 70 bytes...

The 2 with short lines can be fetched but not the other ones. So the long line in UIDL is what causes Pmail to just ignore sending the RETR command!

/ArneLj

RFC 2449 could be an answer:

   This specification increases the length restrictions on commands and
   parameters imposed by RFC 1939.

   The maximum length of a command is increased from 47 characters (4
   character command, single space, 40 character argument, CRLF) to 255
   octets, including the terminating CRLF.

   Servers which support the CAPA command MUST support commands up to
   255 octets.  Servers MUST also support the largest maximum command
   length specified by any supported capability.

   The maximum length of the first line of a command response (including
   the initial greeting) is unchanged at 512 octets (including the
   terminating CRLF).

 The last sentence to be observed...

/ArneLj

As you've already surmised, the UID being generated by the Courier POP3 server is totally illegal (96 characters, where the maximum allowed is 70). Note that the length extensions in RFC2449 don't alter the maximum allowable length of the UID, which is still 70 characters - they only impact the maximum length of entire command lines.

I try very hard to write my code so that it complies with the RFCs that govern it, but then I seem to spend an awful lot of my time modifying that code to accommodate other developers who either can't read, or don't care. :-(  I've now extended the maximum UID length WinPMail will accommodate to 150 characters, which I would hope would be enough for any imaginable scenario. This fix will appear in v4.61, which we're in the late stages of finalizing for release.

Cheers!

-- David --

[quote user="David Harris"]As you've already surmised, the UID being generated by the Courier POP3 server is totally illegal (96 characters, where the maximum allowed is 70). Note that the length extensions in RFC2449 don't alter the maximum allowable length of the UID, which is still 70 characters - they only impact the maximum length of entire command lines.

I try very hard to write my code so that it complies with the RFCs that govern it, but then I seem to spend an awful lot of my time modifying that code to accommodate other developers who either can't read, or don't care. :-(  I've now extended the maximum UID length WinPMail will accommodate to 150 characters, which I would hope would be enough for any imaginable scenario. This fix will appear in v4.61, which we're in the late stages of finalizing for release.

Cheers!

-- David --

[/quote]

David! 

Really looking forward the the 4.61 you mention above - especially the fix for problems with replying, forwarding and printing emails from senders with an email system not fully complying with the standrads! Any news on when we can start to download the new version??

Best regards from Stockholm, Sweden!

Jon R