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: RE : Re: hide headers (Nick Edwards)
2. Re: hide headers (Russ Allbery)
3. Re: Inn-Current-20140910 issues (Julien ?LIE)
4. Re: hide headers (Nick Edwards)
5. Re: Inn-Current-20140910 issues (Russ Allbery)
6. Re: Inn-Current-20140910 issues (The Doctor)
----------------------------------------------------------------------
Message: 1
Date: Wed, 10 Sep 2014 22:19:38 +1000
From: Nick Edwards <[email protected]>
To: Julien ?LIE <[email protected]>
Cc: [email protected]
Subject: Re: RE : Re: hide headers
Message-ID:
<CAMD-=vk-sqxea98xmiheftnpxomoe_oila-0wbzmo_1xvxh...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Morning,
True, but we have been used to dnews being able to overrideall these
things, including the domain in message-id to protect and anonymize
the users, and our users would probably expect that to continue, so in
our test lan we are trying to throw everything we can at it, to ensure
it can do exactly what we have been doing for great many years
already.
Nik
On 9/10/14, Julien ?LIE <[email protected]> wrote:
> Hi Nick,
>
> Did you have a look at pine configuration on jupiter? It seems that the
> user-domain parameter in pine config files could be useful.
> The posting agent provides the message-ID when posting a message.
>
> --
> Julien
>
> -------- Message d'origine --------
> De : Nick Edwards <[email protected]>
> Date :
> A : Russ Allbery <[email protected]>
> Cc : [email protected]
> Objet : Re: hide headers
>
>
>
>>> (jupiter is the dev areas second box, using root user posting to
>>> local.test using pine)
>
> Now the path is done the only thing remaining is the message-id being
> remote still, not the news server, perhaps I'm on information
> overload, and need to walk away till morning, but this one I cant find
> any option to deal with it.
>
------------------------------
Message: 2
Date: Wed, 10 Sep 2014 07:56:25 -0700
From: Russ Allbery <[email protected]>
To: Nick Edwards <[email protected]>
Cc: [email protected]
Subject: Re: hide headers
Message-ID: <[email protected]>
Content-Type: text/plain
Nick Edwards <[email protected]> writes:
> We only have the localhost and custs auth/access's none others, but I
> did fix the problem by stop / start, reload did not seem to do it?
> Now the path is done the only thing remaining is the message-id being
> remote still, not the news server, perhaps I'm on information
> overload, and need to walk away till morning, but this one I cant find
> any option to deal with.
Right, the message ID can be provided by the client and it potentially
seriously breaks the NNTP protocol for the server to override the client's
choice of message ID. (The server doesn't know whether the client is
offering the same message ID to multiple servers.)
You can probably do something with a posting filter by editing the
headers, but there isn't (and won't be) a built-in option for changing the
message ID because it's a protocol violation and could result in duplicate
messages (in scenarios that you probably aren't worried about).
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
------------------------------
Message: 3
Date: Wed, 10 Sep 2014 19:05:36 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Inn-Current-20140910 issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Hi The Doctor,
> lib/fdflag 1/8 12% 0 0 7
> lib/reallocarray 7/15 47% 0 0 5, 7-9, 11, 13, 15
I unfortunately do not manage to reproduce these errors on the NetBSD, FreeBSD
and OpenBSD servers that the GCC C Farm provides...
I would like to help but I currently cannot investigate more on these issues.
> util/innupgrade 12/13 92% 0 0 1-9, 11-13
> As a result the upgrade procedure choked.
Did you upgrade Perl yesterday?
It looks strange that you only get the innupgrade error today (the script has
not been recently changed).
Yet, I have just found out that the innupgrade test suite fails on AIX because
of:
"-T" is on the #! line, it must also be used on the command line at
../../scripts/innupgrade line 1.
This patch addresses the issue:
--- Makefile (r?vision 9683)
+++ Makefile (copie de travail)
@@ -112,15 +112,15 @@
echo '' ; \
cd $$D && $(MAKE) install || exit 1 ; cd .. ; \
done
- test -z "$D" && $(PATHBIN)/innupgrade $(PATHAUTHPASSWD)
- test -z "$D" && $(PATHBIN)/innupgrade $(PATHBIN)
- test -z "$D" && $(PATHBIN)/innupgrade $(PATHDOC)
- test -z "$D" && $(PATHBIN)/innupgrade $(PATHETC)
- test -z "$D" && $(PATHBIN)/innupgrade ${PATHFILTER}
- test -z "$D" && $(PATHBIN)/innupgrade $(MAN1)
- test -z "$D" && $(PATHBIN)/innupgrade $(MAN3)
- test -z "$D" && $(PATHBIN)/innupgrade $(MAN5)
- test -z "$D" && $(PATHBIN)/innupgrade $(MAN8)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(PATHAUTHPASSWD)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(PATHBIN)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(PATHDOC)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(PATHETC)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade ${PATHFILTER}
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(MAN1)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(MAN3)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(MAN5)
+ test -z "$D" && $(PERL) -T $(PATHBIN)/innupgrade $(MAN8)
install-root:
@chmod +x support/install-sh
Index: tests/util/innupgrade.t
===================================================================
--- tests/util/innupgrade.t (r?vision 9683)
+++ tests/util/innupgrade.t (copie de travail)
@@ -13,7 +13,7 @@
# Run innupgrade with the given arguments and expect it to succeed.
run () {
- $innupgrade "$@"
+ ${PERL} -T ${innupgrade} "$@"
if [ $? = 0 ] ; then
printcount "ok"
else
--
Julien ?LIE
? Obsequium amicos ueritas odium parit. ? (T?rence)
------------------------------
Message: 4
Date: Thu, 11 Sep 2014 10:31:21 +1000
From: Nick Edwards <[email protected]>
To: Russ Allbery <[email protected]>
Cc: [email protected]
Subject: Re: hide headers
Message-ID:
<CAMD-=v+sfio-ud5tleoyt+dzrwmwrr1etth7oq9u7mo4foh...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/11/14, Russ Allbery <[email protected]> wrote:
> Nick Edwards <[email protected]> writes:
>
>> We only have the localhost and custs auth/access's none others, but I
>> did fix the problem by stop / start, reload did not seem to do it?
>
>> Now the path is done the only thing remaining is the message-id being
>> remote still, not the news server, perhaps I'm on information
>> overload, and need to walk away till morning, but this one I cant find
>> any option to deal with.
>
> Right, the message ID can be provided by the client and it potentially
> seriously breaks the NNTP protocol for the server to override the client's
> choice of message ID. (The server doesn't know whether the client is
> offering the same message ID to multiple servers.)
>
> You can probably do something with a posting filter by editing the
> headers, but there isn't (and won't be) a built-in option for changing the
> message ID because it's a protocol violation and could result in duplicate
> messages (in scenarios that you probably aren't worried about).
OK, Thanks Russ, we know many servers do it (including inn based),
we've enabled that option since 2002 at least, but the great thing is
your filters understand perl so it'll be easy to take their LHS and
insert it to our @RHS :-)
I think that's the last remaining obstacle , will run it in for a few
more weeks to make sure, bound to be something I've missed heh.
------------------------------
Message: 5
Date: Wed, 10 Sep 2014 20:04:06 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Inn-Current-20140910 issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> Yet, I have just found out that the innupgrade test suite fails on AIX
> because of: "-T" is on the #! line, it must also be used on the command
> line at ../../scripts/innupgrade line 1.
This implies that the script, as installed, will also fail if the admin
just runs it as innupgrade, doesn't it?
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 6
Date: Wed, 10 Sep 2014 21:10:51 -0600
From: The Doctor <[email protected]>
To: Russ Allbery <[email protected]>
Cc: [email protected]
Subject: Re: Inn-Current-20140910 issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
On Wed, Sep 10, 2014 at 08:04:06PM -0700, Russ Allbery wrote:
> Julien ?LIE <[email protected]> writes:
>
> > Yet, I have just found out that the innupgrade test suite fails on AIX
> > because of: "-T" is on the #! line, it must also be used on the command
> > line at ../../scripts/innupgrade line 1.
>
> This implies that the script, as installed, will also fail if the admin
> just runs it as innupgrade, doesn't it?
>
100% correct.
> --
> Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
>
> Please send questions to the list rather than mailing me directly.
> <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
> _______________________________________________
> inn-workers mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/inn-workers
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
22 Sept 2014 New Brunswick save the province vote Liberal!
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 64, Issue 7
******************************************
