teapop - a POP3 server daemon
teapop [-d] [-D] [-i] [-s] [-t seconds] [-u] [-v] [-h]
Teapop is a pop3 mail program that allows remote clients to access mail. Teapop's main goal is to be as flexible as possible, but still be secure and fast. The way virtual domains can be handled is somewhat unique for POP3-servers. You no longer have to choose one way to handle all your domains, rather you can configure how each domain will be handled separately.
-v Show version. -d Delete messages the user has read with the RETR com- mand. -D Delete messages the user has read with either the RETR or the TOP command. Only messages that have been fully downloaded with the TOP command will be deleted. -i Ignore the first message if it's UW IMAP's control mes- sage. -s Starts Teapop in the background and makes it listen to port 110. Mostly known as standalone mode. -t seconds Changes the default timeout from 900 seconds to the number of seconds specified. This does only affect the time waiting for a command to be sent, and does not interfere with long downloads for instance. RFC1939 explicity states that this MUST be set to a value of 600 (10 mins) or higher. -u Makes Teapop look for X-UIDL: headers in the mail and if found use it for the UIDL reported to the client. NOTE: This is not for the faint hearted. If you want to use this to save CPU-cycles, make sure you set your MTA to remove X-UIDL: headers on all incoming mail and then add a unique X-UIDL: header. If you don't know what all this mean, this option is NOT for you. -h Syntax help.
/usr/local/etc/teapop.passwd holds information on where teapop can find the password for different users/domains
Much time has been put into trying to make teapop the most flexible POP3-server available. Main Author: Ibrahim 'Teaspoon' Khalifa Some documentation by: Kitty 'Meow-Meow' Morgan Helps & Hints: Magnus '' Stahre
inetd(8), syslogd(8), RFC1939
When running with the dotlock-method of locking a users mailbox, teapop will drop root privs before creating the lockfile. Therefore the user must have write access to the directory the user's mailbox is in. If this isn't feasable, use flock()-method instead. Neither mbox or POP3 handles multiple concurrent sessions well, a worst case scenario could actually involve corrupt mailboxes. Teapop does its' utmost to lock the file from other processes to avoid any problems, but to ensure that no unwanted problems occurs, please make sure you use the same locking method in both teapop and your MTA (sendmail/qmail/postfix/etc).
Teapop drops root privs after a valid user/pass or apop com- mand