2.3. Meanings of server notice masks

2.3.1. +b, bot warnings

Opers with the +b snomask set will receive warning messages from the server when potential flooders and spambots are detected.

2.3.2. +c, client connections

Opers who have the +c snomask set will receive server notices when clients attach to the local server.

2.3.3. +C, extended client connection notices

Opers who have the +C snomask set will receive server notices when clients attach to the local server. Unlike the +c snomask, the information is displayed in a format intended to be parsed by scripts, and includes the two unused fields of the USER command.

2.3.4. +d, debug

The +d snomask provides opers extra information which may be of interest to debuggers. It will also cause the user to receive server notices if certain assertions fail inside the server. Its precise meaning is variable. Do not depend on the effects of this snomask as they can and will change without notice in later revisions.

2.3.5. +f, full warning

Opers with the +f snomask set will receive notices when a user connection is denied because a connection limit is exceeded (one of the limits in a class{} block, or the total per-server limit settable with /quote set max).

2.3.6. +F, far client connection notices

Note: This snomask is only available if the sno_farconnect.so extension is loaded.

Opers with +F receive server notices when clients connect or disconnect on other servers. The notices have the same format as those from the +c snomask, except that the class is ? and the source server of the notice is the server the user is/was on.

No notices are generated for netsplits and netjoins. Hence, these notices cannot be used to keep track of all clients on the network.

There is no far equivalent of the +C snomask.

2.3.7. +k, server kill notices

Opers with the +k snomask set will receive server notices when services kill users and when other servers kill and save (forced nick change to UID) users. Kills and saves by this server are on +d or +s.

2.3.8. +n, nick change notices

An oper with +n set will receive a server notice every time a local user changes their nick, giving the old and new nicks. This is mostly useful for bots that track all users on a single server.

2.3.9. +r, notices on name rejections

Opers with this snomask set will receive a server notice when somebody tries to use an invalid username, or if a dumb HTTP proxy tries to connect.

2.3.10. +s, generic server notices

This snomask allows an oper to receive generic server notices. This includes kills from opers (except services).

2.3.11. +u, unauthorized connections

This snomask allows an oper to see when users try to connect who do not have an available auth{} block.

2.3.12. +W, whois notifications

Note: This snomask is only available if the sno_whois.so extension is loaded.

Opers with +W receive notices when a WHOIS is executed on them on their server (showing idle time).

2.3.13. +x, extra routing notices

Opers who have the +x snomask set will get notices about servers connecting and disconnecting on the whole network. This includes all servers connected behind the affected link. This can get rather noisy but is useful for keeping track of all linked servers.

2.3.14. +y, spy

Opers with +y receive notices when users try to join RESV'ed ("juped") channels. Additionally, if certain extension modules are loaded, they will receive notices when special commands are used.

2.3.15. +Z, operspy notices

Opers with +Z receive notices whenever an oper anywhere on the network uses operspy.

This snomask can be configured to be only effective for admins.