Call for INN 2.5.2 testing (new NNTP RFC 3977)

Julien ÉLIE julien at
Wed Nov 18 21:11:31 UTC 2009

Hi Ray,

> The closer I look the more I get confused:
> Nov 17 04:47:55 nnrpd[8520]: filter: Checking message <slrn20091109075439.943.twooffive at>
> Nov 17 04:47:55 innd: localhost:172 bad_messageid <slrn20091109075439.943.twooffive at>
> [...]
> Nov 17 13:59:57 nnrpd[3373]: nnn.nnn.nnn.nnn post ok <slrn20091109075439.943.twooffive at>
> This explains why the article exists on the server, but not why it was rejected on the first attempt and accepted on the second.
> Looking at the time, I assume that at 04:47:55 the server was still running inn-STABLE-20091115 and I changed to 
> inn-STABLE-20091116
> some time between 05:00 and 05:30.

The new parser was already in inn-STABLE-20091115 (but not before).
inn-STABLE-20091116 only added logs at two more places in the code.
So it should have changed nothing.

It seems like Mike had problems with Eternal-September only one time
(he posted through aioe):

Date: Sun, 15 Nov 2009 18:00:29 -0500
Message-ID: <slrn20091115175936.69.twooffive at>

All his other posts in 24hoursupport.helpdesk were made through your

I used "XHDR X-No-Bananas 40000-" on aioe to find his posts :)

Did his last post generate a bad_messageid on your server?

Date: Tue, 17 Nov 2009 20:51:28 -0500
Message-ID: <slrn20091117204657.258.twooffive at>

Julien ÉLIE

« Medicorum nutrix est intemperantia. » 

More information about the inn-workers mailing list