>If it is some sort of network congestion problem, then I >will guess that you >may likely see other shortened messages due to a >premature abortion on the >port read (meaning there was momentarily nothing to be >read). >Experimentation will readily reveal if this is a problem.
Hi Scott, I don't think the problem is a network congestion problem as I can download messages both larger/smaller. I can reproduce the problem exactly with the same message, so the error is specific to a particular message. Since Outlook Express is able to download these troublesome messages, I have concluded that the problem is with Rebol. Since my debugging line actually allows me to retrieve the entire message, what I would like to do is return without the tcp error ie. reset whatever flag is flagging an error. I note that if I return from the read-til-dot function after just retrieving one line from any pop read, I get a similar error. So could rebol be flagging an error in both cases because I have not retrieved all the data?? Any ideas??? -- Graham Chiu -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
