Return to pop5.me CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh

Annotation of 43BSDReno/share/doc/usd/08.mh/pop5.me, revision 1.1

1.1     ! root        1: .\"    This file is automatically generated.  Do not edit!
        !             2: .SC POP 5
        !             3: .NA
        !             4: POP \- POP database of subscribers
        !             5: .SY
        !             6: /usr/spool/pop/POP
        !             7: .DE
        !             8: The POP database has exactly the same format as the \fIBBoards\fR\0(5)
        !             9: database,
        !            10: although many fields are unused.
        !            11: Currently,
        !            12: only four fields are examined:
        !            13: 
        !            14: .nf
        !            15: .ta \w'encrypted password  'u
        !            16: \fIfield\fR    \fIvalue\fR
        !            17: name   the POP subscriber
        !            18: primary file   the maildrop for the POP subscriber
        !            19:        (relative to the POP directory)
        !            20: encrypted password     the POP subscriber's password
        !            21: network address        the remote user allowed to RPOP
        !            22: .re
        !            23: .fi
        !            24: 
        !            25: This is an ASCII file.  Each field within each POP subscriber's entry
        !            26: is separated from the next by a colon.
        !            27: Each POP subscriber is separated from the next by a new-line.
        !            28: If the password field is null, then no password is valid.
        !            29: 
        !            30: To add a new POP subscriber,
        !            31: edit the file adding a line such as
        !            32: 
        !            33: .ti +.5i
        !            34: mrose::mrose:::::::0
        !            35: 
        !            36: Then, use \fIpopwrd\fR to set the password for the POP subscriber.
        !            37: If you wish to allow POP subscribers to access their maildrops without
        !            38: supplying a password (by using privileged ports),
        !            39: fill\-in the network address field, as in:
        !            40: 
        !            41: .ti +.5i
        !            42: mrose::mrose:::mrose@nrtc-isc::::0
        !            43: 
        !            44: which permits \*(lqmrose@nrtc\-isc\*(rq to access the maildrop for the POP
        !            45: subscriber \*(lqmrose\*(rq.
        !            46: Under the current implementation,
        !            47: only one network address may be given \fIrpop\fR access to a maildrop for a
        !            48: POP subscriber.
        !            49: 
        !            50: To disable a POP subscriber from \fIreceiving\fR mail,
        !            51: set the primary file name to the empty string.
        !            52: To prevent a POP subscriber from \fIpicking\-up\fR mail,
        !            53: set the encrypted password to \*(lq*\*(rq
        !            54: and set the network address to the empty string.
        !            55: 
        !            56: This file resides in home directory of the login \*(lqpop\*(rq.
        !            57: Because of the encrypted passwords,
        !            58: it can and does have general read permission.
        !            59: .Fi
        !            60: ^/usr/spool/pop/POP~^POP database
        !            61: .Sa
        !            62: bboards(5), pop(8), popaka(8), popd(8), popwrd(8)
        !            63: .Bu
        !            64: A binary indexed file format should be available for fast access.
        !            65: 
        !            66: Appropriate precautions must be taken to lock the file against changes
        !            67: if it is to be edited with a text editor.
        !            68: A \fIvipop\fR program is needed.
        !            69: .En

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.