 | | Re: NNTP Posting Broken?
|
| (...) I've been able to reply via NNTP - in fact, this message is sent that way! :) (...) I'm sure better solutions for SMTP/NNTP users will evolve. The web solution is still good in case you're not working in your natural environment, and as a (...) (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| | | | | Re: NNTP Posting Broken?
|
| (...) I have also posted several messages by NNTP, and I thought I had a pattern established which was confined to responses to Todd's posts (which could have been somehow tripping over the filter he put in place so his ID couldn't be hijacked), and (...) (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| | | | | Re: NNTP Posting Broken?
|
| (...) Hmm, that one actually went through. Let's see if this response does. (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| | | | | Re: NNTP Posting Broken?
|
| (...) Yup, it did. I'm not sure what the heck the pattern is. I hope there's enough stuff in the logs for Todd to diagnose the problem. (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| | | | | Re: NNTP Posting Broken?
|
| "Frank Filz" <ffilz@mindspring.com> wrote in message news:3B2E1051.1F1A@m...ing.com... (...) I've had 1 post go astray and not received an email confirmation for it. This is what I feared might happen - relying on multiple protocols to achieve a (...) (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| | | | | Re: NNTP Posting Broken?
|
| (...) Aha! GOT IT!!! It was totally random and it was happening a LOT. (Now please don't laugh when I tell you what it was :-) (...) It turns out, this was just something stupid that I did. I'm *really* glad this was something that was my fault and (...) (23 years ago, 18-Jun-01, to lugnet.admin.nntp)
| |
