HTML layout by Tatu J. Lund Apr 1997
Network Working Group
Request for Comments: 1459
J. Oikarinen
D. Reed
May 1993
6. REPLIES
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.
401
ERR_NOSUCHNICK
“
Used to indicate the nickname parameter supplied to a command is currently unused. 402
ERRNOSUCHSERVER
_”:No such server” Used to indicate the server name given currently doesn’t exist. 403
ERRNOSUCHCHANNEL
_”:No such channel” Used to indicate the given channel name is invalid. 404
ERRCANNOTSENDTOCHAN
_”: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. 405
ERRTOOMANYCHANNELS
_”: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 another channel. 406
ERRWASNOSUCHNICK
_”:There was no such nickname” Returned by WHOWAS to indicate there is no history information for that nickname. 407
ERRTOOMANYTARGETS
_”: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. 409
ERRNOORIGIN
_”:No origin specified”PING or PONG message missing the originator parameter which is required since these commands must work without valid prefixes. 411
ERRNORECIPIENT
_”:No recipient given ()”
412
ERR_NOTEXTTOSEND
“:No text to send”
413
ERR_NOTOPLEVEL
“
414
ERR_WILDTOPLEVEL
“
412 - 414 are returned by PRIVMSG to indicate that the message wasn’t delivered for some reason. ERRNOTOPLEVEL and ERRWILDTOPLEVEL are errors that are returned when an invalid use of “PRIVMSG $
” or “PRIVMSG # ” is attempted. 421 ERRUNKNOWNCOMMAND
_”:Unknown command” Returned to a registered client to indicate that the command sent is unknown by the server. 422
ERRNOMOTD
_”:MOTD File is missing”Server’s MOTD file could not be opened by the server. 423
ERRNOADMININFO
_”:No administrative info available” Returned by a server in response to an ADMIN message when there is an error in finding the appropriate information. 424
ERRFILEERROR
_”:File error doingon “ Generic error message used to report a failed file operation during the processing of a message. 431
ERRNONICKNAMEGIVEN
_”:No nickname given”Returned when a nickname parameter expected for a command and isn’t found. 432
ERRERRONEUSNICKNAME
_”: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. 433
ERRNICKNAMEINUSE
_”:Nickname is already in use” Returned when a NICK message is processed that results in an attempt to change to a currently existing nickname. 436
ERRNICKCOLLISION
_”: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). 441
ERRUSERNOTINCHANNEL
_”: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. 442
ERRNOTONCHANNEL
_”: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. 443
ERRUSERONCHANNEL
_”:is already on channel” Returned when a client tries to invite a user to a channel they are already on. 444
ERRNOLOGIN
_”:User not logged in” Returned by the summon after a SUMMON command for a user was unable to be performed since they were not logged in. 445
ERRSUMMONDISABLED
_”:SUMMON has been disabled”Returned as a response to the SUMMON command. Must be returned by any server which does not implement it. 446
ERRUSERSDISABLED
_”:USERS has been disabled”Returned as a response to the USERS command. Must be returned by any server which does not implement it. 451
ERRNOTREGISTERED
_”: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. 461
ERRNEEDMOREPARAMS
_”:Not enough parameters” Returned by the server by numerous commands to indicate to the client that it didn’t supply enough parameters. 462
ERRALREADYREGISTRED
_”: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). 463
ERRNOPERMFORHOST
_”: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 is tried. 464
ERRPASSWDMISMATCH
_”:Password incorrect”Returned to indicate a failed attempt at registering a connection for which a password was required and was either not given or incorrect. 465
ERRYOUREBANNEDCREEP
_”: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. 467
ERRKEYSET
_”:Channel key already set”
471
ERR_CHANNELISFULL
“
472
ERR_UNKNOWNMODE
“
473
ERR_INVITEONLYCHAN
“
474
ERR_BANNEDFROMCHAN
“
475
ERR_BADCHANNELKEY
“
481
ERR_NOPRIVILEGES
“:Permission Denied- You’re not an IRC operator”
Any command requiring operator privileges to operate must return this error to indicate the attempt was unsuccessful. 482
ERRCHANOPRIVSNEEDED
_”: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 channel. 483
ERRCANTKILLSERVER
_”: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. 491
ERRNOOPERHOST
_”: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 returned. 501
ERRUMODEUNKNOWNFLAG
_”: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. 502
ERRUSERSDONTMATCH
_”: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.
300
RPL_NONE
Dummy reply number. Not used.
302
RPL_USERHOST
”:[
- Reply format used by USERHOST to list replies to the query list. The reply string is composed as follows:
::= [‘*’] ‘=’ <’+’|’-‘>
The ‘*’ indicates whether the client has registered as an Operator. The ‘-’ or ‘+’ characters represent whether the client has set an AWAY message or not respectively.
303
RPL_ISON
”:[
Reply format used by ISON to list replies to the query list. 301
RPLAWAY
_”: ”
305
RPL_UNAWAY
“:You are no longer marked as being away”
306
RPL_NOWAWAY
“:You have been marked as being away”
These replies are used with the AWAY command (if allowed). RPLAWAY is sent to any client sending a PRIVMSG to a client which is away. RPLAWAY is only sent by the server to which the client is connected. Replies RPLUNAWAY and RPLNOWAWAY are sent when the client removes and sets an AWAY message. 311
RPLWHOISUSER
_”* : ”
312
RPL_WHOISSERVER
“
313
RPL_WHOISOPERATOR
“
317
RPL_WHOISIDLE
“
318
RPL_ENDOFWHOIS
“
319
RPL_WHOISCHANNELS
“
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. 314
RPLWHOWASUSER
_”* : ”
369
RPL_ENDOFWHOWAS
“
When replying to a WHOWAS message, a server must use the replies RPLWHOWASUSER, RPLWHOISSERVER or ERRWASNOSUCHNICK for each nickname in the presented list. At the end of all reply batches, there must be RPLENDOFWHOWAS (even if there was only one reply and it was an error). 321
RPLLISTSTART
_”Channel :Users Name”
322
RPL_LIST
“
323
RPL_LISTEND
“:End of /LIST”
Replies RPLLISTSTART, RPLLIST, 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. 324
RPLCHANNELMODEIS
_”“
331
RPL_NOTOPIC
“
332
RPL_TOPIC
“
When sending a TOPIC message to determine the channel topic, one of two replies is sent. If the topic is set, RPLTOPIC is sent back else RPLNOTOPIC. 341
RPLINVITING
_”“ Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client. 342
RPLSUMMONING
_”:Summoning user to IRC” Returned by a server answering a SUMMON message to indicate that it is summoning that user. 351
RPLVERSION
_”. : ” Reply by the server showing its version details. The
is the version of the software being used (including any patchlevel revisions) and the 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.
352
RPL_WHOREPLY
“
315
RPL_ENDOFWHO
“
The RPLWHOREPLY and RPLENDOFWHO pair are used to answer a WHO message. The RPLWHOREPLY 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 RPLENDOFWHO must be sent after processing each list item with
being the item. 353 RPLNAMREPLY
_”:[[@|+] [[@|+] […]]]”
366
RPL_ENDOFNAMES
“
To reply to a NAMES message, a reply pair consisting of RPLNAMREPLY and RPLENDOFNAMES is sent by the server back to the client. If there is no channel found as in the query, then only RPLENDOFNAMES 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 RPLNAMEREPLY messages with a RPL_ENDOFNAMES to mark the end. 364
RPLLINKS
_”: “
365
RPL_ENDOFLINKS
“
- In replying to the LINKS message, a server must send replies back using the RPLLINKS numeric and mark the end of the list using an RPLENDOFLINKS reply.v 367
RPLBANLIST
_”“
368
RPL_ENDOFBANLIST
“
When listing the active ‘bans’ for a given channel, a server is required to send the list back using the RPLBANLIST and RPLENDOFBANLIST messages. A separate RPLBANLIST is sent for each active banid. After the banids have been listed (or if none present) a RPLENDOFBANLIST must be sent. 371
RPLINFO
_”:”
374
RPL_ENDOFINFO
“:End of /INFO list”
A server responding to an INFO message is required to send all its ‘info’ in a series of RPLINFO messages with a RPLENDOFINFO reply to indicate the end of the replies. 375
RPLMOTDSTART
_”:-Message of the day - “
372
RPL_MOTD
”:-
376
RPL_ENDOFMOTD
“: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 RPLMOTD format replies. These should be surrounded by a RPLMOTDSTART (before the RPLMOTDs) and an RPLENDOFMOTD (after). 381
RPLYOUREOPER
_”:You are now an IRC operator”RPL_YOUREOPER is sent back to a client which has just successfully issued an OPER message and gained operator status. 382
RPLREHASHING
_”:Rehashing” If the REHASH option is used and an operator sends a REHASH message, an RPL_REHASHING is sent back to the operator. 391
RPLTIME
_”:<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 time string. 392
RPLUSERSSTART
_”:UserID Terminal Host”
393
RPL_USERS
”:%-8s %-9s %-8s”
394
RPL_ENDOFUSERS
“:End of users”
395
RPL_NOUSERS
“:Nobody logged in”
If the USERS message is handled by a server, the replies RPLUSERSTART, RPLUSERS, RPLENDOFUSERS and RPLNOUSERS are used. RPLUSERSSTART must be sent first, following by either a sequence of RPLUSERS or a single RPLNOUSER. Following this is RPLENDOFUSERS. 200
RPLTRACELINK
_”Link“
201
RPL_TRACECONNECTING
“Try.
202
RPL_TRACEHANDSHAKE
“H.S.
203
RPL_TRACEUNKNOWN
”????
204
RPL_TRACEOPERATOR
“Oper
205
RPL_TRACEUSER
“User
206
RPL_TRACESERVER
“Serv
208
RPL_TRACENEWTYPE
“
261
RPL_TRACELOG
“File
The RPLTRACE* 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 RPLTRACEUNKNOWN, RPLTRACECONNECTING and RPLTRACEHANDSHAKE 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’. RPLTRACELINK is sent by any server which handles a TRACE message and has to pass it on to another server. The list of RPLTRACELINKs 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. 211
RPLSTATSLINKINFO
_”
212
RPL_STATSCOMMANDS
“
213
RPL_STATSCLINE
“C
214
RPL_STATSNLINE
“N
215
RPL_STATSILINE
“I
216
RPL_STATSKLINE
“K
218
RPL_STATSYLINE
“Y
219
RPL_ENDOFSTATS
“
241
RPL_STATSLLINE
“L
242
RPL_STATSUPTIME
“:Server Up %d days %d:%02d:%02d”
243
RPL_STATSOLINE
“O
244
RPL_STATSHLINE
“H
221
RPL_UMODEIS
“
To answer a query about a client’s own mode, RPL_UMODEIS is sent back. 251
RPLLUSERCLIENT
_”:There areusers and invisible on servers”
252
RPL_LUSEROP
“
253
RPL_LUSERUNKNOWN
“
254
RPL_LUSERCHANNELS
“
255
RPL_LUSERME
“:I have
In processing an LUSERS message, the server sends a set of replies from RPLLUSERCLIENT, RPLLUSEROP, RPLUSERUNKNOWN, RPLLUSERCHANNELS and RPLLUSERME. When replying, a server must send back RPLLUSERCLIENT and RPL_LUSERME. The other replies are only sent back if a non-zero count is found for them. 256
RPLADMINME
_”:Administrative info”
257
RPL_ADMINLOC1
”:
258
RPL_ADMINLOC2
”:
259
RPL_ADMINEMAIL
”:
- When replying to an ADMIN message, a server is expected to use replies RLPADMINME through to RPLADMINEMAIL and provide a text message with each. For RPLADMINLOC1 a description of what city, state and country the server is in is expected, followed by details of the university and department (RPLADMINLOC2) 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
[ go back | search | help | send email ]