Gecko [ 122.154.134.11 ]

Name	Size	Permission
AAAREADME	2.7 KB	-rw-r--r--
ADDRESS_CLASS_README	9.33 KB	-rw-r--r--
ADDRESS_REWRITING_README	42.68 KB	-rw-r--r--
ADDRESS_VERIFICATION_README	19.46 KB	-rw-r--r--
BACKSCATTER_README	12.3 KB	-rw-r--r--
BASIC_CONFIGURATION_README	20.73 KB	-rw-r--r--
BUILTIN_FILTER_README	13.94 KB	-rw-r--r--
CDB_README	2.69 KB	-rw-r--r--
CONNECTION_CACHE_README	8.96 KB	-rw-r--r--
CONTENT_INSPECTION_README	3.29 KB	-rw-r--r--
DATABASE_README	13.25 KB	-rw-r--r--
DB_README	6.9 KB	-rw-r--r--
DEBUG_README	17.71 KB	-rw-r--r--
DSN_README	4.33 KB	-rw-r--r--
ETRN_README	11.4 KB	-rw-r--r--
FILTER_README	27.04 KB	-rw-r--r--
INSTALL	32.72 KB	-rw-r--r--
IPV6_README	11.73 KB	-rw-r--r--
LDAP_README	19.83 KB	-rw-r--r--
LINUX_README	1.64 KB	-rw-r--r--
LOCAL_RECIPIENT_README	5.65 KB	-rw-r--r--
MAILDROP_README	5.16 KB	-rw-r--r--
MILTER_README	36.6 KB	-rw-r--r--
MULTI_INSTANCE_README	42.4 KB	-rw-r--r--
MYSQL_README	4.31 KB	-rw-r--r--
NFS_README	4.73 KB	-rw-r--r--
OVERVIEW	18.57 KB	-rw-r--r--
PACKAGE_README	5.45 KB	-rw-r--r--
PCRE_README	2.87 KB	-rw-r--r--
PGSQL_README	4.4 KB	-rw-r--r--
QSHAPE_README	36.13 KB	-rw-r--r--
RELEASE_NOTES	12.37 KB	-rw-r--r--
RESTRICTION_CLASS_README	6.71 KB	-rw-r--r--
SASL_README	23.29 KB	-rw-r--r--
SCHEDULER_README	65.06 KB	-rw-r--r--
SMTPD_ACCESS_README	15.41 KB	-rw-r--r--
SMTPD_POLICY_README	19.37 KB	-rw-r--r--
SMTPD_PROXY_README	10.47 KB	-rw-r--r--
STANDARD_CONFIGURATION_README	25.24 KB	-rw-r--r--
STRESS_README	19.62 KB	-rw-r--r--
TLS_LEGACY_README	51.46 KB	-rw-r--r--
TLS_README	96.1 KB	-rw-r--r--
TUNING_README	23.76 KB	-rw-r--r--
ULTRIX_README	1.96 KB	-rw-r--r--
UUCP_README	5.14 KB	-rw-r--r--
VERP_README	7 KB	-rw-r--r--
VIRTUAL_README	23.29 KB	-rw-r--r--
XCLIENT_README	9.39 KB	-rw-r--r--
XFORWARD_README	8.28 KB	-rw-r--r--

Code Editor : UUCP_README

PPoossttffiixx aanndd UUUUCCPP

-------------------------------------------------------------------------------

UUssiinngg UUUUCCPP oovveerr TTCCPP

Despite a serious lack of sex-appeal, email via UUCP over TCP is a practical
option for sites without permanent Internet connections, and for sites without
a fixed IP address. For first-hand information, see the following guides:

* Jim Seymour's guide for using UUCP over TCP at http://jimsun.LinxNet.com/
    jdp/uucp_over_tcp/index.html,
  * Craig Sanders's guide for SSL-encrypted UUCP over TCP using stunnel at
    http://taz.net.au/postfix/uucp/.

Here's a graphical description of what this document is about:

LAN to                 Internet
    Local network <--->  UUCP   <--- UUCP ---> to UUCP  <---> Internet
                        Gateway                Gateway

And here's the table of contents of this document:

* Setting up a Postfix Internet to UUCP gateway
  * Setting up a Postfix LAN to UUCP gateway

SSeettttiinngg uupp aa PPoossttffiixx IInntteerrnneett ttoo UUUUCCPP ggaatteewwaayy

Here is how to set up a machine that sits on the Internet and that forwards
mail to a LAN that is connected via UUCP. See the LAN to UUCP gateway section
for the other side of the story.

* You need an rrmmaaiill program that extracts the sender address from mail that
    arrives via UUCP, and that feeds the mail into the Postfix sseennddmmaaiill
    command. Most UNIX systems come with an rrmmaaiill utility. If you're in a
    pinch, try the one bundled with the Postfix source code in the aauuxxiilliiaarryy//
    rrmmaaiill directory.

* Define a pipe(8) based mail delivery transport for delivery via UUCP:

/etc/postfix/master.cf:
        uucp      unix  -       n       n       -       -       pipe
          flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail
    ($recipient)

This runs the uuuuxx command to place outgoing mail into the UUCP queue after
    replacing $nexthop by the next-hop hostname (the receiving UUCP host) and
    after replacing $recipient by the recipients. The pipe(8) delivery agent
    executes the uuuuxx command without assistance from the shell, so there are no
    problems with shell meta characters in command-line parameters.

* Specify that mail for example.com, should be delivered via UUCP, to a host
    named uucp-host:

/etc/postfix/transport:
        example.com     uucp:uucp-host
        .example.com    uucp:uucp-host

See the transport(5) manual page for more details.

* Execute the command "ppoossttmmaapp //eettcc//ppoossttffiixx//ttrraannssppoorrtt" whenever you change
    the ttrraannssppoorrtt file.

* Enable ttrraannssppoorrtt table lookups:

/etc/postfix/main.cf:
        transport_maps = hash:/etc/postfix/transport

Specify ddbbmm instead of hhaasshh if your system uses ddbbmm files instead of ddbb
    files. To find out what map types Postfix supports, use the command
    "ppoossttccoonnff --mm".

* Add example.com to the list of domains that your site is willing to relay
    mail for.

/etc/postfix/main.cf:
        relay_domains = example.com ...other relay domains...

See the relay_domains configuration parameter description for details.

* Execute the command "ppoossttffiixx rreellooaadd" to make the changes effective.

SSeettttiinngg uupp aa PPoossttffiixx LLAANN ttoo UUUUCCPP ggaatteewwaayy

Here is how to relay mail from a LAN via UUCP to the Internet. See the Internet
to UUCP gateway section for the other side of the story.

* Specify that all remote mail must be sent via the uuuuccpp mail transport to
    your UUCP gateway host, say, uucp-gateway:

/etc/postfix/main.cf:
        relayhost = uucp-gateway
        default_transport = uucp

Postfix 2.0 and later also allows the following more succinct form:

/etc/postfix/main.cf:
        default_transport = uucp:uucp-gateway

* Define a pipe(8) based message delivery transport for mail delivery via
    UUCP:

/etc/postfix/master.cf:
        uucp      unix  -       n       n       -       -       pipe
          flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail
    ($recipient)

This runs the uuuuxx command to place outgoing mail into the UUCP queue. It
    substitutes the next-hop hostname (uucp-gateway, or whatever you specified)
    and the recipients before executing the command. The uuuuxx command is
    executed without assistance from the shell, so there are no problems with
    shell meta characters.

* Execute the command "ppoossttffiixx rreellooaadd" to make the changes effective.

${this.title}

Code Editor : UUCP_README