When popper is invoked through a Mail User Agent (MUA) client request, such as GET NEW MESSAGES, popper starts to read the user's mail file system (/usr/mail/username) where sendmail has stored the data, and puts this data (if there are messages) in a temporary maildrop file /usr/mail/popper/.username.pop. The contents of this file are transmitted to the remote client using the existing POP3 TCP connection.
Because the directory does not exist, create it as follows:
/usr/mail/popper/
chmod 777 /usr/mail/popperThe popper uses this directory to create and fill the maildrop file. If this directory is not specified or if permissions are incorrect, you will get an error message similar to the following message:
EZZ7605I:Unable to open temporary maildrop '/usr/mail/popper/.username.pop'Also, inside the POP3 session, you will get an error message similar to the following message:
-ERR System error, can't open temporary file, do you own it?
- If the user maildrop file is a symbolic link, it must have an owning UID or GID that matches the EUID or EGID that is assigned to the popper.
- If the user maildrop file is a hard link or the target of a hard link, users that are outside the owner or group of the directory in which the user maildrop file is stored cannot have write access to the directory.
