RPL_WELCOME

Undocumented in source.

Values

ValueMeaning
RPL_WELCOME001

The server sends RPL_WELCOME through RPL_MYINFO to a user upon successful registration.

RPL_YOURHOST002

ditto

RPL_CREATED003

ditto

RPL_MYINFO004

ditto

RPL_BOUNCE005

Sent by the server to a user to suggest an alternative server. This is often used when the connection is refused because the server is already full.

RPL_USERHOST302

Reply format used by USERHOST to list replies to the query list.

RPL_ISON303

Reply format used by ISON to list replies to the query list.

RPL_AWAY301

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.

RPL_UNAWAY305

ditto

RPL_NOWAWAY306

ditto

RPL_WHOISUSER311

Replies RPL_WHOISUSER through RPL_WHOIS, RPL_WHOISIDLE through RPL_WHOISCHANNELS 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.

RPL_WHOISSERVER312

ditto

RPL_WHOISOPERATOR313

ditto

RPL_WHOISIDLE317

ditto

RPL_ENDOFWHOIS318

ditto

RPL_WHOISCHANNELS319

ditto

RPL_WHOWASUSER314

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).

RPL_ENDOFWHOWAS369

ditto

RPL_LIST322

Replies RPL_LIST, RPL_LISTEND mark the actual replies with data and end of the server's responseto a LIST command. If there are no channels available to return, only the end reply MUST be sent.

RPL_LISTEND323

ditto

RPL_LISTSTART321

Obsolete. Not used.

RPL_UNIQOPIS325
RPL_CHANNELMODEIS324
RPL_NOTOPIC331

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 RPL_NOTOPIC.

RPL_TOPIC332

ditto

RPL_INVITING341

Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client.

RPL_SUMMONING342

Returned by a server answering a SUMMON message to indicate that it is summoning that user.

RPL_INVITELIST346

When listing the 'invitations masks' for a given channel, a server is required to send the list back using the RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A separate RPL_INVITELIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFINVITELIST MUST be sent.

RPL_ENDOFINVITELIST347

ditto

RPL_EXCEPTLIST348

When listing the 'exception masks' for a given channel, a server is required to send the list back using the RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A separate RPL_EXCEPTLIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFEXCEPTLIST MUST be sent.

RPL_ENDOFEXCEPTLIST349

ditto

RPL_VERSION351

Reply by the server showing its version details.

RPL_WHOREPLY352

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.

RPL_ENDOFWHO315

ditto

RPL_NAMREPLY353

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 the end.

RPL_ENDOFNAMES366

ditto

RPL_BANLIST367

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 banmask. After the banmasks have been listed (or if none present) a RPL_ENDOFBANLIST MUST be sent.

RPL_ENDOFBANLIST368

ditto

RPL_INFO371

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 replies.

RPL_ENDOFINFO374

ditto

RPL_MOTDSTART375

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 MUST be surrounded by a RPL_MOTDSTART (before the RPL_MOTDs) and an RPL_ENDOFMOTD (after).

RPL_MOTD372

ditto

RPL_ENDOFMOTD376

ditto

RPL_YOUREOPER381

RPL_YOUREOPER is sent back to a client which has just successfully issued an OPER message and gained operator status.

RPL_REHASHING382

If the REHASH option is used and an operator sends a REHASH message, an RPL_REHASHING is sent back to the operator.

RPL_YOURESERVICE383

Sent by the server to a service upon successful registration.

RPL_TIME391

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.

RPL_USERSSTART392

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 RPL_ENDOFUSERS.

RPL_USERS393

ditto

RPL_ENDOFUSERS394

ditto

RPL_NOUSERS395

ditto

RPL_TRACECONNECTING201

ditto

RPL_TRACEHANDSHAKE202

ditto

RPL_TRACEUNKNOWN203

ditto

RPL_TRACEOPERATOR204

ditto

RPL_TRACEUSER205

ditto

RPL_TRACESERVER206

ditto

RPL_TRACESERVICE207

ditto

RPL_TRACENEWTYPE208

ditto

RPL_TRACECLASS209

ditto

RPL_TRACELOG261

ditto

RPL_TRACEEND262

ditto

RPL_TRACERECONNECT210

Unused.

RPL_STATSLINKINFO211

Returned from the server in response to the STATS message.

RPL_STATSCOMMANDS212

ditto

RPL_ENDOFSTATS219

ditto

RPL_STATSUPTIME242

ditto

RPL_STATSOLINE243

ditto

RPL_UMODEIS221
RPL_SERVLIST234
RPL_SERVLISTEND235

When listing services in reply to a SERVLIST message, a server is required to send the list back using the RPL_SERVLIST and RPL_SERVLISTEND messages. A separate RPL_SERVLIST is sent for each service. After the services have been listed (or if none present) a RPL_SERVLISTEND MUST be sent.

RPL_LUSERCLIENT251

In processing an LUSERS message, the server sends a set of replies from RPL_LUSERCLIENT, RPL_LUSEROP, RPL_USERUNKNOWN, 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.

RPL_LUSEROP252

ditto

RPL_LUSERUNKNOWN253

ditto

RPL_LUSERCHANNELS254

ditto

RPL_LUSERME255

ditto

RPL_ADMINME256

When replying to an ADMIN message, a server is expected to use replies RPL_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 institution (RPL_ADMINLOC2) and finally the administrative contact for the server (an email address here is REQUIRED) in RPL_ADMINEMAIL.

RPL_ADMINLOC1257

ditto

RPL_ADMINLOC2258

ditto

RPL_ADMINEMAIL259

ditto

RPL_TRYAGAIN263

When a server drops a command without processing it, it MUST use the reply RPL_TRYAGAIN to inform the originating client.

ERR_NOSUCHNICK401

Used to indicate the nickname parameter supplied to a command is currently unused.

ERR_NOSUCHSERVER402

Used to indicate the server name given currently does not exist.

ERR_NOSUCHCHANNEL403

Used to indicate the given channel name is invalid.

ERR_CANNOTSENDTOCHAN404

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 or where the user is banned and is trying to send a PRIVMSG message to that channel.

ERR_TOOMANYCHANNELS405

Sent to a user when they have joined the maximum number of allowed channels and they try to join another channel.

ERR_WASNOSUCHNICK406

Returned by WHOWAS to indicate there is no history information for that nickname.

ERR_TOOMANYTARGETS407

Returned to a client which is attempting to send a PRIVMSG/NOTICE using the user@host destination format and for a user@host which has several occurrences. Returned to a client which trying to send a PRIVMSG/NOTICE to too many recipients. Returned to a client which is attempting to JOIN a safe channel using the shortname when there are more than one such channel.

ERR_NOSUCHSERVICE408

Returned to a client which is attempting to send a SQUERY to a service which does not exist.

ERR_NOORIGIN409

PING or PONG message missing the originator parameter.

ERR_NORECIPIENT411

ERR_NOTEXTTOSEND through ERR_BADMASK 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.

ERR_NOTEXTTOSEND412

ditto

ERR_NOTOPLEVEL413

ditto

ERR_WILDTOPLEVEL414

ditto

ERR_BADMASK415

ditto

ERR_UNKNOWNCOMMAND421

Returned to a registered client to indicate that the command sent is unknown by the server.

ERR_NOMOTD422

Server's MOTD file could not be opened by the server.

ERR_NOADMININFO423

Returned by a server in response to an ADMIN message when there is an error in finding the appropriate information.

ERR_FILEERROR424

Generic error message used to report a failed file operation during the processing of a message.

ERR_NONICKNAMEGIVEN431

Returned when a nickname parameter expected for a command and isn't found.

ERR_ERRONEUSNICKNAME432

Returned after receiving a NICK message which contains characters which do not fall in the defined set.

ERR_NICKNAMEINUSE433

Returned when a NICK message is processed that results in an attempt to change to a currently existing nickname.

ERR_NICKCOLLISION436

Returned by a server to a client when it detects a nickname collision (registered of a NICK that already exists by another server).

Meta