[ 
https://issues.apache.org/jira/browse/JAMES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry reopened JAMES-1222:
---------------------------


No, the issue is NOT FIXED.
james-server-container-spring-3.0-M3-20110506.180441-331-bin POP3 hangs on the 
same mails! The pcap file and the raw mail content I sent to your mailbox.
I also sent another row e-mail, as it appears with question marks instead of 
8-bit characters, just in case.
10-20% of mails I get currently with question marks instead of text, but the 
PROBLEM PERSISTS.
I changed the description of this issue.

8-bit headers and body play no role?
I think that 8-bit content can be returned. For hundreds of millions of mail 
readers it is important. :-)

If you consider it necessary, I can create new issue, but I hope that the 
problem will not hang.

> JAMES hangs on some mails
> -------------------------
>
>                 Key: JAMES-1222
>                 URL: https://issues.apache.org/jira/browse/JAMES-1222
>             Project: JAMES Server
>          Issue Type: Bug
>    Affects Versions: 3.0-M3
>         Environment: Windows XP
>            Reporter: Dmitry
>            Assignee: Norman Maurer
>             Fix For: 3.0-M3
>
>         Attachments: mail.txt, mail_UTF-8.txt, wireshark_UTF-8.txt
>
>
> If JAMES has received some mails, POP3 hangs: error 0x800CCC19 in Outlook 
> Express (timeout) or error 0x8004210A in MS Outlook ('The operation timed out 
> waiting for a response from the receiving (POP) server...'). Using IMAP I get 
> all mails without problem.
> I've seen this problem only on mails with 8-bit content in the body. But on 
> mofified mails with question marks (ASCII code 63) instead of 8-bit 
> characters in the body the problem persists.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to