FREE ASSP X (ASSP eXtended - WHM addon with cPanel interface)

[ispro]

What does ASSP X use to get the messages to the spambox? Does it take the messages from the spam collection folder? Does it use spamlover/testmode/ccallspam to collect them? I am curious to know.

I noticed that ASSP X does a lot of work in exim.conf, perhaps you could also address the issue of sub-addresses in exim? I have an enhancement request open here: http://bugzilla.cpanel.net/show_bug.cgi?id=5292

It should be pretty straightforward in exim, the only problem would be writing a frontend that would control the filters for subfolders and such.

ASSP X add directors to Exim and they deliver messages to "spam" directory for each email account of chosen customer if .asspspamboxenable file created at customer's home directory. We also add modified perl functions to Exim.

So it works EXACTLY the same as SpamAssassin Spambox.

[norelidd]

right, but my question was, how to you get the spam messages past ASSP to get to exim in the first place? Because without something like spamlovers or testmode, ASSP will drop the messages before they ever hit exim

[ispro]

right, but my question was, how to you get the spam messages past ASSP to get to exim in the first place? Because without something like spamlovers or testmode, ASSP will drop the messages before they ever hit exim

It has no sense... Because Exim with RBL, etc. filters wil also drop messages even if Spambox enabled.

So in both cases (no ASSP and ASSP) one should either add domain to whitelist (Exim) or to spamlover (ASSP).

One should decide how to enable Spambox: server-wide testmode or domain spamlover.

P.S. Probably we will automatically add domain to all spamlover lists when Spambox enabled. It would be a best for clients who not wish to learn how things work

[Xiron]

Guys, we need your input.

As we have added Spambox we need to decide either put most important filters into Test mode by default or not..

Any filter that is enabled and with Test Mode enabled should end up in Spambox, because they may be false positives.
Those filters that are enabled & Test Mode enabled would be:

Bayesian (if you use it, I always disable it)
DNSBL (they do sometimes get it wrong)
URIBL (this picks up a lot of false positives for simple reason, but can also be affective)
Bomb Regex (can pick up many false positives on simple words, normally this filter should be disabled unless domain suffers lots of spam and client can enable it on their own)
Invalid Helo (can cause a false positive with users sending mail from home bypassing their ISP or mailserver but also catches lots of spam)
Reversed Lookup (if you use it. This filter should be disabled, a lot of genuine domains have no PTR record or even false PTR)
Penalty Box (IP's can end up in Penalty Box for genuine reasons sometimes)


Any filter that is enabled but Test Mode is disabled should not go to Spambox and be immediately rejected because they are genuine spam.
Those filters that are enabled & with Test Mode disabled would be:

BlackDomain
Helo-Blacklist
Spam Address
SPF
SRS
Script Regex (virus, phishing type crap, always spam)
Missing MX/A Record (every domain that sends mail should have an MX record, if not its spam from a false domain)
Forged Local Helo
Forged Local Sender


I always disable Bayesian. It takes too much time and very much effort is needed by admin & clients to make it work, and for all the effort needed its not very effective anyway. Only my opinion, yours most probably differs

Spam Bombs Filters should be enabled, but Spam Bombs Filters option in ASSP X cPanel interface should be initially disabled for all accounts, possibly on account creation.
Clients can enable this if they receive too much spam to a domain. Generally this filter causes far to much false positives and shouldn't be used unless it is needed.

[Xiron]

Errors and bugs:

Spambox:

For me the Spambox does not work. I have enabled the Spambox feature in clients cPanel ASSP X interface but still the spam is delivered to the clients inbox and no Spambox is created. What extra work is needed by me to make this work? A '.asspspamboxenable' file is created in the users /home/ directory when Spambox is enabled and it is deleted when Spambox is disabled, but as I said when enabled Spambox still does not work.

File error:

The error I mentioned before in a previous post still exists.
ASSP Configuration > Relaying > Local Domains: default entry > file:../../../etc/localdomains
This list is unpopulated, error in red at the top reads: File path includes '..' -- access denied

WHM ASSP X interface 'ASSP Mail Processing Options':

If one change is made in your WHM ASSP X interface 'ASSP Mail Processing Options' section ALL filters that were added to Test Mode or enabled/disabled directly in ASSP web interface are removed from Test Mode and enabled when they were disabled!

When I Enable a filter in WHM ASSP X interface 'ASSP Mail Processing Options' section, for example Spam Bombs Filters, it sets them to mode '3' = score only. That's not enable, enable would be 1 = activate.

The section is completely inconsistent and incompatible with the ASSP web interface settings. I think you may be attempting to keep users away from ASSP web interface by adding this section, due to it being large, time consuming and sometimes confusing, but you options simply don't work correctly.

Actually there are so many inaccuracy's and inconsistency's in your 'ASSP Mail Processing Options' section, I wont list them all here, I find it a massive hindrance more than any help. You should fix it and make it consistent or even better just remove it altogether.

[Xiron]

I would like to make some more suggestions for future features if I may:

Have Spambox enabled on cPanel account creation, or an option on WHM ASSP X interface to enable or disable it on cPanel account creation.

Write a script to go through all the Spambox's and delete messages older than 30 days, or an admin configurable time on the WHM ASSP X interface.

Have a daily or weekly reminder of what's in the Spambox emailed to the cPanel user.
The email could contain the 'Date', 'Subject', 'From' and 'To' headers of each message in the Spambox. Perhaps also a reminder of how to retrieve any message from the Spambox. An option to receive this reminder email or not receive it could be added to the cPanel ASSP X interface for each domain that has Spambox enabled.

An option in the 'Software Overview' section to disable automatic update and only run a manual update! As said before your script does a stealth update, changes all settings to your preferred ones and stops ASSP working the way I want it to. Especially stop overwriting files in /files/ directory with your own versions. whitedomains.txt, rbl-service.txt, uribl-service.txt for example. When an install or update runs you should check if these files exist, if they do leave them alone, if not add your versions. Like I said before I have received spam from domains in your whitedomains.txt
Have a link to the 'change log' added when an update is available, admins can check it and then update if they feel the need.

Don't let Cpanel clients have the option to disable / enable certain filters in their cPanel ASSP X interface. For example I don't want my cPanel users being able to disable the SPF filter. The WHM ASSP X interface could have a check-box list of filters clients can disable / enable in their cPanel.
The only filters I would let cPanel clients enable & disable are:
Bayesian (if the filter is enabled)
Penalty Box
RBL
URIBL
Bomb Regex
Basically only the filters that could cause a false positive.
All the others should never be disabled, e.g. SPF, If SPF records are entered correctly any mail that fails SPF must be spam. Others might not agree or want this feature so the check-box list in WHM ASSP X interface could have all filters initially ticked.

Options in WHM ASSP X interface to enable or disable certain filters on cPanel account creation. Again a check-box list in WHM ASSP X interface for the filters to have initially enabled and the ones that should be initially disabled. For example I want Spam Bombs Filters enabled in ASSP but initially disabled for all cPanel clients, it causes far too many false positives. They can enable it themselves later if they suffer a lot of spam to a domain.

Add a feature to the WHM ASSP X interface 'Server Maintaince' section to 'Enable filters for all domains', similar but opposite to the existing 'Disable filters for all domains'. Obviously this option should observe the above suggestion, i.e. don't enable a filter if it is in the don't enable list.

Just abandon the log idea in cPanel ASSP X interface. There is no real need for it in my opinion and only wastes resources, complicates & perhaps confuses the average cPanel user, who don't want spam but also don't want the job of a system administrator.
If you don't want to abandon it have an option in WHM ASSP X interface to disable or hide the link in the cPanel ASSP X interface.

I would still like to see my previous suggestion of a cPanel whitelist addition & removal feature. Rather than clients use the 'Email Interface' have a cPanel ASSP X interface section to make it much easier and less complicated for clients to add and remove from their personal whitelist.

Thank, keep up the good work

[ispro]

A lot of good suggestions! I will definitely review everything and add further features etc.

[ispro]

What about "file:../../../etc/localdomains" you shouldn't be able to edit it via Email Interface! That's why you see error. I feel it is absolutely correct, it is system cPanel file and it is being used by ASSP as local domains list. You shouldn't be able to edit it.

[Radio_Head]

[QUOTE=Xiron;304875]I would like to make some more suggestions for future features if I may:

Have Spambox enabled on cPanel account creation, or an option on WHM ASSP X interface to enable or disable it on cPanel account creation.
Write a script to go through all the Spambox's and delete messages older than 30 days, or an admin configurable time on the WHM ASSP X interface.
>

already available on assp deluxe for cpanel.

>
An option in the 'Software Overview' section to disable automatic update and only run a manual update! As said before your script does a stealth update, changes all settings to your preferred ones and stops ASSP working the way I want it to. Especially stop overwriting files in /files/ directory with your own versions. whitedomains.txt, rbl-service.txt, uribl-service.txt for example.
>

already available on assp deluxe for cpanel.

>
Don't let Cpanel clients have the option to disable / enable certain filters in their cPanel ASSP X interface. For example I don't want my cPanel users being able to disable the SPF filter. The WHM ASSP X interface could have a check-box list of filters clients can disable / enable in their cPanel.
The only filters I would let cPanel clients enable & disable are:
Bayesian (if the filter is enabled)
Penalty Box
RBL
URIBL
Bomb Regex
Basically only the filters that could cause a false positive.
All the others should never be disabled, e.g. SPF, If SPF records are entered correctly any mail that fails SPF must be spam. Others might not agree or want this feature so the check-box list in WHM ASSP X interface could have all filters initially ticked.
>

already available on assp deluxe for cpanel. See the whm/assp screenshot


>
Options in WHM ASSP X interface to enable or disable certain filters on cPanel account creation. Again a check-box list in WHM ASSP X interface for the filters to have initially enabled and the ones that should be initially disabled. For example I want Spam Bombs Filters enabled in ASSP but initially disabled for all cPanel clients, it causes far too many false positives. They can enable it themselves later if they suffer a lot of spam to a domain.
>

already available . Not only .
Suppose you have domain.com with all filters disabled and the clients creates/adds
domain2.com or subdomain.domain.com . Which will be the filters status of domain2.com and subdomain.domain.com ? assp deluxe for cpanel take care of this too (reading and updating values from your default assp filter settings).


>
Add a feature to the WHM ASSP X interface 'Server Maintaince' section to 'Enable filters for all domains', similar but opposite to the existing 'Disable filters for all domains'. Obviously this option should observe the above suggestion, i.e. don't enable a filter if it is in the don't enable list.
>
already available on assp deluxe for cpanel-

>
Just abandon the log idea in cPanel ASSP X interface. There is no real need for it in my opinion and only wastes resources, complicates & perhaps confuses the average cPanel user, who don't want spam but also don't want the job of a system administrator.
If you don't want to abandon it have an option in WHM ASSP X interface to disable or hide the link in the cPanel ASSP X interface.
>

logs are already available on assp deluxe
http://grscripts.com/screenshots.html
Most important logs are delaying and PB logs which shows improtant values not showed also
on assp logs . If you wish you can disable visualization .


Bye

[norelidd]

(since the both of you (ispro and radiohead) seem to be reading this thread, I'll just post it here once)

Great news!!! I talked to the ASSP developer and he agreed to implement a few of my ideas. The most important one, I think, if the use of wildcards in the CC Spam and Send (sendAllSpam) directive.

You don't have to use a single address like spambox@, or mess around with testmode or spamlovers or ANY of that!! what you can do now is either make a duplicate mailbox like bob@serv.com and bob-spam@servo.com, then use USERNAME-spam@DOMAIN in sendAllSpam

OR

with all of the neat trickery you're doing in exim.conf anyways, you could enable subaddressing and set sendAllSpam to USERNAME+spam@DOMAIN, and the spam mail would automatically be filtered into the spam subfolder in the user's inbox.

OR (I think this is the best and easiest one to do)

Just set sendAllSpam to USERNAME@DOMAIN to ensure that all the user's spam gets directly to them, then use exim filters in the user's maildir to pluck out the ones with "X-Assp-Spam: YES" in their headers.

The gui could configure exactly how the exim filters are used: either to let all the spam though for client side filtering, to deliver it to a subfolder, to forward it to another address (like username-spam), or to drop it entirely. It would also control how often the spambox is cleaned out, and what might be neat is instead of deleting the messages, to wrap them up in a compressed archive every X days and store them somewhere in the user's home dir. Then there would be 2 layers of protection against missing false positives. "Archive Spam every X days", and "Delete Oldest Archive every Y days"

This is truly fantastic news. This makes it so much easier than having to poke holes in the filters with spamlovers or turning some of them off entirely with testmode. Granted, you can still do that, but I don't want to

EDIT: ALSO, the both of you need to put in support for Penalty Box Single Message Mode, that would clear out 90% of the false positives problems! Granted Single Message Mode is global and can't be edited by the customer, but I don't want them to. I am vastly more educated in spam control than any of my clients are, so why would I want to let them knock my filters out of balance?

[Radio_Head]

I have read your post on assp mailing list , good idea . Personally , I'll leave spambox@ using piping (note that it does not use test mode , spamlovers or other... my spambox plugin uses sendallspam with piping!) as solution 1 , while I'll use these new features to redirect spam on imap subfolder (solution 2) . IMHO I continue to prefer spambox@ piping (it setup in 1 minute and it only uses sendallspam).

Bye

[norelidd]

The problem with your spambox is that it is per-domain and not per-user. That means that bob@company could read cathy@company's false positives, which is a pretty big breach of privacy.

Using exim filters would let you set it up on a per-user basis, with even more granularity on how each user wants to filter their spam

[Radio_Head]

If someone is able to create a spambox@ account using cpanel is an admin , no ?
Only the admin read email , no privacy problem . And pratically an admin could read any email user , anytime (since he has the passwords) ; in this case the admin should only read a lot of spam .
And how many people on your server are using imap ? Less than 5% on my servers . BTW I will create imap subfolder too (also if it will not be really used such as the SA imap spambox which was never or rarely used on my servers) .

Bye

[norelidd]

Well yes, I can read all of my user's emails. They trust me to run their email, but they don't trust eachother. My users don't care if I admin the server, but they would care if they could read eachother's email

[Radio_Head]

Well yes, I can read all of my user's emails. They trust me to run their email, but they don't trust eachother. My users don't care if I admin the server, but they would care if they could read eachother's email

uhm...some confusion here. I am talking of cpanel admin not server admin , you are a server admin right ? . In other words , if you, server admin activate the spambox plugin using WHM assp deluxe for cpanel , the Cpanel admin opens the assp deluxe web interface, and see the spambox icon an read instructions.... (only if you activate the spambox plugin using WHM assp)

The Cpanel client creates the spambox@domain.com pop3 account , for his domain . He checks the spam on spambox@domain.com . He is the cpanel admin for this domain , and he can read all the email on @domain.com (such as any other email on @domain.com). So I cannot see any privacy problem , if he wants he can read all the emails on @domain.com with or without spambox@domain.com . On spambox@domain.com he will read only spam .

Another big advantage of my piping script is that it pipes only to spambox accounts which really need this service (only clients which have created a spambox@ pop3 account) . So you don't waste your cpu sending the spam for all your users (probably you have users which ignore spam too).
Credits to this idea goes to Remy Gardien.

Again I will create also the imap spambox (also I don't believe in its utility since very few users use imap) .

Bye