cant store article: bogus Xref: header in INN 2.5 ?

[Matija Nalis]

On Thu, Sep 08, 2011 at 08:16:25PM +0200, Julien ÉLIE wrote:
> This patch for Xref: header field fixes the regression introduced
> in INN 2.5.0.  The behaviour for the Xref: header field will be
> the same as it was in INN 2.4.x.
> 
> I hope the above proposal of "fix" is fine for your needs.  INN 2.5.2 will
> work fine with it in xrefslave mode.

Great, thanks!  

I've patched the server, and so far it's been running without throttling for
36 hours, so it does look fixed (it used to throttle itself at least one a
day, usually few times a day).  

I'll leave it running with no load for couple more days, and then I'll turn
it back in the production to see how it fares.

> I also believe it is the safest fix to do right now, just before an upcoming
> release of INN 2.5.3.  Properly testing extensive changes in the Xref: parsing
> code in an RFC 5536 way need time.  (And is no longer a blocking issue, now that
> the legacy parsing of Xref: is used again.)

yes, this looks like best patch to me too. I'll let you know if anything
suspicious pops up in this setup. Thanks again!

-- 
Opinions above are GNU-copylefted.