 | | Re: posting failure?
|
|
(...) Did you post from the web interface or send it in by e-mail? I guess only the web interface sends you a copy of your e-mail, and the news-by-mail gateway only writes you back when there was a problem. Lemme check the server logs... Hmm, the (...) (26 years ago, 2-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) I submitted by the web. I'm hesitant to post the entire dat file as it is 566 lines and everytime I include it my post doesn't seem to make it. 8( I could possibly attach it if you want. Your web address (lehman@javanet.com) keeps getting (...) (26 years ago, 3-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) What web browser are you submitting this from? I'll hafta mess around and try to recreate the problem. I think BramL was having the same problem a few weeks ago...but I think that was a Juno e-mail problem. In the meantime, try e-mailing the (...) (26 years ago, 3-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) writes: (...) gotten a (...) rather (...) only (...) a (...) the (...) 566 (...) could (...) I'm using IE5b2, but it's never given me a lick of trouble before. I've gone ahead and sent the file, we'll see if it makes it. The rejection message (...) (26 years ago, 4-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) You e-mailed the .DAT file to lugnet.cad.dat@lugnet.com then? Veddy veddy odd...it hasn't shown up in the ng, and it doesn't appear in the dead- articles file (the rejects file) on the server. It's as if it never made it to the server. Do you (...) (26 years ago, 4-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
Todd Lehman writes: Would you try uploading the raw .DAT file here?-- (...) Todd, Well, it's uploaded. Sorry for the long delay. Had to recover from a nasty hard drive crash. Anyway, it's up there. Since I seem to be bombing out still (I tried to (...) (26 years ago, 8-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) Well, this bug is certainly interesting. (Thank you for discovering this, BTW.) I've got the problem narrowed down to a file size limitation of approximately 16.5 KB in an NNTP connection library. I know that it's not a bug somewhere in the (...) (26 years ago, 8-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) Getting closer...I have a workaround. I'll have to talk to the authors of the Net::Cmd module to be absolutely certain about the nature of the problem, but I think I see it clearly now. The post() method of Net::NNTP goes like this[1]: sub (...) (26 years ago, 8-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) Todd, Thanks for all your hard work to diagnose this problem. I've sent off the file via email again, so we'll see if it works now. Thanks again, Ben. (26 years ago, 10-Feb-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) Well, what I wrote above in February was not entirely correct. It is necessary (at least on this system) to FLUSH the socket's buffer when it becomes full. I am not very knowledgeable about sockets in Perl, and it's not a well-documented area, (...) (26 years ago, 12-Apr-99, to lugnet.admin.general)
|
| |
| | Re: posting failure?
|
|
(...) Hold that thought! (...) Well, I feel pretty stoopit now for making the above post -before- doing more stress testing. :-/ A 595KB file I just posted (to a faux group) dropped a few lines in the middle. This bug is out of my league. I'm not (...) (26 years ago, 12-Apr-99, to lugnet.admin.general)
|
