|
|
|
Posted on 20 Apr 2006 06:59 AM |
The dspam appication is not working. It was working until yesterday when I added a new mailbox. I went into dspam to run aliases and although it said it ran, none of my email that I'm getting has any of the dspam info in it. I have not used it in a while so I'm at a loss as to why it won't work now. I noticed that a few of the tabs were returning the contents of the script instead of running and my history is missing.
|
|
|
|
|
|
Posted on 20 Apr 2006 11:48 AM |
Matthew,
I grabbed this from your history,
rm matthewaxsom.com
mv matthewaxsom-old.com. matthewaxsom.com
cd /var/www/cgi-bin
ls
cd dspam
ls -al
mv configure.pl configure.cgi
cd admins
mv configure.cgi configure.pl
more default.prefs
ls -al
more admins
vi admins
ls -al
cd ..
ls
ls -al
chmod -R a+rw dspam/
cd dspam
ls
ls -al
vi admins
cd dspam
ls
ls -al
chmod g-w *
ls -al
chmod o-w *
ls -al
perl dspam.cgi
It appears you have been making changes to some dspam config files. You can uninstall and reinstall dspam from the control panel to recover any errors you may have made.
|
|
|
Matthew E. Axsom
(customer)
|
|
|
Posted on 20 Apr 2006 06:29 PM |
I'm not sure how to reply to this. On the one hand you did the
obvious thing and check my bash history file. On the other you didn't
bother to see if any of the change actually amounted to anything. As
you can see by the trail, I reversed every change I made to the dspam
directory. The only reason I tinkered with it was it didnt' work. The
time stap on the bash history should bare that out if you compare it
w/the web access logs.
So if we're done sluthing on stuff that doesn't apply, perhaps we can
get back to the issue of dspam not working. In general it has never
worked correctly since I started hosting w/eapps, but it did it's job
by tagging spam so I didn't complain. I don't want to re-install if I
don't have to since I'll loose all the info I had build up in the
history. I have not touched dspam in quite a number of months. Given
the trouble I've had w/my account since the eapps move, I'd be really
shocked if it stopped working at the UI level after the move.
I'd appreciate you looking a little deeper at the issue than just by
bash history file and having me reinstall. That's like telling a
windows user to reboot in order to solve a problem. It'll keep them
busy and perhaps it'll just "go away". I'd actually like to to figure
out what the problem is.
-Matt
On Apr 20, 2006, at 12:48 PM, Emeka Asika wrote:
|
|
|
|
|
|
Posted on 20 Apr 2006 07:49 PM |
Mr. Axsom,
Once you have made any configuration change to any software that we provide and support free of charge then we can no longer support that application for you. This is our standard policy and we use this policy for many good reasons.
We can understand that you want to figure out why it doesn't work. However if you want to do that you will have to continue in that direction without support on this particular installation.
If you would like to uninstall and re-install a fresh copy from the CP and that install does not work without any changes be made to the configuration then we are most happy to support and help resolve the issue for you.
Thank you for you understanding in this matter.
Thank you;
eApps Support
|
|
|
|
|
|
Posted on 22 Apr 2006 11:57 AM |
I don't think I'm being really clear on this.. The software DIDN'T work to start with. It's never worked correctly since day 1. The only reason I fiddled with permissions was to try and get it to work. From my point of view you broke what was minimally working so it's up to you to fix it. All I did was fiddle w/permissions and the contents of 1 file in order to attempt to get it to work.
At any rate, I'll install and admin my own copy of dspam since I can't really rely on you help or technical know how.
|
|
|
|
|
|
Posted on 22 Apr 2006 12:12 PM |
Mr. Axsom,
We understand what you are saying. If some software that is installed by our CP does not work properly just contact us right away before making any changes to it how ever small they may be.
We will gladly correct the issue for you at that time.
Thank you
eApps Support
|
|
|
|
|
|
Posted on 22 Apr 2006 02:50 PM |
One question that you can answer that'll help me complete my own dspam install is if the install of dspam that you install is set up as a local delivery agent w/sendmail or via procmail or something else?
|
|
|
|
|
|
Posted on 22 Apr 2006 03:27 PM |
Hi,
Your MTA is Sendmail.
/usr/sbin/sendmail
Thank you
eApps Support
|
|
|
|
|
|
Posted on 23 Apr 2006 10:26 AM |
That I was able to figure out and that wasn't the answer I was looking for. I can see now why you don't want to mess with figuring out why modified apps don't work: You know nothing about them other than how to install them from an RPM file.
At any rate I have my own local copy of dspam installed and working. Compiled and installed fine from a tarball. Also upgraded to the latest version of GD so I can see the dspam graphs I'm never been able to see from the RPM install.
For kicks I also figured out why when I reinstalled your copy of dspam from the PRM it didn't work, which was my original question. The answer is 3 fold:
1) The RPM package that installs dspam has the files owned by root. The embedded apache server will NOT run root owned files, hence the actual deployment out of the RPM is incompatable with the system setting, specfically apache.
2) Even when the permission problem is cleaned up on the file, there's a permissions problem with the directory. Again, the defaut dspam install dir is owned by root and once again, your embedded apache server will NOT run things from a root owned dir.
3) Once the permission is OK on the files AND on the directory the remaining problem is the access permissions on the dspam directory itself. It's set to world write and once again your embedded apache server won't run items from a world writable directory.
So I guess what I should do next is replace the embedded apache server with one that actually works.
All in all a very interesting weekend. I learned a number of things:
1) I know more about your system than you do
2) The system is configured for shit
3) My best action when things don't work is to replace the RPM versions w/a "built from source" tarball so I know exactly how it will work.
|
|
|
|
|
|
Posted on 23 Apr 2006 10:27 AM |
Ticket Closed by Customer
Reason Specified: fixed all issues myself w/no help from tech support
|
|
|