On 06/03/2012 10:30, Vladimir Panteleev wrote: <snip>
(An alternative explanation might be that your client might be placing the message in the outbox and retrying automatically in the background.)
It's a plausible explanation if it's the kind of error that happens _only_ on posting. But no program can do this when reading a 'group and make it look to the user as if a message has been downloaded when it hasn't.
Though one possibility is that some newsreader polls the server at intervals in the background and automatically downloads all messages. Then you might notice only when you manually trigger a poll, or when you try to read a message that hasn't downloaded because the connection crashed between downloading new headers and downloading the message body.
Though a well-made newsreader would still indicate to the user in some way that there's been a problem, as much as it may try to lessen the inconvenience to the user.
Stewart.
