HTML layout by Tatu J. Lund Apr 1997
Network Working Group
Request for Comments: 1459
The following is a list of numeric replies which are generated in
response to the commands given above. Each numeric is given with its
number, name and reply string.
6.1 Error Replies.
"<nickname> :No such nick/channel"
- Used to indicate the nickname parameter supplied to a
command is currently unused.
"<server name> :No such server"
- Used to indicate the server name given currently
"<channel name> :No such channel"
- Used to indicate the given channel name is invalid.
"<channel name> :Cannot send to channel"
- Sent to a user who is either (a) not on a channel
which is mode +n or (b) not a chanop (or mode +v) on
a channel which has mode +m set and is trying to send
a PRIVMSG message to that channel.
"<channel name> :You have joined too many channels"
- Sent to a user when they have joined the maximum
number of allowed channels and they try to join
"<nickname> :There was no such nickname"
- Returned by WHOWAS to indicate there is no history
information for that nickname.
"<target> :Duplicate recipients. No message delivered"
- Returned to a client which is attempting to send
PRIVMSG/NOTICE using the user@host destination format
and for a user@host which has several occurrences.
":No origin specified"
- PING or PONG message missing the originator parameter
which is required since these commands must work
without valid prefixes.
":No recipient given (<command>)"
":No text to send"
"<mask> :No toplevel domain specified"
"<mask> :Wildcard in toplevel domain"
- 412 - 414 are returned by PRIVMSG to indicate that
the message wasn't delivered for some reason.
ERR_NOTOPLEVEL and ERR_WILDTOPLEVEL are errors that
are returned when an invalid use of
"PRIVMSG $<server>" or "PRIVMSG #<host>" is attempted.
"<command> :Unknown command"
- Returned to a registered client to indicate that the
command sent is unknown by the server.
":MOTD File is missing"
- Server's MOTD file could not be opened by the server.
"<server> :No administrative info available"
- Returned by a server in response to an ADMIN message
when there is an error in finding the appropriate
":File error doing <file op> on <file>"
- Generic error message used to report a failed file
operation during the processing of a message.
":No nickname given"
- Returned when a nickname parameter expected for a
command and isn't found.
"<nick> :Erroneus nickname"
- Returned after receiving a NICK message which contains
characters which do not fall in the defined set. See
section x.x.x for details on valid nicknames.
"<nick> :Nickname is already in use"
- Returned when a NICK message is processed that results
in an attempt to change to a currently existing
"<nick> :Nickname collision KILL"
- Returned by a server to a client when it detects a
nickname collision (registered of a NICK that
already exists by another server).
"<nick> <channel> :They aren't on that channel"
- Returned by the server to indicate that the target
user of the command is not on the given channel.
"<channel> :You're not on that channel"
- Returned by the server whenever a client tries to
perform a channel effecting command for which the
client isn't a member.
"<user> <channel> :is already on channel"
- Returned when a client tries to invite a user to a
channel they are already on.
"<user> :User not logged in"
- Returned by the summon after a SUMMON command for a
user was unable to be performed since they were not
":SUMMON has been disabled"
- Returned as a response to the SUMMON command. Must be
returned by any server which does not implement it.
":USERS has been disabled"
- Returned as a response to the USERS command. Must be
returned by any server which does not implement it.
":You have not registered"
- Returned by the server to indicate that the client
must be registered before the server will allow it
to be parsed in detail.
"<command> :Not enough parameters"
- Returned by the server by numerous commands to
indicate to the client that it didn't supply enough
":You may not reregister"
- Returned by the server to any link which tries to
change part of the registered details (such as
password or user details from second USER message).
":Your host isn't among the privileged"
- Returned to a client which attempts to register with
a server which does not been setup to allow
connections from the host the attempted connection
- Returned to indicate a failed attempt at registering
a connection for which a password was required and
was either not given or incorrect.
":You are banned from this server"
- Returned after an attempt to connect and register
yourself with a server which has been setup to
explicitly deny connections to you.
"<channel> :Channel key already set"
"<channel> :Cannot join channel (+l)"
"<char> :is unknown mode char to me"
"<channel> :Cannot join channel (+i)"
"<channel> :Cannot join channel (+b)"
"<channel> :Cannot join channel (+k)"
":Permission Denied- You're not an IRC operator"
- Any command requiring operator privileges to operate
must return this error to indicate the attempt was
"<channel> :You're not channel operator"
- Any command requiring 'chanop' privileges (such as
MODE messages) must return this error if the client
making the attempt is not a chanop on the specified
":You cant kill a server!"
- Any attempts to use the KILL command on a server
are to be refused and this error returned directly
to the client.
":No O-lines for your host"
- If a client sends an OPER message and the server has
not been configured to allow connections from the
client's host as an operator, this error must be
":Unknown MODE flag"
- Returned by the server to indicate that a MODE
message was sent with a nickname parameter and that
the a mode flag sent was not recognized.
":Cant change mode for other users"
- Error sent to any user trying to view or change the
user mode for a user other than themselves.
6.2 Command responses.
Dummy reply number. Not used.
- Reply format used by USERHOST to list replies to
the query list. The reply string is composed as
<reply> ::= <nick>['*'] '=' <'+'|'-'><hostname>
The '*' indicates whether the client has registered
as an Operator. The '-' or '+' characters represent
whether the client has set an AWAY message or not
- Reply format used by ISON to list replies to the
"<nick> :<away message>"
":You are no longer marked as being away"
":You have been marked as being away"
- These replies are used with the AWAY command (if
allowed). RPL_AWAY is sent to any client sending a
PRIVMSG to a client which is away. RPL_AWAY is only
sent by the server to which the client is connected.
Replies RPL_UNAWAY and RPL_NOWAWAY are sent when the
client removes and sets an AWAY message.
"<nick> <user> <host> * :<real name>"
"<nick> <server> :<server info>"
"<nick> :is an IRC operator"
"<nick> <integer> :seconds idle"
"<nick> :End of /WHOIS list"
- Replies 311 - 313, 317 - 319 are all replies
generated in response to a WHOIS message. Given that
there are enough parameters present, the answering
server must either formulate a reply out of the above
numerics (if the query nick is found) or return an
error reply. The '*' in RPL_WHOISUSER is there as
the literal character and not as a wild card. For
each reply set, only RPL_WHOISCHANNELS may appear
more than once (for long lists of channel names).
The '@' and '+' characters next to the channel name
indicate whether a client is a channel operator or
has been granted permission to speak on a moderated
channel. The RPL_ENDOFWHOIS reply is used to mark
the end of processing a WHOIS message.
"<nick> <user> <host> * :<real name>"
"<nick> :End of WHOWAS"
- When replying to a WHOWAS message, a server must use
the replies RPL_WHOWASUSER, RPL_WHOISSERVER or
ERR_WASNOSUCHNICK for each nickname in the presented
list. At the end of all reply batches, there must
be RPL_ENDOFWHOWAS (even if there was only one reply
and it was an error).
"Channel :Users Name"
"<channel> <# visible> :<topic>"
":End of /LIST"
- Replies RPL_LISTSTART, RPL_LIST, RPL_LISTEND mark
the start, actual replies with data and end of the
server's response to a LIST command. If there are
no channels available to return, only the start
and end reply must be sent.
"<channel> <mode> <mode params>"
"<channel> :No topic is set"
- When sending a TOPIC message to determine the
channel topic, one of two replies is sent. If
the topic is set, RPL_TOPIC is sent back else
- Returned by the server to indicate that the
attempted INVITE message was successful and is
being passed onto the end client.
"<user> :Summoning user to IRC"
- Returned by a server answering a SUMMON message to
indicate that it is summoning that user.
"<version>.<debuglevel> <server> :<comments>"
- Reply by the server showing its version details.
The <version> is the version of the software being
used (including any patchlevel revisions) and the
<debuglevel> is used to indicate if the server is
running in "debug mode".
The "comments" field may contain any comments about
the version or further version details.
"<channel> <user> <host> <server> <nick> <H|G>[*][@|+] :<hopcount> <real name>"
"<name> :End of /WHO list"
- The RPL_WHOREPLY and RPL_ENDOFWHO pair are used
to answer a WHO message. The RPL_WHOREPLY is only
sent if there is an appropriate match to the WHO
query. If there is a list of parameters supplied
with a WHO message, a RPL_ENDOFWHO must be sent
after processing each list item with <name> being
"<channel> :[[@|+]<nick> [[@|+]<nick> [...]]]"
"<channel> :End of /NAMES list"
- To reply to a NAMES message, a reply pair consisting
of RPL_NAMREPLY and RPL_ENDOFNAMES is sent by the
server back to the client. If there is no channel
found as in the query, then only RPL_ENDOFNAMES is
returned. The exception to this is when a NAMES
message is sent with no parameters and all visible
channels and contents are sent back in a series of
RPL_NAMEREPLY messages with a RPL_ENDOFNAMES to mark
"<mask> <server> :<hopcount> <server info>"
"<mask> :End of /LINKS list"
- In replying to the LINKS message, a server must send
replies back using the RPL_LINKS numeric and mark the
end of the list using an RPL_ENDOFLINKS reply.v
"<channel> :End of channel ban list"
- When listing the active 'bans' for a given channel,
a server is required to send the list back using the
RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate
RPL_BANLIST is sent for each active banid. After the
banids have been listed (or if none present) a
RPL_ENDOFBANLIST must be sent.
":End of /INFO list"
- A server responding to an INFO message is required to
send all its 'info' in a series of RPL_INFO messages
with a RPL_ENDOFINFO reply to indicate the end of the
":- <server> Message of the day - "
":End of /MOTD command"
- When responding to the MOTD message and the MOTD file
is found, the file is displayed line by line, with
each line no longer than 80 characters, using
RPL_MOTD format replies. These should be surrounded
by a RPL_MOTDSTART (before the RPL_MOTDs) and an
":You are now an IRC operator"
- RPL_YOUREOPER is sent back to a client which has
just successfully issued an OPER message and gained
"<config file> :Rehashing"
- If the REHASH option is used and an operator sends
a REHASH message, an RPL_REHASHING is sent back to
"<server> :<string showing server's local time>"
- When replying to the TIME message, a server must send
the reply using the RPL_TIME format above. The string
showing the time need only contain the correct day and
time there. There is no further requirement for the
":UserID Terminal Host"
":%-8s %-9s %-8s"
":End of users"
":Nobody logged in"
- If the USERS message is handled by a server, the
replies RPL_USERSTART, RPL_USERS, RPL_ENDOFUSERS and
RPL_NOUSERS are used. RPL_USERSSTART must be sent
first, following by either a sequence of RPL_USERS
or a single RPL_NOUSER. Following this is
"Link <version & debug level> <destination> <next server>"
"Try. <class> <server>"
"H.S. <class> <server>"
"???? <class> [<client IP address in dot form>]"
"Oper <class> <nick>"
"User <class> <nick>"
"Serv <class> <int>S <int>C <server> <nick!user|*!*>@<host|server>"
"<newtype> 0 <client name>"
"File <logfile> <debug level>"
- The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection
which does not fit in the other categories but is
being displayed anyway.
"<linkname> <sendq> <sent messages> <sent bytes> <received messages> <received bytes> <time open>"
"C <host> * <name> <port> <class>"
"N <host> * <name> <port> <class>"
"I <host> * <host> <port> <class>"
"K <host> * <username> <port> <class>"
"Y <class> <ping frequency> <connect frequency> <max sendq>"
"<stats letter> :End of /STATS report"
"L <hostmask> * <servername> <maxdepth>"
":Server Up %d days %d:%02d:%02d"
"O <hostmask> * <name>"
"H <hostmask> * <servername>"
"<user mode string>"
- To answer a query about a client's own mode,
RPL_UMODEIS is sent back.
":There are <integer> users and <integer> invisible on <integer> servers"
"<integer> :operator(s) online"
"<integer> :unknown connection(s)"
"<integer> :channels formed"
":I have <integer> clients and <integer> servers"
- In processing an LUSERS message, the server
sends a set of replies from RPL_LUSERCLIENT,
RPL_LUSERCHANNELS and RPL_LUSERME. When
replying, a server must send back
RPL_LUSERCLIENT and RPL_LUSERME. The other
replies are only sent back if a non-zero count
is found for them.
"<server> :Administrative info"
- When replying to an ADMIN message, a server
is expected to use replies RLP_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the university and department
(RPL_ADMINLOC2) and finally the administrative
contact for the server (an email address here
is required) in RPL_ADMINEMAIL.
6.3 Reserved numerics.
These numerics are not described above since they fall into one of
the following categories:
- no longer in use;
- reserved for future planned use;
- in current use but are part of a non-generic 'feature' of
the current IRC server.
|209 ||RPL_TRACECLASS ||217 ||RPL_STATSQLINE|
|231 ||RPL_SERVICEINFO ||232 ||RPL_ENDOFSERVICES|
|233 ||RPL_SERVICE ||234 ||RPL_SERVLIST|
|235 ||RPL_SERVLISTEND || |
|316 ||RPL_WHOISCHANOP ||361 ||RPL_KILLDONE|
|362 ||RPL_CLOSING ||363 ||RPL_CLOSEEND|
|373 ||RPL_INFOSTART ||384 ||RPL_MYPORTIS|
|466 ||ERR_YOUWILLBEBANNED ||476 ||ERR_BADCHANMASK|
|492 ||ERR_NOSERVICEHOST || |