Obviously in an internet provider a web interface to administrate such a service is very important so my users won�t be calling for every littlle change on their confs. So I installed tmda-cgi and compiled with these parameters:
./configure -m system-wide -r pop3://localhost:110 -t /var/www/cgi-bin/tmda.cgi -d /display --virtual-user web -l None
It didn�t authenticate.
You may want to try running ./configure with no arguments and going through the interactive setup to make sure any important settings aren't missed. For example, if you're not using Virtual Users, you probably won't want to specify --virtual-user at all, but this is all taken care of in the interactive mode.
Then I tried:
./configure -m single-user -r pop3://localhost:110 -t /var/www/cgi-bin/tmda.cgi -d /display -l None
And I started to authenticate but got a big error page with permission denied on crypt_key message at the bottom.
Could you send me (or the list) a copy of this big error page?
My crypt_key was using this ownership:
drwxr-xr-x 6 gustavo users 4096 Dec 3 17:41 . drwxr-xr-x 4 gustavo users 4096 Dec 3 13:08 .. -rw-r--r-- 1 gustavo users 1794 Dec 3 12:35 config -rw-r--r-- 1 gustavo users 0 Dec 3 12:35 confirmed -rw------- 1 gustavo users 42 Dec 3 12:29 crypt_key drwxr-xr-x 2 gustavo users 4096 Dec 3 14:56 filters drwxr-xr-x 2 gustavo users 4096 Dec 3 19:09 lists drwx------ 2 gustavo users 4096 Dec 3 18:10 pending drwx------ 2 gustavo users 4096 Dec 3 18:10 responses -rw-r--r-- 1 gustavo users 214 Dec 3 19:12 tmda-cgi.ini
That should be right. TMDA-cgi is doing something wrong and can't see your crypt_key... It's probably not configured right so it can't SUID to your user.
So I changed the ownership to:
drwxr-xr-x 6 web users 4096 Dec 3 17:41 . drwxr-xr-x 4 web users 4096 Dec 3 13:08 .. -rw-r--r-- 1 web users 1794 Dec 3 12:35 config -rw-r--r-- 1 web users 0 Dec 3 12:35 confirmed -rw------- 1 web users 42 Dec 3 12:29 crypt_key drwxr-xr-x 2 web users 4096 Dec 3 14:56 filters drwxr-xr-x 2 web users 4096 Dec 3 19:09 lists drwx------ 2 web users 4096 Dec 3 18:10 pending drwx------ 2 web users 4096 Dec 3 18:10 responses -rw-r--r-- 1 web users 214 Dec 3 19:12 tmda-cgi.ini
Were web is my user for apache. Then tmda-cgi starts working and tmda stops.
TMDA stops working in this case because it can't read the crypt_key since it's owned by not you and has the mode 600.
Okay, then it looks like TMDA-CGI isn't able to SUID to your actual user. You shouldn't have to change anything about your crypt_key at all. The error page you get when you change your ownership back to yourself may be we need to figure out why, but I recommend running ./configure interactively first to make sure no settings have been missed.
-- Jim Ramsay
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
