Aquariophile: -> Mit SOCKET's zu IRC connecten --> USER :Not enough parameters

Hallo!

Über SOCKET's in einem Perl-Script connecte ich zu IRC.
Relevanter Teil im Script:

#############
print $client_socket "USER test\n";
print $client_socket "NICK test214324\n";
print $client_socket "JOIN #testchannel\n";
print $client_socket "PRIVMSG #testchannel Hello\n";
#############

Das müsste eigentlich reichen, USER und NICK
Anstatt USER versuchte ich auch schon USERNAME,
und ob ich REALNAME dazunehme oder nicht macht auch keinen unterschied,
ist auch egal ob ich eine EMAIL angebe.

Es kommt immer folgende Meldung von Seiten des Servers:

-------
:sauron.ca.us.webchat.org 461 * USER :Not enough parameters
:sauron.ca.us.webchat.org 451 * :You have not registered
:sauron.ca.us.webchat.org 451 * :You have not registered
-------

Was mach ich falsch?

DANKE!
Aquariophile

  1. hi!

    print $client_socket "USER test\n";
    print $client_socket "NICK test214324\n";
    print $client_socket "JOIN #testchannel\n";
    print $client_socket "PRIVMSG #testchannel Hello\n";
    :sauron.ca.us.webchat.org 461 * USER :Not enough parameters
    Was mach ich falsch?

    Ich hab dir doch schon im Chat gesagt, dass du mal im betreffenden
    RFC[1] nachlesen sollst. Dort steht:

    === cut ===
    4.1.3 User message

    Command: USER
       Parameters: <username> <hostname> <servername> <realname>

    The USER message is used at the beginning of connection to specify
       the username, hostname, servername and realname of s new user.  It is
       also used in communication between servers to indicate new user
       arriving on IRC, since only after both USER and NICK have been
       received from a client does a user become registered.

    Between servers USER must to be prefixed with client's NICKname.
       Note that hostname and servername are normally ignored by the IRC
       server when the USER command comes from a directly connected client
       (for security reasons), but they are used in server to server
       communication.  This means that a NICK must always be sent to a
       remote server when a new user is being introduced to the rest of the
       network before the accompanying USER is sent.

    It must be noted that realname parameter must be the last parameter,
       because it may contain space characters and must be prefixed with a
       colon (':') to make sure this is recognised as such.

    Since it is easy for a client to lie about its username by relying
       solely on the USER message, the use of an "Identity Server" is
       recommended.  If the host which a user connects from has such a
       server enabled the username is set to that as in the reply from the
       "Identity Server".

    Numeric Replies:

    ERR_NEEDMOREPARAMS              ERR_ALREADYREGISTRED

    Examples:

    USER guest tolmoon tolsun :Ronnie Reagan

    ; User registering themselves with a
                                       username of "guest" and real name
                                       "Ronnie Reagan".

    :testnick USER guest tolmoon tolsun :Ronnie Reagan
                                       ; message between servers with the
                                       nickname for which the USER command
                                       belongs to
    === cut ===

    Siehe auch die benachbarten Abschnitte zu NICK und PASS.

    bye, Frank!

    [1] mindestens RFC 1459.