1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Notice Bug (Update)
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20Notice%20Bug%20%28Update%29&In-Reply-To=200502201734.j1KHXpur136694%40pimout2-ext.prodigy.net">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"004849.html">
11 <LINK REL=
"Next" HREF=
"004851.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Notice Bug (Update)
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20Notice%20Bug%20%28Update%29&In-Reply-To=200502201734.j1KHXpur136694%40pimout2-ext.prodigy.net"
17 TITLE=
"[IRCServices] Notice Bug (Update)">Craig at frostycoolslug.com
19 <I>Sun Feb
20 10:
32:
12 PST
2005</I>
21 <LI>Previous message:
<A HREF=
"004849.html">FW: [IRCServices] Notice Bug (Update)
23 <LI>Next message:
<A HREF=
"004851.html">FW: [IRCServices] Notice Bug (Update)
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4850">[ date ]
</a>
27 <a href=
"thread.html#4850">[ thread ]
</a>
28 <a href=
"subject.html#4850">[ subject ]
</a>
29 <a href=
"author.html#4850">[ author ]
</a>
34 <PRE>Straying off topic slightly..
36 If your looking for a 'Quick fix' to this problem, add the following to
43 The /operserv will be sent to the services correctly, without the :
45 /****************************************
46 * Craig
"FrostyCoolSlug
" McLure
47 *
<A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">Craig at FrostyCoolSlug.com
</A>
48 * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A>
49 * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
50 ****************************************/
52 EpicIRC Administration wrote:
53 ><i> I have posted regarding this bug on the mIRC Bug Forums. They have verified
54 </I>><i> that it is infact happening. We have found a 'semi' solution to the problem
55 </I>><i> though, that may would be good for your to add on the faq.
57 </I>><i> If I send the notice
" /OperServ Global
<really long noitce
>" That is when
58 </I>><i> the
":
" (colon) will appear.
60 </I>><i> HOWEVER, if I were to do
"/msg OperServ Global
<really long notice
>" The
61 </I>><i> colon does not appear.
63 </I>><i> So... it seems that when mIRC is pulling the alias for /operserv or
64 </I>><i> /chanserv it somehow creates this error. For anyone else out there that may
65 </I>><i> ever have this problem, until it is fixed just use /msg operserv to get
66 </I>><i> around it.
69 </I>><i> EpicIRC.Net - irc.epicirc.net
75 </I>><i> Hello... I have noticed a little error, and I just wanted to post here to
76 </I>><i> see if anyone had already posted regarding it, or if it was the first time.
78 </I>><i> I run an IRC Network with Unreal3.2
.2b and ircservices-
5.0.41
80 </I>><i> When I send a global notice that is fairly long it appears that the
81 </I>><i> character
":
" shows up in the notice. If I were to just sent a global
82 </I>><i> notice as an oper, Unreal would cut the message off before the
":
" would
83 </I>><i> appear, so this only occurs with services.
85 </I>><i> I have noticed it in Channel Join Notices, Network Connect Notices, and
86 </I>><i> Global Notices. Below is an example:
88 </I>><i> -------------------------- Sending the notice with OperServ global
89 </I>><i> -------------------------
91 </I>><i> [
11:
30pm] -Global- [Network Notice] Our network has been experiencing a
92 </I>><i> major increase of unattended bots connecting. We are taking many defensive
93 </I>><i> actions to make sure that they do not interrupt the normal activity of the
94 </I>><i> network. If you receive a CTCP LAG, please ignore it, as it is our Opers
95 </I>><i> running :a scan to detect malicious bots. If you have any questions, please
96 </I>><i> join #Help and speak to an Oper. - XanaX, Sr. Network Admin.
98 </I>><i> ------------------------ Sending the same notice as an oper, and not with
99 </I>><i> services -----------------------
101 </I>><i> [
11:
32pm] -XanaX- [Network Notice] Our network has been experiencing a major
102 </I>><i> increase of unattended bots connecting. We are taking many defensive actions
103 </I>><i> to make sure that they do not interrupt the normal activity of the network.
104 </I>><i> If you receive a CTCP LAG, please ignore it, as it is our Opers running a
105 </I>><i> scan to detect malicious bots. If you have any questions, please join #Help
113 </I>><i> ------------------------------------------------------------------------
115 </I>><i> ------------------------------------------------------------------
116 </I>><i> To unsubscribe or change your subscription options, visit:
117 </I>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
125 <LI>Previous message:
<A HREF=
"004849.html">FW: [IRCServices] Notice Bug (Update)
127 <LI>Next message:
<A HREF=
"004851.html">FW: [IRCServices] Notice Bug (Update)
129 <LI> <B>Messages sorted by:
</B>
130 <a href=
"date.html#4850">[ date ]
</a>
131 <a href=
"thread.html#4850">[ thread ]
</a>
132 <a href=
"subject.html#4850">[ subject ]
</a>
133 <a href=
"author.html#4850">[ author ]
</a>