The problem is that many NNTP servers are really picky about
message-id's; they won't allow duplicates, and they won't
allow cross-postings with the same message-id. I suppose if
the message had an id we could try to preserve it, attempt a
post, and if that's rejected by the nntpd, we could try
again with our own crafted message-id.
I'm up for any suggestions that are rfc-compliant and work
with the widest range of currently existing nntpds.
The problem is that many NNTP servers are really picky about
message-id's; they won't allow duplicates, and they won't
allow cross-postings with the same message-id. I suppose if
the message had an id we could try to preserve it, attempt a
post, and if that's rejected by the nntpd, we could try
again with our own crafted message-id.
I'm up for any suggestions that are rfc-compliant and work
with the widest range of currently existing nntpds.