Index: ossp-pkg/lmtp2nntp/lmtp2nntp.pod RCS File: /v/ossp/cvs/ossp-pkg/lmtp2nntp/lmtp2nntp.pod,v rcsdiff -q -kk '-r1.42' '-r1.43' -u '/v/ossp/cvs/ossp-pkg/lmtp2nntp/lmtp2nntp.pod,v' 2>/dev/null --- lmtp2nntp.pod 2003/09/25 07:25:27 1.42 +++ lmtp2nntp.pod 2005/04/22 21:14:03 1.43 @@ -70,7 +70,7 @@ The B program is an LMTP service for use in conjunction with an MTA (like Sendmail), providing a reliable real-time mail to news gateway. Input messages get their headers reformatted according to configurable rewrite rules. -The article is then posted or feeded into +The article is then posted or fed into a remote NNTP service (like INN). Delivery must take place immediately or the transaction fails. B relies on the queuing capabilities of the MTA in order to provide a fully reliable service. @@ -127,7 +127,7 @@ is a CIDR style bitmask where /0 means no comparison and enforces a match. Omitting the wholly option defaults to 0.0.0.0/0 and [::] which allows access from any IPv4 or IPv6 host. It is possible to specify both inclusive and exclusive addresses, -the latter have to prefixed with an exclamation mark. In order to pass the ACL +the latter have to be prefixed with an exclamation mark. In order to pass the ACL a client must match any inclusion and not match any exclusion. If you specify exclusions only, a fake inclusion of 0.0.0.0/0 and [::] is appended internally. Any addr can be a name which will be resolved on program launch time. MULTI. @@ -145,7 +145,7 @@ Client connections for outgoing NNTP communication bind to this address. If an address is specified but port is omitted the kernel chooses an ephemeral port. -If you want to specify a port but no address then replace address with all zeroes. +If you want to specify a port but no address then replace address with all zeros. If completely omitted, no assumptions are made which causes the kernel to choose an address based on routing information and an ephemeral port. The addr can be a name which will be resolved on program launch time. SINGLE. @@ -181,7 +181,7 @@ Header rewriting rule. A message received by the LMTP server is split into header and body. The header is further split into a list where the -headernames are uniqe keys to access single- or multivalues. The values +headernames are unique keys to access single- or multivalues. The values are kept in sequence as they appeared in the original message. The gateway processes each rule in priority order. Small I numbers are processed first. The default prioriy is 500. Each rule can modify a @@ -240,7 +240,7 @@ '${msg.header.I}' and again, indexes are supported for multivalued headers. -Inside variables, functions can be access through '%functionname'. +Inside variables, functions can be accessed through '%functionname'. Currently, only %createmessageid is available which creates a value properly suitable for a Message-ID: header. @@ -259,7 +259,7 @@ =item B<--mailfrom|-m> I -"Mail From:" envelope restriction to limit sender addresses. If ommitted, anyone can send +"Mail From:" envelope restriction to limit sender addresses. If omitted, anyone can send mail. The value to be compared includes the angle brackets. Use a PCRE (Perl compatible reguar expression) for I. SINGLE. @@ -287,7 +287,7 @@ =item B<--restrictheader|-r> I Restrict messages by header. Messages with a matching restrictheader are rejected. If -ommitted no restrictions apply. Matching is done before headers are +omitted no restrictions apply. Matching is done before headers are rewritten. Use a PCRE (Perl compatible reguar expression) for I. SINGLE.