When echo-message is enabled and a message is sent to an unloaded or unknown module, an echoed message is returned alongside an error, as seen in the following:
C: CAP REQ echo-message
S: :irc.znc.in CAP Guest47551 ACK :echo-message
C: PRIVMSG *x hi
S: :Guest47551!~kyle@x PRIVMSG *x hi
S: :*status!znc@znc.in PRIVMSG Guest47551 :No such module x
Is this expected? Perhaps no such nick response would be better suited.
S: :irc.znc.in 401 Guest47551 *x :No such module
When `echo-message` is enabled and a message is sent to an unloaded or unknown module, an echoed message is returned alongside an error, as seen in the following:
```
C: CAP REQ echo-message
S: :irc.znc.in CAP Guest47551 ACK :echo-message
C: PRIVMSG *x hi
S: :Guest47551!~kyle@x PRIVMSG *x hi
S: :*status!znc@znc.in PRIVMSG Guest47551 :No such module x
```
Is this expected? Perhaps no such nick response would be better suited.
```
S: :irc.znc.in 401 Guest47551 *x :No such module
```
<!-- github-sync-id:661290214 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When
echo-messageis enabled and a message is sent to an unloaded or unknown module, an echoed message is returned alongside an error, as seen in the following:Is this expected? Perhaps no such nick response would be better suited.