I run a channel and i need a script that work this way. I have Two Linked eggdrops and I want them to work this way.
Bot2 stays without Op. Any messages sent to the bot i.e.: *go*#* *http* *server* etc... this egg sends a Notice or Privmsg to bot1 who has Op status, and this one bans the Ip of the Spammer and send a onotice containing a message like: Baning Nick / Ip cause of SPAM detected by Egg2.
bot2 cycles the channel each 10 minutes, checking for automsgs containing the same strings above (*go*#* ...) if he receives any, the same thing happens.
I've seen this done by two scripts, that works in egg 1.4, but not in 1.6.6. They're line server-antispam.tcl (Op) and client-antispam.tcl (egg without Op).
i'd be grateful if someone could help me, please. PPslim can u help me with that?
<font size=-1>[ This Message was edited by: hmelo on 2001-12-10 13:33 ]</font>
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
TCL Request
Yes, I have just the solution for you. Fresh out of the bag, with bug fixes galor *G*
Try No!Spam.tcl (by Wreck and PPSlim) *COUGH*ADVERT*COUGH*
It is available from http://sourceforge.net/projects/no-spam/
I recomend using the beta version, as it is as about as stable as it will get for the next 2 weeks.
1.7.2 is just around the corner, which is the beta version with 2 extra tweaks (so far).
The only thing it does not do, is send a onotice. This support is not likely to be added, as kick (and ban) reasons, will be suficient to determine the reason for the kick.
Try No!Spam.tcl (by Wreck and PPSlim) *COUGH*ADVERT*COUGH*
It is available from http://sourceforge.net/projects/no-spam/
I recomend using the beta version, as it is as about as stable as it will get for the next 2 weeks.
1.7.2 is just around the corner, which is the beta version with 2 extra tweaks (so far).
The only thing it does not do, is send a onotice. This support is not likely to be added, as kick (and ban) reasons, will be suficient to determine the reason for the kick.
-
hhmelo
ppslim this is a very good tcl...
but i'm having these 2 little problems:
1) When the hub bot cycle the channel, he receives a Notice from ChanServ like this "Welcome to #Channel ..." and the leaf bot bans *!*@services.blahblah"
i've add a user Services with the hostmask he bans, with o|o but he doesn't stop baning Chanserv hehe
2) i've tried many options of the ban types list, but the leaf bot only bans *!user@host.domain. I'm trying mking he ban only *!*@host.domain, that is supposed to be option 2.
do u have any idea of what can i do??
but i'm having these 2 little problems:
1) When the hub bot cycle the channel, he receives a Notice from ChanServ like this "Welcome to #Channel ..." and the leaf bot bans *!*@services.blahblah"
i've add a user Services with the hostmask he bans, with o|o but he doesn't stop baning Chanserv hehe
2) i've tried many options of the ban types list, but the leaf bot only bans *!user@host.domain. I'm trying mking he ban only *!*@host.domain, that is supposed to be option 2.
do u have any idea of what can i do??
-
hhmelo
I have looked into this issue, and see no problems.
the spam-ignore-opped setting, is to ignore any1 that has OP status on the channel. They do not need to added to the bot, only to have had a +o mode issued to the server, for there nickname (or as some like, have a @ next tot here nick).
The spam-ignore-flag is to ignore users that have this flag, as a global flag, not a channel flag. They must also have a hostmask that the bot is able to identify them by.
This is probably the largest flaw in No!Spam. The inability to ignore by channel flag, even though I advise only to use channel flags. I will post an update to the download page within 2 hours.
the spam-ignore-opped setting, is to ignore any1 that has OP status on the channel. They do not need to added to the bot, only to have had a +o mode issued to the server, for there nickname (or as some like, have a @ next tot here nick).
The spam-ignore-flag is to ignore users that have this flag, as a global flag, not a channel flag. They must also have a hostmask that the bot is able to identify them by.
This is probably the largest flaw in No!Spam. The inability to ignore by channel flag, even though I advise only to use channel flags. I will post an update to the download page within 2 hours.
-
hhmelo
tks :razz:P
the tcl is great !!!
by the way... i couldn't get the no.spam.leaf.tcl from the 1.7.2 session, the link was dead. I'm using fron the 1.7.1 zip file. I think there are no changes but... warning doesn't hurt...
tks ppslim....
i'm waiting for the update
[]s
<font size=-1>[ This Message was edited by: hmelo on 2001-12-11 13:51 ]</font>
the tcl is great !!!
by the way... i couldn't get the no.spam.leaf.tcl from the 1.7.2 session, the link was dead. I'm using fron the 1.7.1 zip file. I think there are no changes but... warning doesn't hurt...
tks ppslim....
i'm waiting for the update
[]s
<font size=-1>[ This Message was edited by: hmelo on 2001-12-11 13:51 ]</font>
It is strongly advised against using the leaf.tcl from the 1.7.1 zip. I had originaly posted the beta version, because of issues arising when another tester used a previous version.
I will check and make sure the file is added correctly when updating the beta copies.
You actualy spotted a larger flaw than first thought.
If a user that is not on the channel, but has a user record with a ignored flag, spammed the bot via notice, private message, dcc send, invite (I think thats them all:P). They would not be ignored. (This would mean chanserv would not be ignored) This was due to eggdrops user detection, only having the ability to match users by nickname, if they are on the channel. I have changed this so, it matches users by mask, unless a handle is directly passed.
This should fix chanserv ralted issues.
I will check and make sure the file is added correctly when updating the beta copies.
You actualy spotted a larger flaw than first thought.
If a user that is not on the channel, but has a user record with a ignored flag, spammed the bot via notice, private message, dcc send, invite (I think thats them all:P). They would not be ignored. (This would mean chanserv would not be ignored) This was due to eggdrops user detection, only having the ability to match users by nickname, if they are on the channel. I have changed this so, it matches users by mask, unless a handle is directly passed.
This should fix chanserv ralted issues.
-
hhmelo
If you could, can you make a test on the ignore system.
1 method, would be to remove the +f flag from the user you added for chanserv. Wait till chanserv does it's bit of spamming, and hope it bans. Please report back with the results. As without this information, it can't be launched as a full release.
1 method, would be to remove the +f flag from the user you added for chanserv. Wait till chanserv does it's bit of spamming, and hope it bans. Please report back with the results. As without this information, it can't be launched as a full release.
-
hhmelo
I tested this way...
There is no user ChanServ
the hub cycled and the leaf banned the Chanserv's host when the notice/spam was received..
this is the way the tcl is configured
set spam-ignore-flag "f"
set spam-ignore-cflag ""
set spam-ignore-opped 1
set spam-ignore-voiced 0
set spam-dcc-flag m
i don't know if it is exactly what u asked...
so i tested with a user Chanserv with no flags. the same thing happened, only +f spammers are ignored.
i think that is exactly how it is supposed to be, isn't it??
ban spam notices even from users that are not in channel....
When i ask to a channel op, that is not in the user file, send a spam to the hub, he's banned. it's fine to me, but as i understand in the tcl it's not suposed to happen
[]s
<font size=-1>[ This Message was edited by: hmelo on 2001-12-11 16:40 ]</font>
There is no user ChanServ
the hub cycled and the leaf banned the Chanserv's host when the notice/spam was received..
this is the way the tcl is configured
set spam-ignore-flag "f"
set spam-ignore-cflag ""
set spam-ignore-opped 1
set spam-ignore-voiced 0
set spam-dcc-flag m
i don't know if it is exactly what u asked...
so i tested with a user Chanserv with no flags. the same thing happened, only +f spammers are ignored.
i think that is exactly how it is supposed to be, isn't it??
ban spam notices even from users that are not in channel....When i ask to a channel op, that is not in the user file, send a spam to the hub, he's banned. it's fine to me, but as i understand in the tcl it's not suposed to happen
[]s
<font size=-1>[ This Message was edited by: hmelo on 2001-12-11 16:40 ]</font>
Yes and no.
I gather your are refering to the spam-ignore-opped setting?
If so, then yes, your understanding is correct, but only when it comes to channel messages and notices.
A private message is not destined for a channel. You can't be oped in a private message. Therefor, the spam-ignore-opped is not applied to this type of spam (nor is spam-ignore-voice). Only global flag based ignoring can take place.
I gather your are refering to the spam-ignore-opped setting?
If so, then yes, your understanding is correct, but only when it comes to channel messages and notices.
A private message is not destined for a channel. You can't be oped in a private message. Therefor, the spam-ignore-opped is not applied to this type of spam (nor is spam-ignore-voice). Only global flag based ignoring can take place.