=======                                             NOSview [301]
popmail
=======

[N.B.  This is different from the 'pop' command].

The Post Office Protocols (POP2 and POP3), are mail protocols
designed for use in networks containing hosts that are normally
turned off when they are not in use.  In this environment it is
not possible for an SMTP mail server to deliver mail to these
hosts because they are not always available.

The solution to this problem is to designate a mailbox server
that is available to the network at all times and can accept SMTP
mail for other hosts.  When a host comes on-line it uses POP to
access the mail in its mailbox(es) on the mailbox server.

The advantage of using a POP server at an area mail gateway is
that when mail arrives at the gateway for a station that may not
be available, the gateway does not have to waste time trying to
establish a connection with that station.  Instead it accepts the
mail and places it in the addressee's mailbox, just as if the
addressee were a normal user on the gateway system (that is, this
is the same thing that is done with AX.25 BBSs).

As POP2 and POP3 are different and incompatible protocols, both
the POP2 and POP3 servers should be started, to handle all POP
requests from clients.

The POP server requires one data file called /popusers.

The POP protocols are very simple, with minimal error handling.
When an error is encountered, an error message is generated and
then the connection is terminated.  You then have to re-establish
a connection to continue.


_________________________________________________________________
popmail addserver <host> [<seconds>] [<hh:mm-hh:mm>] <protocol>
                                  <mailbox> <username> <password>
_________________________________________________________________
Add <host> as a pop server.  When <seconds> is given, a timer is
started to query the host with that interval for mail.

If not specified no quering to the pop host will be started.  You
have to do that manually with a 'kick'.

When <hh:mm-hh:mm> is given then only in that exact timeframe are
queries to the host made (allowed).

Protocol is either POP2 or POP3, depending on the mail service
the host is providing.  Note: pop2 is superceded by pop3.

<mailbox> is the mailbox name on the host from which mail has to
be picked up.

<username> and <password> are this system's validation parameters
for the host (in /popusers).

Note that on entering this command the host name is looked up.
If non existent an error message is presented.

>> Example:  (all on one line):

   popmail addserver ns9bob 1800 00:00-03:00 pop3 ns9liz ns9liz
                                                        lizpasswd


_________________________________________________________________
popmail dropserver <host>
_________________________________________________________________
Drop host from the list of pop servers to be queried.   All
references to the entry are deleted from the current system.

>> Example:  popmail dropserver ns9bob



_________________________________________________________________
popmail kick
_________________________________________________________________
Kick the local POP client, to get mail from the server.  This
command is needed when no interval is specified with the 'popmail
addserver' command.



_________________________________________________________________
popmail list
_________________________________________________________________
List the current popmail server table.



_________________________________________________________________
popmail quiet [on|off]                               Default: off
_________________________________________________________________
Display or set the POP quiet flag.

This flag determines whether the bell sounds when the system
announces that incoming mail has arrived.  When quiet is set to
'off' you hear the bell.

>> Example:  pop quiet on


_________________________________________________________________
popmail trace [<level>]
_________________________________________________________________
Display or set the trace level of POP sessions.

<level> = 0:  no trace
          1:  serious errors reported
          2:  transient errors reported
          3:  session progress reported

All trace output goes to the session log file.

