Since upgrading some of our daemon's from qpopper 3.1 to qpopper 4.0.4, I've noticed some errors in our pop logs:
Oct 1 00:10:00 cats-po-1.ucsc.edu /usr/local/lib/kpopper[1011]: [ID 702911 local1.notice] Can't write cache file for XXXXX; spool is in mmdf format (where XXXXX was the account name) We didn't used to get this, and we're now getting it a LOT (ie. taking up lots of disk space with the log messages). Further, I'm concerned that not writing the cache file might cause problems down the road (though, I'm also running in Server mode, so I don't know how much the cache file matters). The daemon's that are doing this are our KPOP daemon and our SPOP daemon, both of which are standalone instead of inetd based, and are invoked as: /usr/local/lib/kpopper 1109 -k -K pop -s -S -T120 /usr/local/lib/spopper 995 -s -S -T120 -f /etc/mail/pop/spopper.config This seems a lot to me like a bug in MMDF support.
