13 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: Problem with ...
FromSent OnAttachments
Guillaume Girard (PS-FR)Nov 7, 2001 9:09 am 
Sam VarshavchikNov 7, 2001 3:15 pm 
Guillaume Girard (PS-FR)Nov 8, 2001 1:11 am 
Sam VarshavchikNov 8, 2001 4:49 am 
Guillaume Girard (PS-FR)Nov 8, 2001 5:52 am 
Stefan Hornburg (Racke)Nov 8, 2001 7:24 am 
Sam VarshavchikNov 8, 2001 4:49 pm 
Sam VarshavchikNov 8, 2001 4:49 pm 
Guillaume Girard (PS-FR)Nov 9, 2001 1:37 am 
Stefan Hornburg (Racke)Nov 9, 2001 6:40 am 
David EhleNov 9, 2001 7:30 am 
Jerry AmundsonNov 9, 2001 2:52 pm 
Sam VarshavchikNov 9, 2001 6:21 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] Re: Problem with the webadmin module.Actions...
From:Guillaume Girard (PS-FR) (guil@trendmicro.fr)
Date:Nov 8, 2001 1:11:40 am
List:net.sourceforge.lists.courier-users

Well, the courierwebadmin cgi is SUID root and the configuration files all belong to the same user and group : root/root.

So I don't think it's this kind of problem.

Guillaume Girard

-----Message d'origine----- De : cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net]De la part de Sam Varshavchik Envoyé : jeudi 8 novembre 2001 00:16 À : cour@lists.sourceforge.net Objet : [courier-users] Re: Problem with the webadmin module.

Guillaume Girard \(PS-FR\) writes:

Hi everybody.

I've just installed Courier on a Debian GNU/Linhux system. I've picked those packages from sid : courier-mta courier-imap courier-authdaemon courier-base courier-webadmin

So to admin Courier via the html interface, I point my browser on : http://myserver/cgi-bin/courierwebadmin (I also touched /etc/courier/webadmin/unsecureok).

It seems to work, at least all the pages display correctly, except one, the first : "Mail server name and local domains". It keeps displaying only "Configuration error: hosteddomains/webadmin: Permission denied". (Of course, the CGI is SUID root...)

Any idea ?

This is probably the end result of a discussion several weeks ago with the Debian porter, regarding him changing the ownership of the configuration files in the port.

File a report in the port bug tracker, and see what happens.