13 messages in net.sourceforge.lists.courier-users[courier-users] Re: Problem with the ...
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:[courier-users] Re: Problem with the webadmin module.Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Nov 9, 2001 6:21:43 pm
List:net.sourceforge.lists.courier-users

Stefan Hornburg (Racke) writes:

"Sam Varshavchik" <mrs@courier-mta.com> writes:

[...]

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.

Hmm, I assume that webadmin is searching for /etc/courier/hosteddomains/webadmin.

The directory /etc/courier/hosteddomains doesn't exist after the installation.

The cgi automatically creates one, if it doesn't exist.

OK. However, I don't like to give away the ownership on /etc/courier to a different user. But probably I should do that if the user installs the courier-webadmin package.

Any opinions for that ?

See: since webadmin is supposed to edit all the configuration files, then changing the userid on $sysconfdir, and all its files, is going to break webadmin completely.

If you insist on using a different uid for the configuration files, patch webadmin to run under that different uid.

-- Sam