Forums Bug Reports Dedicated Message window does not trigger ON OPEN

I have enabled "Use single message window" under mIRC IRC Options.

The following code works on normal message windows, but will not work on a dedicated window open:

on ^*:OPEN:?:*:{
if ((http:// isin $1-) || (www. isin $1-) || ($chr(35) isin $1-) || ($chr(3) isin $1-) || ($!decode isin $1-)) {
msg $nick [spamfilter] your message has been considered as spam and window was closed.
halt
}
}


BTW, its maybe time to add an anti-spam filter in mirc, since QuakeNet is flooding over by spammers that message you with:

All off game cheats, patchs , consoles , weekly updated online server list here => http://blah

Hot movies,Hot teens, Pam , Jennifer and more then stars , All of free and 4 u ==> http://blah

Wold class free porn all off for u => http://blah


I think I've gotten like 40 messages like this the past week. Always from new nicks. I know I could ignore them, but I wanted this antispam filter to work.

This is something that I wondered about a long time ago myself (the dedicated query window) and basically it's like this:

It's not a bug cause the query window does not have a name attached to it

Change it to NOT be a dedicated query window and try it out without changing the code at all and you'll see it should work (Im ignoring if the code is right or wrong atm)

Believe it or not, but I use Dedicated Message window for a reason. And this reason is not for spam, but because I usually get questions and similar from many many nicks, since I am an operator on one of the top chans on QuakeNet.

Thus a query window for each nick would infact cause a big problem.

I would still encourage khaled to enable on open for this
'Messages' window.

The easiest way to solve this would be to have an $identifyer return who messaged you in the DQW (dedicated query window) and be able to parse it out (the text). I dont blame you your reason, just saying the troubles I had with it in the past. One way you could do this (until/if this gets taken care of) is to output it (possibly) to a @window and filter it BEFORE it gets there and still maintain the indiviual window option. Would that work in the mean time?