--- lmtp2nntp.pod 2001/08/29 14:58:21 1.9
+++ lmtp2nntp.pod 2001/08/30 08:35:44 1.10
@@ -8,13 +8,14 @@
=head1 SYNOPSIS
B<lmtp2nntp>
+[B<-V>]
[B<-d> I<deliverymode>]
[B<-g> I<groupmode>]
-[B<-h> I<host>[I<:port>]]
+[B<-h> I<host>[I<:port>][,I<host>[I<:port>], ...]]
[B<-m> I<maxmessagesize>]
[B<-t> I<tracefile>]
[B<-v>]
-[B<-V>]
+I<newsgroup> [I<newsgroup> ...]
B<FIXME NOT YET IMPLEMENTED>
[B<-o> I<origin>]
[B<-j> I<hostname>]
@@ -22,7 +23,6 @@
[B<-T> I<timeout>]
[B<-l> I<logtarget>]
-
=head1 DESCRIPTION
The B<lmtp2nntp> program is a LMTP service which is usually invoked by a MTA.
@@ -37,55 +37,9 @@
=over 4
-=item B<-o> I<origin>
-
-Outgoing network IP address or hostname to bind to.
-
-=item B<-j> I<hostname>
-
-Own FQDN used in LMTP and NNTP protocols.
-
-=item B<-i> I<messageid>
-
-Message id of MTA (for logging purposes only).
-
-=item B<-t> I<timeout>
+=item B<-V>
-LMTP and NNTP protocol timeouts (in seconds).
-
-=item [B<-m> I<maxmessagesize>]
-
-Maximum message size in bytes. Default is 8388608 (8M). Values below 64 are
-considered unacceptable small.
-
-=item B<-p> I<protocol>
-
-Incoming protocol. Default is C<stdin> which means B<lmtp2nntp>
-reads the incoming mail from F<stdin> in RFC822 message format and reports errors to F<stderr>.
-Alternatively if I<protocol> is C<LMTP>, B<lmtp2nntp> speaks Local Mail
-Transport Protocol (LMTP) according to RFC 2033 on F<stdin>/F<stdout>.
-
-=item B<-l> C<stderr>
-
-=item B<-l> C<syslog>[C<:>I<facility>]
-
-=item B<-l> C<file:>I<localfile>
-
-Logging target. This option can be specified more than once. Default is no
-logging. Default I<facility> for C<syslog:> is C<lmtp2nntp>.
-
-=item B<-h> I<host>[:<port>]
-
-Hostname or address and optional TCP port of a NNTP service. Unless a port is
-specified, getserbyname(nntp) is queried with fallback to 119/tcp. If C<-h>
-option is ommited, the environment variable C<NNTPSERVER> is read, if this is
-undefined or empty C<news> is used and if this doesn't resolve, C<localhost>
-is assumed.
-
-This option can be specified more than once. It is assumed that multiple
-servers are used to increase the reliability of the news system and to speed
-up distribution by posting the same article to more than one server. In regard
-to this program they must provide the same groups and talk to each other.
+Print version information.
=item B<-d> I<deliverymode>
@@ -105,12 +59,32 @@
Possible values for I<groupmode> are C<arg> (default), C<envelope> and
C<header>. In C<arg> mode, the C<newsgroup>s specified as command line
arguments are ultimate destinations for the received messages. Addresses from
-envelope are ignored. In C<envelope> mode the newsgroup(s) are taken from the
-LMTP envelope, in C<header> mode the newsgroup(s) are taken from the header.
-In all modes C<Newsgroups:> header is rewritten. In C<envelope> and C<header>
-mode groups must still be specified as command line arguments. However, in
-these modes the command line arguments are filters representing allowed
-groups. Filters can be specified as wildmat's.
+envelope and headers are ignored. In C<envelope> mode the newsgroup(s) are
+taken from the LMTP envelope, in C<header> mode the newsgroup(s) are taken
+from the header. In all modes C<Newsgroups:> header is rewritten. In
+C<envelope> and C<header> mode groups must still be specified as command line
+arguments. However, in these modes the command line arguments are filters
+representing allowed groups. Filters can be specified as wildmat's.
+
+=item [B<-h> I<host>[I<:port>][,I<host>[I<:port>], ...]]
+
+Hostname or address and optional TCP port of a NNTP service. Unless a port is
+specified, getserbyname(nntp) is queried with fallback to 119/tcp. If C<-h>
+option is ommited, the environment variable C<NNTPSERVER> is read, if this is
+undefined or empty C<news> is used and if this doesn't resolve, C<localhost>
+is assumed.
+
+This option can be specified more than once and it is possible to specify more
+than one host/ port per option as a comma-separated list. It is assumed that
+multiple servers are used to increase the reliability of the news system and
+to speed up distribution by posting the same article to more than one server.
+In regard to this program they must provide the same groups and talk to each
+other.
+
+=item [B<-m> I<maxmessagesize>]
+
+Maximum message size in bytes. Default is 8388608 (8M). Values below 64 are
+considered unacceptable small.
=item B<-t> I<tracefile>
@@ -122,10 +96,45 @@
Enable verbose processing messages in logfile. When using C<syslog:> these
messages are logged with C<info> level.
-=item I<newsgroup>
+=item I<newsgroup> [I<newsgroup> ...]
+
+Newsgroup to post the message to or filter, depending on groupmode. Multiple
+groups can be specified. Crosspostings succeed if delivery to I<any> group
+succeeds.
-Newsgroup to post the message to. Multiple groups can be specified.
-Crosspostings only succeed if delivery to I<all> groups succeed.
+B<FIXME NOT YET IMPLEMENTED>
+
+=item B<-o> I<origin>
+
+Outgoing network IP address or hostname to bind to.
+
+=item B<-j> I<hostname>
+
+Own FQDN used in LMTP and NNTP protocols.
+
+=item B<-i> I<messageid>
+
+Message id of MTA (for logging purposes only).
+
+=item B<-t> I<timeout>
+
+LMTP and NNTP protocol timeouts (in seconds).
+
+=item B<-p> I<protocol>
+
+Incoming protocol. Default is C<stdin> which means B<lmtp2nntp>
+reads the incoming mail from F<stdin> in RFC822 message format and reports errors to F<stderr>.
+Alternatively if I<protocol> is C<LMTP>, B<lmtp2nntp> speaks Local Mail
+Transport Protocol (LMTP) according to RFC 2033 on F<stdin>/F<stdout>.
+
+=item B<-l> C<stderr>
+
+=item B<-l> C<syslog>[C<:>I<facility>]
+
+=item B<-l> C<file:>I<localfile>
+
+Logging target. This option can be specified more than once. Default is no
+logging. Default I<facility> for C<syslog:> is C<lmtp2nntp>.
=back
@@ -134,12 +143,12 @@
t.virtusertable
# mail to news gateway
- posting+*@mail.de.cw.net %2@lmtp2nntp
+ posting+*@first.gateway.example %2@lmtp2nntp
t.mailertable
# mail to news gateway
- lmtp2nntp lmtp2nntp:visp.engelschall.com
+ lmtp2nntp lmtp2nntp:second.gateway.example
sendmail.m4
@@ -149,94 +158,85 @@
define(`LMTP2NNTP_MAILER_DELIVERYMODE', `post')
define(`LMTP2NNTP_MAILER_GROUPMODE', `envelope')
define(`LMTP2NNTP_MAILER_ARGS', `-t confMYVARDIR/lmtp2nntp.log')
- define(`LMTP2NNTP_MAILER_GROUPS', `cw.\* en.\*')
+ define(`LMTP2NNTP_MAILER_GROUPS', `alt.test.\* alt.binaries.test')
MAILER(lmtp2nntp)
-=head1 EXAMPLE
+=head1 DIAGNOSTICS
- $ cat rfc822.message | lmtp2nntp -l /tmp/log -v -h mynews foo.bar
+when invoked as LMTP server
-reads rfc822.message and posts it into group "foo.bar" using NNTP service on
-host "mynews". Activity is logged to /tmp/log. If posting is
-successful, the exit status is 0.
+ 0 = successful execution
+ 1 = execution failed
- $ cat rfc822.message | lmtp2nntp -h news1 -h news2 -h news3 foo.bar
+Returning proper delivery status notification is part of the LMTP protocol.
-reads rfc822.message and posts it into group "foo.bar" using NNTP service on
-all hosts "news1", "news2" and "news3". Activtiy is not logged.
-If at least one posting is successful, the exit status is 0.
+=head1 STANDARDS
- $ cat rfc822.message | lmtp2nntp -l stderr foo.bar quux.bar test.bar
+=over 4
-reads rfc822.message and posts it into groups "foo.bar", "quux.bar" and
-"test.bar" using NNTP service on host C<${NNTPSERVER:-news}>. Activity
-is logged to stderr. Only if all three crosspostings succeed, the exit
-status is 0.
+=item RFC0821 Simple Mail Transfer Protocol.
-=head1 DIAGNOSTICS
+J. Postel. Aug-01-1982. (Format: TXT=124482 bytes) (Obsoletes RFC0788 )
+(Obsoleted by RFC2821) (Also STD0010) (Status: STANDARD )
-when invoked from command line
+=item RFC0822 Standard for the format of ARPA Internet text messages.
- 0 = successful execution and delivery
- 1 = execution failed
- 2 = cannot deliver to any nntpserver
+D. Crocker. Aug-13-1982. (Format: TXT=109200 bytes) (Obsoletes RFC0733)
+(Obsoleted by RFC2822) (Updated by RFC1123, RFC1138, RFC1148, RFC1327,
+RFC2156) (Also STD0011) (Status: STANDARD)
-when invoked as LMTP server
+=item RFC0977 Network News Transfer Protocol.
- 0 = successful execution
- 1 = execution failed
+B. Kantor, P. Lapsley. Feb-01-1986. (Format: TXT=55062 bytes) (Status:
+PROPOSED STANDARD)
-delivery status is part of the LMTP protocol
+=item RFC1035 Domain names - implementation and specification.
-=head1 STANDARDS
+P.V. Mockapetris. Nov-01-1987. (Format: TXT=125626 bytes) (Obsoletes
+RFC0973, RFC0882, RFC0883) (Updated by RFC1101, RFC1183, RFC1348,
+RFC1876, RFC1982, RFC1995, RFC1996, RFC2065, RFC2136, RFC2181, RFC2137,
+RFC2308, RFC2535, RFC2845) (Also STD0013) (Status: STANDARD)
+
+=item RFC1652 SMTP Service Extension for 8bit-MIMEtransport.
-0821 Simple Mail Transfer Protocol. J. Postel. Aug-01-1982. (Format:
- TXT=124482 bytes) (Obsoletes RFC0788) (Obsoleted by RFC2821) (Also
- STD0010) (Status: STANDARD)
-
-0822 Standard for the format of ARPA Internet text messages. D.
- Crocker. Aug-13-1982. (Format: TXT=109200 bytes) (Obsoletes RFC0733)
- (Obsoleted by RFC2822) (Updated by RFC1123, RFC1138, RFC1148,
- RFC1327, RFC2156) (Also STD0011) (Status: STANDARD)
-
-0977 Network News Transfer Protocol. B. Kantor, P. Lapsley.
- Feb-01-1986. (Format: TXT=55062 bytes) (Status: PROPOSED STANDARD)
-
-1035 Domain names - implementation and specification. P.V.
- Mockapetris. Nov-01-1987. (Format: TXT=125626 bytes) (Obsoletes
- RFC0973, RFC0882, RFC0883) (Updated by RFC1101, RFC1183, RFC1348,
- RFC1876, RFC1982, RFC1995, RFC1996, RFC2065, RFC2136, RFC2181,
- RFC2137, RFC2308, RFC2535, RFC2845) (Also STD0013) (Status: STANDARD)
-
-1652 SMTP Service Extension for 8bit-MIMEtransport. J. Klensin, N.
- Freed, M. Rose, E. Stefferud, D. Crocker. July 1994. (Format:
- TXT=11842 bytes) (Obsoletes RFC1426) (Status: DRAFT STANDARD)
-
-1854 SMTP Service Extension for Command Pipelining. N. Freed. October
- 1995. (Format: TXT=14097 bytes) (Obsoleted by RFC2197) (Status:
- PROPOSED STANDARD)
-
-1893 Enhanced Mail System Status Codes. G. Vaudreuil. January 1996.
- (Format: TXT=28218 bytes) (Status: PROPOSED STANDARD)
-
-1894 An Extensible Message Format for Delivery Status Notifications.
- K. Moore, G. Vaudreuil. January 1996. (Format: TXT=77462 bytes)
- (Updated by RFC2852) (Status: PROPOSED STANDARD)
-
-2034 SMTP Service Extension for Returning Enhanced Error Codes. N.
- Freed. October 1996. (Format: TXT=10460 bytes) (Status: PROPOSED
- STANDARD)
-
-2606 Reserved Top Level DNS Names. D. Eastlake, A. Panitz. June 1999.
- (Format: TXT=8008 bytes) (Also BCP0032) (Status: BEST CURRENT
- PRACTICE)
-
-2821 Simple Mail Transfer Protocol. J. Klensin, Editor. April 2001.
- (Format: TXT=192504 bytes) (Obsoletes RFC0821, RFC0974, RFC1869)
- (Status: PROPOSED STANDARD)
+J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker. July 1994.
+(Format: TXT=11842 bytes) (Obsoletes RFC1426) (Status: DRAFT STANDARD)
-2980 Common NNTP Extensions. S. Barber. October 2000. (Format:
- TXT=57165 bytes) (Status: INFORMATIONAL)
+=item RFC1854 SMTP Service Extension for Command Pipelining.
+
+N. Freed. October 1995. (Format: TXT=14097 bytes) (Obsoleted by RFC2197)
+(Status: PROPOSED STANDARD)
+
+=item RFC1893 Enhanced Mail System Status Codes.
+
+G. Vaudreuil. January 1996. (Format: TXT=28218 bytes) (Status: PROPOSED
+STANDARD)
+
+=item RFC1894 An Extensible Message Format for Delivery Status Notifications.
+
+K. Moore, G. Vaudreuil. January 1996. (Format: TXT=77462 bytes) (Updated
+by RFC2852) (Status: PROPOSED STANDARD)
+
+=item RFC2034 SMTP Service Extension for Returning Enhanced Error Codes.
+
+N. Freed. October 1996. (Format: TXT=10460 bytes) (Status: PROPOSED
+STANDARD)
+
+=item RFC2606 Reserved Top Level DNS Names.
+
+D. Eastlake, A. Panitz. June 1999. (Format: TXT=8008 bytes) (Also
+BCP0032) (Status: BEST CURRENT PRACTICE)
+
+=item RFC2821 Simple Mail Transfer Protocol.
+
+J. Klensin, Editor. April 2001. (Format: TXT=192504 bytes) (Obsoletes RFC0821, RFC0974, RFC1869) (Status: PROPOSED STANDARD)
+
+=item RFC2980 Common NNTP Extensions.
+
+S. Barber. October 2000. (Format: TXT=57165 bytes) (Status:
+INFORMATIONAL)
+
+=back
=head1 AUTHOR
|
