Teapoplogo General
Man Page


Table of Contents




Is Teapop really free?

Simply put, yes. Teapop is released under a Berkeley style license. Please refer to the source code for the exact license, it's an Open Source license. Do note that Teapop is copyrighted and not public domain.

Even though it's not a requirement, it's appreciated if you notify the maintainer if you are planning to redistribute Teapop. Also, if you do changes to your distribution, contribute. If you do contribute patches to the main distribution, you avoid having to make the changes over and over for every release.

May I submit patches and what happens if I do?

Submitting patches is not only accepted, it's also encouraged. It makes the Open Source world continue to exists, helps others and in some cases someone else might even enhance your patch, which in turn could be to your advantage.

Only contributions that are being released under the same license as the rest of Teapop is being distributed under, a Berkeley style license, will be accepted. All contributions sent in, such as (but not limited to) patches, source code, bugfixes and documentation, will be assumed to have a Berkeley style license, unless otherwise stated.

IRIX Compiling hints

This was reported to us in regards to compilation on IRIX:
  You can list it as compatible with Irix 6.5.x - though I would add a caveat that you shouldn't use GCC on Irix due to byte ordering issues. (GCC pads the wrong buffers) so cavaet should indicate use MIPS Pro compilers or gcc for -o32 compiles.

The configure-script is currently not made to deal with this automatically, so ignoring this may or may not work for you, depending on your environment. If you have any problems running Teapop on IRIX, please first make sure you followed the instruction.

When/when not to use support for virtual domains (vpop)

Most people who compiles Teapop will not disable the support for virtual domains (done at configure time with the flag --disable-vpop) However, there might be times when you actually do want to disable this feature in Teapop. If vpop is disabled, Teapop will not split the username into two strings, username and domain, as it usually does otherwise. This can be useful in more advanced environments where authentication is done against a database where you have a column with the username in the form username@domain.
Note that if you disable vpop, only rows with the magic keywords empty and default, in teapop.passwd, will be used for authentication.

Troubleshooting hints

The first thing to do, when troubleshooting, is to make sure that your syslog daemon is set to log all messages for local0. Teapop will log lots of useful information to it, including, but not limited to, errors in teapop.passwd, permission problems and incorrect username/password.
With a standard syslogd, make sure you have a line like the following in /etc/syslog.conf
local0.debug			/var/log/teapop
Note: It must be tabs, not spaces, separating them
Then create the file /var/log/teapop
touch /var/log/teapop
Now you need to restart syslogd or send a HUP signal to the existing one.

Getting netscape mail to accept @-signs in username

The developers of Netscape decided at some point to filter out @-signs, and all text following it, in usernames. Unfortunately this can cause problems for Teapop users in regards to virtual domains.
Even though this is not a problem specific to Teapop, there are workarounds built-in. As of Teapop v0.25 both the @-sign and the %-sign works as dividers between username and domain. This means that you can just tell your Netscape users to use user%schmoop.com instead of user@schmoop.com as login name and you are set. If you would prefer other characters for divider it's fully configurable at compile-time.
Leon Harris reported that Ken Dowling knew how to get Netscape to act decently. Edit preferences.js and add the following line:
user_pref("mail.allow_at_sign_in_user_name", true);
This is of course hearsay, but some brave souls might want to try it out.

-ERR Mailbox already locked.

If you get this error it might just mean that there is already another session connected to Teapop which is locking the users mailbox. However, it may also mean that Teapop is not able to lock the users mailbox for some other reason. The most common reason is that you have compiled Teapop with dotlocking method for locking mailboxes AND that the user does not have access to write files in the directory the mailbox resides in. To work around this, compile Teapop to use flock() instead: ./configure --enable-flock