[email protected] wrote:
but this is the trouble, i think AUTHINFO command is not RFC 2980 compliant - For news.alphanet.org and all OK servers for my test (see fr.test for a list ;), the NNTP server answers a 480 error when a "POST" command is asked - Your server respond 340 OK and refuse mail after and not before...
This is really a limitation of the nntp protocol.
ok
The problem is dnews can be configured to allow posting
to a subset of news groups, as such, it's impossible for it to
know when you say 'post' if you are going to
try and send a message to one of the groups you are permitted
to post to or not.
Ok, but the trouble was the message was "lost" when DNEWS send the famous 480 code... my software (who is RFC compliant)
send AUTHINFO and after DNEWS send a 501 code :-(
the author of my software refuse to modify his software so it is DNEWS to respect RFC :-)
so DNEWS develloper must program this software to keep the message in memory after sending 480 code and destroy "message" if next user command is not AUTHINFO USER -or- if AUTHINFO USER or PASS is bad :-)
The person running the server in question can change the access rules so that it will behave in an rfc compliant way, but that is the manager of that servers choice, they may instead choose to have the extra functionality at the cost of not working with a few nntp clients.
I don't see how your suggested solution would help. Did the author of the client in question suggest it would fix it ?
ChrisP.
