Why can't I disable SA on 1 account.

S

sde

Verified User
Joined
Sep 11, 2004
Messages
213
Location
Temecula, CA
I login to the account and click the 'disable' button in the SA menu.

I click save.

I click back.

It still says "SpamAssassin is currently enabled."

Any ideas how to remedy this?
 
next I tried to disable it from the reseller level.

I select the user and modify the account.

I un-check SA and save.

Here is the error:
An error has occurred

Details


Error with system Quotas
setquota: Quota file not found or has wrong format. setquota: Not all specified mountpoints are using quota.
Click to expand...

Even though I got this error, SA is turned off when I go back and view the account.
 
Hi,

I've got the same issue with one client.

I click disable spamassassin, DON'T click on save because it re-enables it then on the spot.

Check back and it remains disabled.

BUT!!!

Now the strange thing comes along.. When I check back a while later (don't know the exact time) spamassassin is re-enabled.

How do I permanently disable SA??

Thanks
 
Just remember that it is enabled/disabled for the entire user account not for just one domain. So if you disable for a domain and then go to another domain and enable it then you just reversed the other disable action.
 
RoRoo said:
I click disable spamassassin, DON'T click on save because it re-enables it then on the spot.

Check back and it remains disabled.

BUT!!!

Now the strange thing comes along.. When I check back a while later (don't know the exact time) spamassassin is re-enabled.
Click to expand...
Just a guess, but this would be normal behavior if the SpamAssassin change doesn't happen instantly, but rather is added to the task queue.

What happens if you click do disable, and then DON'T check right back, but do check back later?

Jeff
 
Clicking the Disable button brings you back to the same screen but now shows disabled. So its instantaneous.
 
floyd said:
Just remember that it is enabled/disabled for the entire user account not for just one domain. So if you disable for a domain and then go to another domain and enable it then you just reversed the other disable action.
Click to expand...

The particular user has 1 domain associated with it.
so he has 3 seperate usernames with 3 seperate domains.

No way to disable.......

It seems like there's a task queue running what checks the enabled status and enables it....
 
RoRoo said:
The particular user has 1 domain associated with it.
so he has 3 seperate usernames with 3 seperate domains.

No way to disable.......
Click to expand...

I don't understand the question. I thought I already answered what you are asking. Spamassassin is disabled/enabled on a per username basis.

It seems like there's a task queue running what checks the enabled status and enables it....
Click to expand...

Why does it seem like that? What is your reasoning behind that?
 
floyd said:
I don't understand the question. I thought I already answered what you are asking. Spamassassin is disabled/enabled on a per username basis.

Why does it seem like that? What is your reasoning behind that?
Click to expand...

Floyd,

It's pretty simple actually.

I disable spamassassin from within the user control panel using the disable button.
one or two weeks later my client forwards me his spamassassin blocked email.
I go back to the user control panel and walla!! Spamassassin is enabled.
No user input at all.

Tried to disable it on the reseller level. Spamassassin feature is indeed gone, but mail keeps getting blocked by it.

This must be a bug, because it's a pretty annoying feature.
 
Ok but why does it seem like there is a task queue running? The task queue runs every minute. So if task queue was doing it then you would see it within a minute not weeks later.

Somebody is logging in and enabling it again. Start checking logs and also see when the user_prefs file was changed. Perhaps the user_prefs is being uploaded by the client and they do not even know it.

The user_prefs file should be gone as soon as you disable SpamAssassin.

My point is stop looking at it like DirectAdmin is doing something. A person is doing something somewhere whether they know it or not.
 
Last edited:
floyd said:
Ok but why does it seem like there is a task queue running? The task queue runs every minute. So if task queue was doing it then you would see it within a minute not weeks later.

Somebody is logging in and enabling it again. Start checking logs and also see when the user_prefs file was changed. Perhaps the user_prefs is being uploaded by the client and they do not even know it.

The user_prefs file should be gone as soon as you disable SpamAssassin.

My point is stop looking at it like DirectAdmin is doing something. A person is doing something somewhere whether they know it or not.
Click to expand...

I know for sure that there's something wrong within DA, since the user isn't logging in other than POP3. I've even tested it with my own account.. Same thing is happening.

The task queue was just a hint, as I'm not dug into the whole DA thing. But maybe this would ring a bell with someone else...

as a test, i've disabled spamassassin on my account.. let's see when this changes back
 
If it does get re-enabled first check to see when the user_prefs was created again. Then check all the logs for that time and see who logged in near that time.

Do you have anything in the directadmin custom scripts folder that do thing when other activities are done?

/usr/local/directadmin/scripts/custom

One example but not the only one:
http://help.directadmin.com/item.php?id=117
 
floyd said:
If it does get re-enabled first check to see when the user_prefs was created again. Then check all the logs for that time and see who logged in near that time.

Do you have anything in the directadmin custom scripts folder that do thing when other activities are done?

/usr/local/directadmin/scripts/custom

One example but not the only one:
http://help.directadmin.com/item.php?id=117
Click to expand...
I'll check it.. Thanks..

I've checked the user_create_post.sh:
#!/bin/sh
echo $username >> /usr/local/directadmin/plugins/awstats/hooks/permissions.txt

and the domain_create_post.sh

#!/bin/sh
echo $domain >> /etc/virtual/use_rbl_domains
exit 0;

only other file in that folder is: README
 
and..... it's enabled again..
what files could I definitely check?

edit:
checked several logfiles.. only thing that ran was the datasq tally....
 
Last edited:
I don't know what that time means. Is that between the time you disabled spamassassin and the time you saw enabled again?
 
floyd said:
I don't know what that time means. Is that between the time you disabled spamassassin and the time you saw enabled again?
Click to expand...

You asked at what time it got created..

The time between is... 10 minutes
 
You must log in or register to reply here.
Back
Top