View Issue Details

IDProjectCategoryView StatusLast Update
0005501unrealircdpublic2020-01-02 15:48
Reporterwestor Assigned Tosyzop  
Status resolvedResolutionfixed 
Product Version5.0.0 
Fixed in Version5.0.1 
Summary0005501: Blacklist module doesn't allow clients to connect if warn action set

I noticed that when i set in unrealircd.conf into a blacklist block a warn action , then when the client is trying to connect, the warn action is acting like action kill upon the client
but it sending the server notice.


[Blacklist] IP matches blacklist justspamrbl (


blacklist justspamrbl {
        dns {
                type record;
                reply { 2; };
        action warn;
        ban-time 1h;
        reason "Possible IRC Proxy/Drone/TOR detected via JustSpam RBL service, Check$ip for details, if this action was incorrect then email us on including that message.";

User report:

Closing Link: [] (Possible IRC Proxy/Drone/TOR detected via JustSpam RBL service, Check for details, if this action was incorrect then email us on including that message.)
TagsNo tags attached.
3rd party modules


related to 0005276 resolvedsyzop UnrealIRCD blacklist + antirandom modules doesn't let the user connect in if ban-action is warn,shun,tempshun,kill 



2020-01-02 15:48

administrator   ~0021189

This bug uncovered some other bugs as well. Thanks for the report, fixed for 5.0.1:

commit d7d673faf2e38eeac915d369c7748686fdb23af2
Author: Bram Matthys <>
Date: Thu Jan 2 14:25:28 2020 +0100

    Multiple fixes related to ban actions:
    1) Fix issue if HOOKTYPE_IS_HANDSHAKE_FINISHED rejects the user
    2) Fix authprompt issue. We now allow adding the TKL in
       place_ban_host() for soft-kline/etc. Previously all the
       soft-kline/gline/zline/gzline acted like soft-kill.
    3) The blacklist module did not allow clients in with action 'warn',
       reported by westor in

Issue History

Date Modified Username Field Change
2019-12-18 21:44 westor New Issue
2019-12-30 17:45 syzop Relationship added related to 0005276
2020-01-02 13:22 syzop Assigned To => syzop
2020-01-02 13:22 syzop Status new => assigned
2020-01-02 13:22 syzop Priority urgent => normal
2020-01-02 15:48 syzop Status assigned => resolved
2020-01-02 15:48 syzop Resolution open => fixed
2020-01-02 15:48 syzop Fixed in Version => 5.0.1
2020-01-02 15:48 syzop Note Added: 0021189