To configure E-mail collection via POP3: Once a user has authenticated, you need to change to the relevant (hashed) directory using the chhashdir program. This is inserted into the standard qmail-popup checkpassword qmail-pop3d chain of events. Thus, if your startup file for tcpserver/qmail-popup reads like this, exec env - PATH=/var/qmail/bin:/usr/local/bin:$PATH tcpserver -u 0 \ 1.2.3.4 pop3 qmail-popup pop3.domain checkpassword \ qmail-pop3d Maildir & you would change it to the following, exec env - PATH=/var/qmail/bin:/var/qmail/hashbin:/usr/local/bin:$PATH \ tcpserver -u 0 1.2.3.4 pop3 qmail-popup pop3.domain \ customcheckpassword setuidgid hash_username chhashdir \ qmail-pop3d Maildir & Note that the UID that chhashdir... runs as is significant, since it must be the owner of the [hashed user] Maildirs. Alternatively, if your customcheckpassword doesn't need to run as root, you can run everything as the hash user, which is more secure and more elegant - such as in this example, where the hash user has UID 191: exec env - PATH=/var/qmail/bin:/var/qmail/hashbin:/usr/local/bin:$PATH \ tcpserver -u 191 1.2.3.4 pop3 qmail-popup pop3.domain \ customcheckpassword chhashdir \ qmail-pop3d Maildir & Note that user authentication is handled separately by the a slot-in replacement for the checkpassword program. Given that the hashing mechanism bypasses normal system users, you've probably installed the hashing mechanism to avoid having normal system users. You therefore need to consider how you'll authenticate your users. Options include using a database or authenticating out of a cdb file - in particular, see the program by Chris Johnson to authenticate a user from a cdb file, or my own program, radcheckpassword, which authenticates using Radius. There are further options too - see the checkpassword section of the qmail home page, www.qmail.org.