Hi Davide, I have been using XMail for about ages now... may be from the age of = Xmail 0.2 or so, but never came across such kind of a bug. A maildrop in one = of the user's directory showed size as 170kb. However the content of it was nothing but a '.'. I have no idea how that=92s possible, i.e. how XMail = missed writing data to the file (maybe not), it happened on windows and is = quite possible, but that=92s not the point.
The point is when xmail is feeding mail drop to MUA. Consider following session: +OK <[EMAIL PROTECTED]> [XMail 1.25 POP3 Server] service ready;=20 +Sat, 19 May 2007 12:59:06 +0530 user [EMAIL PROTECTED] +OK Password required for [EMAIL PROTECTED] pass xxxxxxx +OK Maildrop has 1 messages (173113 bytes) retr 1 +OK 173113 bytes .. retr 1 +OK 173113 bytes .. quit +OK [XMail 1.25 POP3 Server] closing session When such session happens the XMail becomes unresponsive and will always reply with -Err Server too Busy, if any other user tries to suck mail = from the server, the client is always presented with -Err Server Too Busy.=20 I thought of going through the code, but thought best would be asking = the 'Source'. Is it a bug or one of those _very rare_ occasions? Thanks ~XT Step to Reproduce the bug: 1. Create a file of size 200kb. Maybe you can just allocated a buffer of about 200kb. Zero it out completely, assign the first 3-4 of bytes as = '.', \0, \r\n and drop it in any of the test user. 2. Try to access the file. Meanwhile try to access other user's mails. 3. Server will reply with -Err Server Too Busy. =A0 - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
