Net::NNTP(3perl) | Perl Programmers Reference Guide | Net::NNTP(3perl) |
Net::NNTP - NNTP Client class
use Net::NNTP; $nntp = Net::NNTP->new("some.host.name"); $nntp->quit; # start with SSL, e.g. nntps $nntp = Net::NNTP->new("some.host.name", SSL => 1); # start with plain and upgrade to SSL $nntp = Net::NNTP->new("some.host.name"); $nntp->starttls;
"Net::NNTP" is a class implementing a simple NNTP client in Perl as described in RFC977 and RFC4642. With IO::Socket::SSL installed it also provides support for implicit and explicit TLS encryption, i.e. NNTPS or NNTP+STARTTLS.
The Net::NNTP class is a subclass of Net::Cmd and (depending on avaibility) of IO::Socket::IP, IO::Socket::INET6 or IO::Socket::INET.
"OPTIONS" are passed in a hash like fashion, using key and value pairs. Possible options are:
Host - NNTP host to connect to. It may be a single scalar, as defined for the "PeerAddr" option in IO::Socket::INET, or a reference to an array with hosts to try in turn. The "host" method will return the value which was used to connect to the host.
Port - port to connect to. Default - 119 for plain NNTP and 563 for immediate SSL (nntps).
SSL - If the connection should be done from start with SSL, contrary to later upgrade with "starttls". You can use SSL arguments as documented in IO::Socket::SSL, but it will usually use the right arguments already.
Timeout - Maximum time, in seconds, to wait for a response from the NNTP server, a value of zero will cause all IO operations to block. (default: 120)
Debug - Enable the printing of debugging information to STDERR
Reader - If the remote server is INN then initially the connection will be to innd, by default "Net::NNTP" will issue a "MODE READER" command so that the remote server becomes nnrpd. If the "Reader" option is given with a value of zero, then this command will not be sent and the connection will be left talking to innd.
LocalAddr and LocalPort - These parameters are passed directly to IO::Socket to allow binding the socket to a specific local address and port.
Domain - This parameter is passed directly to IO::Socket and makes it possible to enforce IPv4 connections even if IO::Socket::IP is used as super class. Alternatively Family can be used.
Unless otherwise stated all methods return either a true or false value, with true meaning that the operation was a success. When a method states that it returns a value, failure will be returned as undef or an empty list.
"Net::NNTP" inherits from "Net::Cmd" so methods defined in "Net::Cmd" may be used to send commands to the remote NNTP server in addition to the methods documented here.
If "FH" is specified then it is expected to be a valid filehandle and the result will be printed to it, on success a true value will be returned. If "FH" is not specified then the return value, on success, will be a reference to an array containing the article requested, each entry in the array will contain one line of the article.
If no arguments are passed then the current article in the currently selected newsgroup is fetched.
"MSGNUM" is a numeric id of an article in the current newsgroup, and will change the current article pointer. "MSGID" is the message id of an article as shown in that article's header. It is anticipated that the client will obtain the "MSGID" from a list provided by the "newnews" command, from references contained within another article, or from the message-id provided in the response to some other commands.
If there is an error then "undef" will be returned.
Using the "nntpstat" command to select by message-id is valid but of questionable value, since a selection by message-id does not alter the "current article pointer".
Returns the message-id of the "current article".
In a scalar context it returns the group name.
In an array context the return value is a list containing, the number of articles in the group, the number of the first article, the number of the last article and the group name.
Returns true if the server desires the article and "MESSAGE" was successfully sent, if specified.
If "MESSAGE" is not specified then the message must be sent using the "datasend" and "dataend" methods from Net::Cmd
"MESSAGE" can be either an array of lines or a reference to an array and must be encoded by the caller to octets of whatever encoding is required, e.g. by using the Encode module's "encode()" function.
Returns the message-id of the article.
Returns a reference to a list which contains the message-ids of all news posted after "SINCE", that are in a groups which matched "GROUPS" and a distribution which matches "DISTRIBUTIONS".
Returns the message-id of the article.
If "MESSAGE" is not specified then the message must be sent using the "datasend" and "dataend" methods from Net::Cmd
"MESSAGE" can be either an array of lines or a reference to an array and must be encoded by the caller to octets of whatever encoding is required, e.g. by using the Encode module's "encode()" function.
The message, either sent via "datasend" or as the "MESSAGE" parameter, must be in the format as described by RFC822 and must contain From:, Newsgroups: and Subject: headers.
These methods use commands that are not part of the RFC977 documentation. Some servers may not support all of them.
The return value will be a reference to a hash where the keys are the message numbers and each value contains the text of the requested header for that message.
The names of the fields can be obtained by calling "overview_fmt".
Returns a reference to a HASH where the keys are the message numbers and the values are the References: lines from the articles
This is required by some servers. For example if you are connecting to an INN server and you have transfer permission your connection will be connected to the transfer daemon, not the NNTP daemon. Issuing this command will cause the transfer daemon to hand over control to the NNTP daemon.
Some servers do not understand this command, but issuing it and ignoring the response is harmless.
The following NNTP command are unsupported by the package, and there are no plans to do so.
AUTHINFO GENERIC XTHREAD XSEARCH XINDEX
If "MESSAGE-SPEC" is a reference to a list of two message numbers and the second number in a range is less than or equal to the first then the range represents all messages in the group after the first message number.
NOTE For compatibility reasons only with earlier versions of Net::NNTP a message spec can be passed as a list of two numbers, this is deprecated and a reference to the list should now be passed
Patterns are implicitly anchored at the beginning and end of each string when testing for a match.
There are five pattern matching operations other than a strict one-to-one match between the pattern and the source to be checked for a match.
The first is an asterisk "*" to match any sequence of zero or more characters.
The second is a question mark "?" to match any single character. The third specifies a specific set of characters.
The set is specified as a list of characters, or as a range of characters where the beginning and end of the range are separated by a minus (or dash) character, or as any combination of lists and ranges. The dash can also be included in the set as a character it if is the beginning or end of the set. This set is enclosed in square brackets. The close square bracket "]" may be used in a set if it is the first character in the set.
The fourth operation is the same as the logical not of the third operation and is specified the same way as the third with the addition of a caret character "^" at the beginning of the test string just inside the open square bracket.
The final operation uses the backslash character to invalidate the special meaning of an open square bracket "[", the asterisk, backslash or the question mark. Two backslashes in sequence will result in the evaluation of the backslash as a character with no special meaning.
Net::Cmd, IO::Socket::SSL
Graham Barr <gbarr@pobox.com>.
Steve Hay <shay@cpan.org> is now maintaining libnet as of version 1.22_02.
Copyright (C) 1995-1997 Graham Barr. All rights reserved.
Copyright (C) 2013-2016 Steve Hay. All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself, i.e. under the terms of either the GNU General Public License or the Artistic License, as specified in the LICENCE file.
2023-11-25 | perl v5.32.1 |