Y:-line parsing change to allow class with 0 connects

[Helmut Springer <delta@xxxxxxxxxxxxxxxxxxxx>]

hi,

seeing the disussion about open servers and the problems they raise
I would like to use B:-lines to bounce clients from domains I don't
want to give complete open i/I:-lines to other servers.

for that I'd need a class with a client limit of '0', which is not
possibile at the moment because '0' is parsed as 'unlimited'.  since
admins imho don't need that 'unlimited' I'm asking to change that
to '0 means 0'.  checking against some limit might burn a little
more CPU than performing no check at all (which '0' does at the moment)
but I think that's no problem.

before someone tells me to use K:-lines or according i/I:-lines:  I
think the possibility to bounce users more or less transparently to
servers which take care for the domain they're coming from would
limit the number of 'needed' open servers.  the possibility to use
the unused field in the B:_line for a comment would be handy.  If
I could bounce every not explicit I:-lined client from *.com to some US 
server with a comment like "you're bounced to <server>, contact <me> if 
you need access to a *.de server" I could close down my open line for *.com.

that's not possible with i/I/K:-lines that user-friendly.  I can't K:-line
*.com to send a comment to rejected clients since I've *.com also inside
germany.  I can't send a comment what to do without any I:-line for *.com
and most users won't understand why they can't connect to a *.de-server
being in germany (don't tell me now not to care about DAUs, thanx).

regards
 delta

-- 
helmut springer                  Consulting: Unix, IP, Security, InfoServices
delta@xxxxxxxxxxxxxxxxxxxx                          Stuttgart University, FRG
http://home.pages.de/~delta/
phone : +49 711 685-2003           "Freedom's just another word for
FAX   : +49 711 685-7096            nothing left to lose"  Kris Kristofferson