[IRCServices Coding] channel: MODE #channel -b *!*@host: ban not found

[Andrew Church]

     Fixed (the ban wasn't getting added to the internal list).

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/

>Services v 5.0a23
>
>Not sure exactly on the causes of this one yet, but logs indicate that 
>something is wrong so am reporting it in case it is something obvious while 
>I research further.
>
>Basically, whenever ChanServ sets +b*!user at host in a channel in response to 
>an autokick entry, the subsequent attempt to remove the ban from a channel 
>results in services logging:
>
>channel: MODE #channel -b *!*@host: ban not found
>
>The bans are usually removed automatically by channel bots to keep the 
>channel ban list manageable so I am assuing there is some discrepancy 
>between the original announcement by Chanserv of the ban it has set and the 
>actual ban it sets or Chanserv incorrectly parsing the /mode -b.  
>
>>From channel:
>DOS_BOT_77 (~username at ctcp-35163.cas-lon.golden.net) joined #channel.
>#channel: mode change '+b dos_bot*!*@*' by ChanServ!services at ctcp.net
>DOS_BOT_77 kicked from #channel by ChanServ: User has been banned from the 
>channel
>....
>(#channel) Channel ban on dos_bot*!*@* expired.
>#channel: mode change '-b dos_bot*!*@*' by Bot
>
>services.log:
>channel: MODE #channel -b dos_bot*!*@*: ban not found
>
>
>
>-- 
>Mark.
>CTCP Networks.
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices-coding