i think there should be a trigger to suspend and/or remove a user who
uses the ban *!*@* thru X for 1 day, then increase to 2 days , then 3
for repeated usage by that user, per *!*@* ban if a useradd uses this
command within 7 days of being added to X.
This will then stop being a easy way to clea
Hi Coders,
Having searched just about everywhere else, in search of the answer to this question
I'm searching here. What was (in the past) the use of the R: ?
Please just posts answers to the mailing list, I'm already subscribed.
Regards,
Oliver "Ozzy" Keenan.
Official QuakeNET Helper
> Having searched just about everywhere else, in search of the answer to
this question I'm searching here. What was (in the past) the use of the R: ?
R: lines enabled admins to establish different policies
about users connecting, rather than the simple
authorization methods allowed by I: and K:
>>Hidden:
> Easy to remove the *!*@* ban OUTsider,
> In my case, I could: /msg X unban #chan Hidden
> X will then check wich bans are matching me and will remove *!*@* and
other
> bans matching me if there are any, but X will not remove ALL bans as if
you
> were doing /msg X unban #chan *!*@*
I a
Whatever the use of the command, the user MUST be 100+ user in the
channel to use it, so it's the responsibility of the 400+ users to
manage the userlist. Why would we deal with all kind of channel abuse by
chanops on X? the 400+ just have to suspend/remove the access of the
abuser and that's all.
OUTsider,
/msg X unban #chan Hidden was suppose to remove only the bans matching the
nick Hidden (*!*@*) but it didnt.
Coders, There is a bug here.
[18:01] -> *[EMAIL PROTECTED]* ban #test-chan *!*[EMAIL PROTECTED]
[18:01] -X- Added ban *!*[EMAIL PROTECTED] to #test-chan at level 75
[18:01] -> *
Your mail to 'Bugs' with the subject
Eggheads Development Team
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message body is too big: 130183 bytes but there's a limit of 40 KB
Either the message will get posted to the list, or you will
I would guess that the *!*@* ban overwrote the other 2 bans, since the other
2 bans were covered by the *!*@*, and therefore they were probably deleted
in favor of the *!*@* ban. Therefore, the only ban left in the channel
would be the 1 *!*@* ban, and therefore only 1 ban would be removed. :-)
You'll have to excuse my feeble mind on this one:
> Thats indeed a bug, and when it'll be fixed, I think the unban issue with
> *!*@* can be forgotten. That cmd SHOULD remove only bans matching
> [EMAIL PROTECTED] (*!*@*) and not the 2 others (*!*[EMAIL PROTECTED] and
> the other)
When setting t
All this talk about X ... Does that belong on this list?
In order to preserve synchronization it is necessary for
the servers to remove all bans that are overlapped
by a new ban that is set. That means that when someone
(including when that someone is X) sets a ban *!*@*
then ALL bans are remove
Well, it's not actually a bug since X will automaticly remove bans that
are covered by more restrictive bans. Example:
I ban *!*[EMAIL PROTECTED] *!*[EMAIL PROTECTED]
And after that I set ban *!*@*, *!*@* implies that *!*[EMAIL PROTECTED]
and *!*[EMAIL PROTECTED] are banned, so X removes thease ba
11 matches
Mail list logo