Do away with akpop3d altogether. Use OpenBSD's sendmail and popa3d.
Install OpenVPN on your OpenBSD server and client computer to connect to
OpenBSD's default MTA and POP3 server. This is a much easier and vastly
more flexible solution. I use it all the time and only require's me to
install one single 3rd party application (OpenVPN). By your route, you
have to install akpop3d and configure it and then sasl and configure it
for sending out encrypted email. By your route, you have to watch not
only your OpenBSD vulnerabilities but vulnerabilites for akpop3d and
sasl (or any other 3rd party solution you choose to authenticate your
smtp connection). Do it my way and you only have to watch out for
OpenBSD and OpenVPN vulnerabilities.
J Moore wrote:
... trying to get an errant package (akpop3d) squared away raised the
following question:
Some othe OSs (Linux-Fedora, and FreeBSD) assign ownership of the
/var/mail directory to a group named "mail"; OpenBSD assigns ownership
of this directory to the group "wheel".
Apparently akpop3d needs write access to /var/mail to create a lock file
for the user's mail spool. akpop3d assumes /var/mail is owned by group
"mail", but allows that to be changed at startup with the -g option.
This leads me to a two-part question:
1. Is there an advantage to assigning group ownership of /var/mail to
"wheel", or was this choice simply arbitrary?
2. To get akpop3d running should I change group ownership of /var/mail
to "mail" (rather than giving akpop3d the '-g wheel' option)?
And yes - I did email the port maintainer, but have received no response
in almost a week.
Thnx,
Jay
