Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Test rig (Richard Kettlewell)
2. Re: Test rig (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sun, 05 Jul 2015 17:13:59 +0100
From: Richard Kettlewell <[email protected]>
To: [email protected]
Subject: Re: Test rig
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
On 2015-06-27 18:08, Richard Kettlewell wrote:
> I've alluded to this test rig a couple of times. It's now mature enough
> that I'm prepared to let other people see it. It can be found at:
>
> https://github.com/ewxrjk/inntest
>
> Some caveats:
> - It remains a work in progress and is likely to be unstable.
> - It's somewhat tied to my local environment, though I've
> tried to keep this a matter of configuration.
> - I've not tried running it outside Debian sid.
Now with HTML output, for example:
http://www.greenend.org.uk/rjk/junk/news/innfeed.html
('innfeed' represents a test configuration name, not a particular focus
on innfeed.)
ttfn/rjk
------------------------------
Message: 2
Date: Sun, 5 Jul 2015 22:51:15 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Test rig
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Richard,
>> https://github.com/ewxrjk/inntest
That's a pretty useful work, thanks!
> Now with HTML output, for example:
>
> http://www.greenend.org.uk/rjk/junk/news/innfeed.html
Good to know that the outcome column is all OK.
Regarding the response codes:
- I think that's OK for 235 (article accepted) instead of 437 (rejected)
for IHAVE commands in the examples you give (malformed From: and
Expires: headers, and empty body) in order to be conservative in what
has already been injected into Usenet.
- Empty Followup-To: header with POST -> does the resulting article
<[email protected]> contain that empty header?
nnrpd normally removes it.
- Malformed From: header with POST -> could you please tell what is the
malformed header you tried? I think nnrpd should enforce a valid
syntax, so this one is a real bug.
- 435/438/439 instead of 501 to reject articles sent via
IHAVE/CHECK/TAKETHIS is the right legacy behaviour. Doing otherwise
would break backwards compatibility so it shouldn't be encouraged right
now. Maybe in the future...
Thanks again for your test rig!
--
Julien ?LIE
? J'ai fait tous les calculs. Ils confirment l'opinion des
sp?cialistes : notre id?e est irr?alisable. Il ne me reste plus
qu'une chose ? faire : la r?aliser. ? (Pierre-Georges
Lat?co?re, p1906, entrepreneur de l'aviation)
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 74, Issue 1
******************************************
