There is a bug when setting a new E-Line on a mask then if a user was match by antirandom module due connecting then E-Line doesn't allowing him to connect on the network as it should and client is getting "Registration Timeout" error, this applies with any action "shun,gzline,etc.."
*** E:Line added by westor (firstname.lastname@example.org) for mask *@220.127.116.11 and types 'GZQsq'
*** [antirandom] denied access to user with score 6: email@example.com:westor
*** Shun added for *@18.104.22.168 on Wed May 15 03:27:25 2019 GMT (from IRC.server.Net to expire at Wed May 15 04:27:25 2019 GMT: You're look like an IRC Bot.)
You know you can add exceptions for antirandom too right? =]
Other than that, I believe TKL exceptions are only checked on connect (so during the USER/NICK handshake) and antirandom comes just after that. So antirandom will set the shun without checking for TKL exceptions because you didn't tell that mod to exempt the host itself.
I did notice you filed a bug with Unreal so perhaps Syzop can shed some light on it as well. The registration timeout after a shun seems pretty weird too so it might just be a bug in the antirandom mod. I'll close the issue for now because I don't think there's anything I can really do from within the module, but you should still be able to comment on it in case Syzop says/does something to allow this module to do something about it. ;]
Closed because module no longer exists.