FW: [IRCServices] Notice Bug (Update)

[EpicIRC Administration]

I have posted regarding this bug on the mIRC Bug Forums.  They have verified
that it is infact happening.  We have found a 'semi' solution to the problem
though, that may would be good for your to add on the faq.
 
If I send the notice " /OperServ Global <really long noitce>"  That is when
the ":" (colon) will appear.
 
HOWEVER, if I were to do "/msg OperServ Global <really long notice>"  The
colon does not appear.
 
So... it seems that when mIRC is pulling the alias for /operserv or
/chanserv it somehow creates this error.  For anyone else out there that may
ever have this problem, until it is fixed just use /msg operserv to get
around it.  
 
Darvocet
EpicIRC.Net - irc.epicirc.net
 


  _____  

Hello... I have noticed a little error, and I just wanted to post here to
see if anyone had already posted regarding it, or if it was the first time.
 
I run an IRC Network with Unreal3.2.2b and ircservices-5.0.41
 
When I send a global notice that is fairly long it appears that the
character ":" shows up in the notice.  If I were to just sent a global
notice as an oper, Unreal would cut the message off before the ":" would
appear, so this only occurs with services.
 
I have noticed it in Channel Join Notices, Network Connect Notices, and
Global Notices.  Below is an example:
 
-------------------------- Sending the notice with OperServ global
-------------------------
 
[11:30pm] -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.
 
------------------------ Sending the same notice as an oper, and not with
services -----------------------
 
[11:32pm] -XanaX- [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 spe
....
....
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: ../attachments/20050220/d96e2975/attachment.htm