#111809 - 19/02/05 08:04 AM
Long Server Notice - Unexpected Character ":"
|
Darvocet
newbie
Registered: 19/02/05
Posts: 5
Loc: United States
|
First off I would like to apologise in case this is already posted somewhere, but I felt that I should post it just in case.
I am running a small IRC network with ircservices and unrealircd.
When I issue a long global notice command through OperServ, the character ":" appears somewhere in the sentence.
Example:
[12:26am] -Global- [Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running :a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin.
As you can see the phrase "Opers running :a scan" is what mIRC sent through to services. Checking the debug log report for services, as well as telnet to the server to check commands, I have determined that this error only occurs when the command is sent from mIRC.
This only occurs through services, because if I were to just send the notice myself it would be cut off, and not even reach the point where mIRC added the :.
mIRC must be adding the character : to any notice that is over a certian length.
If you would like more detail please just let me know, I have lots of logs with debug, etc. in them.
Thanks,
Darvocet
_________________________
Darvocet
EpicIRC.Net - irc.epicirc.net
|
|
Top
|
|
|
|
#111810 - 19/02/05 08:53 AM
Re: Long Server Notice - Unexpected Character ":"
|
Skip
enthusiast
Registered: 09/12/02
Posts: 361
Loc: Darwin, Australia
|
Exactly how are you sending the message to the services? If you could paste the exact line being sent from mIRC (with /debug -p @debug) it may help someone track this down.
Hope that helps
|
|
Top
|
|
|
|
#111811 - 19/02/05 07:07 PM
Re: Long Server Notice - Unexpected Character ":"
|
Darvocet
newbie
Registered: 19/02/05
Posts: 5
Loc: United States
|
Certianly. Here is some more info. I am running the notice from an alias. I will paste here:
alias xdccwarn { .operserv global [Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin. }
Here is how it looks through debug:
-> mountie.ns.ca.epicirc.net OPERSERV global [Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running :a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin.
<- :Global!services@epicirc.net NOTICE $* :[Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running :a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin.
Receive Notice in RAW Telnet session:
Global!services@epicirc.net NOTICE $* :[Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running :a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin.
I also have debug logs for ircservices, however they just show the ":" placed in there so it is not very helpful. From BitchX sending the notice worked fine, without the ":" appearing. I have also noticed this same bug happens on Network Connect Notices, Channel Join Notices, anything that services or servers send out, and only when kinda long. Again, if it wasn't sent through services or a server, then the ircd server or mIRC, i'm not sure which does seem to crop the notice for being too long. However, being sent through to services it is able to be sent out.
UnrealIRCd v3.2.2b (not related)
IRCServices 5.0.41 (determined NOT a ircservices bug)
mIRC 6.16
WinXP
Thanks again!
Darvocet/XanaX
Edited by Darvocet (19/02/05 07:19 PM)
_________________________
Darvocet
EpicIRC.Net - irc.epicirc.net
|
|
Top
|
|
|
|
#111812 - 19/02/05 08:06 PM
Re: Long Server Notice - Unexpected Character ":"
|
Danthemandoo
addict
Registered: 04/03/04
Posts: 491
Loc: Behind you
|
confirmed here on 6.16.
The " : " is in exactly the same place as shown above.
It however only seems to do it when you msg something using the IRCd's alias. Eg: /operserv /chanserv etc but not when messaging a with the normal /msg.
Edited by Danthemandoo (19/02/05 08:44 PM)
|
|
Top
|
|
|
|
#111813 - 19/02/05 08:54 PM
Re: Long Server Notice - Unexpected Character ":"
|
Darvocet
newbie
Registered: 19/02/05
Posts: 5
Loc: United States
|
I can confirm that.
Testing using /msg OperServ the message works fine. However using the alias /OperServ it puts the colon in.
_________________________
Darvocet
EpicIRC.Net - irc.epicirc.net
|
|
Top
|
|
|
|
#111814 - 20/02/05 02:06 AM
Re: Long Server Notice - Unexpected Character ":"
|
Skip
enthusiast
Registered: 09/12/02
Posts: 361
Loc: Darwin, Australia
|
I would *guess* this is mIRC acting like an ircd for some reason. If you change your global to just 1 2 3 4 .. etc. does the : appear at the same Nth word or at the same Nth byte?
The : is used to indicate the last parameter, where everything else is seperated by a space, if a : is given this instructs the ircd to put all remaining data into one parameter, this is how /raw PRIVMSG <nick> :a b c works but /raw PRIVMSG <nick> a b c will only display 'a' on most ircds (because they only treat the 3rd parameter as the message contents, not the 3rd 4th 5th Nth..).
mIRC knows where to place the : for some messages (privmsg/notice obviously, but it also seems to like globops and wallops too). It looks like it has a hardcoded maximum for other commands. Perhaps this is an old feature that should be removed.
In the meantime you might have more luck changing your alias to do .operserv global :rest of message, though this may make unrealircd include an additional : when it creates the PRIVMSG from your alias.
(add: confirmed it places on the same token/word with /1 2 [Network Notice] Our network has been experiencing a major increase of unattended bots connecting. We are taking many defensive actions to make sure that they do not interrupt the normal activity of the network. If you receive a CTCP LAG, please ignore it, as it is our Opers running a scan to detect malicious bots. If you have any questions, please join #Help and speak to an Oper. - XanaX, Sr. Network Admin.)
|
|
Top
|
|
|
|
#111816 - 20/02/05 05:19 AM
Re: Long Server Notice - Unexpected Character ":"
|
Skip
enthusiast
Registered: 09/12/02
Posts: 361
Loc: Darwin, Australia
|
Sorry if my post caused any confusion...
I was just trying to explain why I think the bug occurs. If you have at this section of the IRC RFC you will see how ":" is used as the 'last' parameter (so it can include spaces).
/debug -p @debug /privmsg nick 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
mIRC knows where to place the last parameter in some commands (namely PRIVMSG and NOTICE), which is why there is no problem when you /msg the command thru to your services.
/silly command 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
For commands where mIRC does not know where to place the :, it will insert it after the 50th token not counting the command itself (maybe to reduce load on the ircd that processes it). You can get around this by using /raw:
/raw silly command 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
You can also see how unreal will handle you putting the : in the alias yourself (probably as operserv global :rest of message or operserv :global rest of messasge).
Anyhow, I *do* think this is a bug, even though mIRC has probably been deliberately coded to do this. Hopefully the behaviour will change, but in the meantime, use /raw operserv or experiment with ':' to work around the problem.
|
|
Top
|
|
|
|
#111817 - 20/02/05 05:36 AM
Re: Long Server Notice - Unexpected Character ":"
|
Darvocet
newbie
Registered: 19/02/05
Posts: 5
Loc: United States
|
I will and I appreaicate everyones help very much!!!
Thanks again.
_________________________
Darvocet
EpicIRC.Net - irc.epicirc.net
|
|
Top
|
|
|
|
Moderator: d00dman, Hammer, Karen, Krejt, Mentality, Merlin, MIMP, ParaBrat, qwerty
|
|