On 2014/05/26 09:16, Eric Radman wrote: > The upgrade notes for 5.5 suggest that akpop3d might work as a > replacement for the popa3d that was removed from base. Is there a trick > to using this daemon? akpop3d does not seem to manage locks correctly:
Doesn't entirely surprise me, the port hasn't had much love recently (not even an rc script..) - I don't think it is very widely used so unlikely to have picked up many problem reports. >From reading Solar's recent comments about it, it seems to expect to run as gid mail (with mail spool permissions set accordingly). Last substantive commit to the port (in 2005) was "create/use _akpop3d group rather than the non-existent 'mail' one" so it wouldn't be a huge surprise if this was broken since then. (And if anyone did get it to run, you might be interested in his other comments... http://www.openwall.com/lists/oss-security/2014/05/02/2) Personally I'm using Dovecot. Once configured it's pretty solid, though admittedly setup is more complex than the simple pop3-only daemons. > I ended up using solid-pop3d which was trivial to install. I've been > using nginx from ports to provide SSL access: Using nginx for this may make Reyk sad! (relayd can do SSL offload too).
