🚀 go-pugleaf

In article <fanamamkpwm.pminews@sharra>
           noone@llondel.demon.co.uk "Dave {Reply Address in.sig}" wrote:

>On Mon, 14 Sep 1998 16:05:51 GMT, Chris Croughton wrote:
>
>>Yes.  If it's impossible to trap, you can't do anything else.  Just mark
>>the message as not retrieved (e.g. don't store its message ID or article
>>number in the 'read' category) so that it will be fetched gain next time,
>>just as for any other broken connection when downloading.
>>
>So if I chuck a line such as
>
>503 just to upset things
>
>in my posts, it'll screw up things. Not that I often need to start
>lines with an error code, you understand.

No, not at all.  It will only be reportd if it is followed by a dropped
connection, so it is the /last line/ received.  That's what he was saying,
display the last line if the connection is terminated unexpectedly
(normally it should end with CR.CR then the clent sends QUIT and receives
a 250 response.  That's the point - be tolerant in what you receive so
things don't get messed up (and be rigid in what you send so that there's
less chance of them getting messed up in the first place).

>Apologies to anyone that did upset, by the way....

If it did, they wouldn't see your apology!

Chris C