Hi! Benny,

In a message to Björn Felten you wrote:

 BP> why is jamnntpd using the boss node number for authed logings eg
 BP> points ?

Because the server does not know who is going to call in to it, prior to
getting a 'call'.

 BP> so basicly is it need to make each point there own groups ?, and then
 BP> set the point number pr group unshered by others :)

Nope.  Close, though an interesting thought.  But it's still not a complete
answer.  (I'm unsure of whether JamNNTPd would be able to differentiate between
multiple definitions for the same echoes, per each point's group.)

 BP> i would expect that authed users would override boss node number in
 BP> groups ?

It still won't work as JamNNTPd cannot stipulate multiple origins (lines).  It
is at the mercy of the particular tosser, which determines the origin.

You've raised an interesting notion indeed, Benny.  The idea would work with
multiple servers being configured for multiple inbound *ports*, each with their
own configuration files _and_ tosser.  I.e., one pair of JamNNTPd and tosser
configurations (and scripts) for each point.

That's a lot of work for a single sysop.  Is it not better to have each point
do the work for themselves!?!  :)

Cheers,
Paul.

... Bad command.  Bad, bad command!  Sit!  Stay!  Staaay...
--- Paul's Win98SE VirtualBox