From the DESIGN-document: Well, the goals themselves are obvious; they're probably the same for most other POP3 servers as well. It's their priority that differs. For popa3d, the goals are: 1. Security (to the extent that is possible with POP3 at all, of course). 2. Reliability (again, as limited by the mailbox format and the protocol). 3. RFC compliance (slightly relaxed to work with real-world POP3 clients). 4. Performance (limited by the more important goals, above). popa3d can be run from inetd, or as a stand-alone server. Note that popa3d only uses flock(2) for locking and may not be safe on NFS or with mail systems that only use lock files.
OS | Architecture | Version |
---|---|---|
NetBSD 10.0 | aarch64 | popa3d-1.0.3.tgz |
NetBSD 10.0 | aarch64eb | popa3d-1.0.3.tgz |
NetBSD 10.0 | alpha | popa3d-1.0.3.tgz |
NetBSD 10.0 | alpha | popa3d-1.0.3.tgz |
NetBSD 10.0 | earmv6hf | popa3d-1.0.3.tgz |
NetBSD 10.0 | earmv6hf | popa3d-1.0.3.tgz |
NetBSD 10.0 | earmv7hf | popa3d-1.0.3.tgz |
NetBSD 10.0 | earmv7hf | popa3d-1.0.3.tgz |
NetBSD 10.0 | i386 | popa3d-1.0.3.tgz |
NetBSD 10.0 | m68k | popa3d-1.0.3.tgz |
NetBSD 10.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 10.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 10.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 10.0 | sparc64 | popa3d-1.0.3.tgz |
NetBSD 10.0 | sparc | popa3d-1.0.3.tgz |
NetBSD 10.0 | vax | popa3d-1.0.3.tgz |
NetBSD 10.0 | vax | popa3d-1.0.3.tgz |
NetBSD 10.0 | x86_64 | popa3d-1.0.3.tgz |
NetBSD 9.0 | aarch64 | popa3d-1.0.3.tgz |
NetBSD 9.0 | alpha | popa3d-1.0.3.tgz |
NetBSD 9.0 | earmv6hf | popa3d-1.0.3.tgz |
NetBSD 9.0 | earmv6hf | popa3d-1.0.3.tgz |
NetBSD 9.0 | earmv7hf | popa3d-1.0.3.tgz |
NetBSD 9.0 | earmv7hf | popa3d-1.0.3.tgz |
NetBSD 9.0 | i386 | popa3d-1.0.3.tgz |
NetBSD 9.0 | m68k | popa3d-1.0.3.tgz |
NetBSD 9.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 9.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 9.0 | powerpc | popa3d-1.0.3.tgz |
NetBSD 9.0 | sparc64 | popa3d-1.0.3.tgz |
NetBSD 9.0 | x86_64 | popa3d-1.0.3.tgz |
NetBSD 9.3 | x86_64 | popa3d-1.0.3.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.