|
FAQ |
SAPD FAQ
Copyleft 2002 Milton Maldonado Junior
This FAQ is being updated as needed...
0. With which systems has SAPD been tested?
1. How can I configure SAPD 1.2?
2. What about the maximum userbase size?
3. What other parameters can be changed?
0. With which systems has SAPD been tested?
SAPD 1.2 has been tested so far with Slackware 8.x and 9.0, and did run OK out of the box. Therefore, SAPD should work in any linux distro with Sendmail and GNU-POP3D. Note: In theory SAPD should work with any POP server, but I've received problem reports with VPOP3D.
1. How can I configure SAPD 1.2?
SAPD 1.2 has no provisions for runtime configuration, and the only way to modify its settings is by changing the file sapd.h, and thereafter compiling it with make.
2. What about the maximum userbase size?
SAPD 1.2 supports a maximum of 1,500 users by default. It should be enough to most applications, but this quantity can be changed by altering a line in the file sapd.h. Find the line #define VIRTUSERTABLE_SIZE 1500 and change the number to whatever you want. Be warned, however, that SAPD wasn't tested with so many users and increasing this limit may harm performance.
3. What other parameters are pre-defined?
The parameters defined in the file sapd.h are listed below. Remember to recompile the program after every change by running make. Note that these parameters are not trivial and should be changed only if you are really sure about what they mean.
#define CLIENT_SMTP_PORT 725
#define CLIENT_POP3_PORT 810
These two define the default ports allocated by sapd 1.2. I.e., the ports that sapd listens for incoming calls for SMTP & POP. You won't normally want to change them, unless you have another service assigned to one of these ports.
#define STR_RELAY_DENIED "550 E-mail transmission denied. Contact the sysadmin.\n"
#define STR_NEED_AUTH_POP "550 Read your mailbox before sending e-mail.\n"
You may change the messages sapd returns to the e-mail client when things go wrong.
#define AUTH_ENTRY_LIFESPAN (30 * 60)
Number of seconds that an authentication is still kept as valid; that is, how often the user should perform a successful POP operation in order to be able to send e-mail. Of course, the default indicated above is half an hour.
#define UID_DAEMON 2
#define GID_DAEMON 2
These two define the default userid and groupid assumed by the process. In Slackware the value "2" corresponds to the user & group "daemon". Check if your system has the user and group "daemon" equal to 2.
There are several other parameters defined in sapd.h. I would't mess with them, you've been warned...
Sapd was originally designed to rely solely in the virtusertable file, so for the version 1.2, you'll need to export the userbase to the virtusertable. SAPD 1.3, when released (don't ask me when) should address this issue.
Well, the development of sapd is just a hobby for me, so I can't dedicate too much time to it. I hope I'll have soon SAPD 1.3 which will address most defects from sapd 1.2.