I verified that SELinux was not enabled. Was pretty sure this wasn't the case but it never hurts to double-check.
HTTPD error logs show the following: [Mon Aug 15 13:12:56 2005] [error] [client 10.10.10.52] <h2>Error: could not change to directory </h2>, referer: http://mail.wiredrepublik.com/qmailadmin/index.cgi/com/adddotqmail?atype=forward&user=postmaster&dom=wiredrepublik.com&time=1124129554&; [Mon Aug 15 13:12:56 2005] [error] [client 10.10.10.52] Error. Domain was not found in the assign file, referer: http://mail.wiredrepublik.com/qmailadmin/index.cgi/com/adddotqmail?atype=forward&user=postmaster&dom=wiredrepublik.com&time=1124129554&; I am a total newbie to Qmail toaster, but doesn't that error smack of something wrong with my use of virtual domains? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mon 8/15/2005 12:08 PM To: [email protected] Subject: Re: [qmailtoaster] QMail Admin - Error: could not change to directory > Experiencing the following symptoms in QmailAdmin: > > When adding/modifying an item, upon submitting the change I am bounced > to the the QmailAdmin logon page with the following error at the top > of the > page: Error: could not change to directory. > > I have made some minor cosmetic changes to the html files that > QmailAdmin uses. Upon finding the error I restored the originals, but > am still seeing the error. I am embarrassed to admit that it is > entirely possible that at some point I mistakenly modified the > original files instead of my working copies. > > Anyone seen this behavior? > > Would it be possible for someone to send me a .zip of the originals? > or am I going down the wrong path? > > Any assistance would be very much appreciated. > > BTW: This is a new install of of Qmail Toaster 1.2 stable on Fedora > Core 4. > > > ---------------------------------------------------------------------- > ---------- > > ROBERT ECKDALE > P.O. Box 1283 > Madison, WI 53701-1283 > LOCATE > > > [EMAIL PROTECTED] > CONTACT > Hi Robert, Check to see if you have SELinux enabled. If so, to disable selinux edit /etc/selinux/config and set SELINUX=disabled. Reboot and it should work. If that isn't the problem, what do your httpd logs show? Regards, Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
