🚀 go-pugleaf

In article <905725972.4977.0.nnrp-04.d4e48b20@news.demon.co.uk>
           alisdair@nospam.demon.co.uk "Alisdair Wren" wrote:

>A little while ago, Richard Clayton <richard@turnpike.com> digitally said:
>>>  Although 
>>>this line could be recognised not to be a LIST line, if this occurred in 
>>>a message, this could not be trapped by the news client as an error.  
>>>How would you propose dealing with such an eventuality?
>>by applying tolerance {or as the RFC would have it; being "liberal"} :)
>
>Even if being tolerant means ignoring the error?  (It's impossible to 
>trap).

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.

Your idea of printing the last line received wit hthe error message seems
reasonable - I would be tempted to filter it and look for a numeric code
at the start of the line before doing so, but that may be overkill.

Chris C