We have been more than 2 years with Liquidweb. Yes, great machine and datacenter. We were using spamassasin as bundled software on cpanel to fight with spammer, but it was not good enough.
1 year ago we decided to install ASSP Deluxe antispam on our dedicated server, bought from grscripts.com. Its powerful software against the spammer which succesfuly isolate them on a separate folder/email. And our clients happy working on emailing activity.
But in the early of 2009, liquidweb has terminated the software as it's not match with their TOS. Its a weird policy since we installed it 1 year ago.
Honestly, we want to keep you (liquidweb) as our valuable datacenter, but we need solution to keep running a business and stay alive on it. Otherwise we have no choice to migrate our dedicated server (consume a lot of time and energy).
I've heard of Fantastico and have seen it in CPanel with my almost-host (not my personal site...yet) MDDHosting (good hst by the way). However the guy from Aquarius Storage mentioned Installatron. Seems like a good deal for long-term hosts since they offer a lifetime membership...provided the hosts keep their server around for a few years...but other than that what are the pros and conds of each platform? Why do you guys (by which I mean the hosts who frequent this board) use what you do?
I cannot SSH or login into Plesk Admin panel. Once I tried SSH, it says 'connection refused'. Once I tried login into admin panel, it says 'Error: Access for administrator from address 'xxx.xxx.xxx.xxx' is restricted in accordance with IP Access restriction policy currently applied.
Tried restarting the plesk server too. Nothing seems working.
We do little hosting since a couple of years but want to expend our hosting solution.
Actually, we user ASSP and SpamAssasin to block spam but we are looking for a better solution, something who get power and who is easy to user for end user...
I take a look at barracuda but it's very expensive...
we provide a community portal for our users, we run the possibility of setting up a mail from us. Since we have limited experience with anti-spam configuration and we do not like spam bothering our users, looking for suitable "hosted antispam solution.
I would be interested in knowing if anyone has used the data returned from Senderbase.org as part of their antispam evaluation. And if yes, have you found this to be effective compared to traditional IP blacklists like SpamHaus ?
I have noticed that a customer's emails are banned by certain RBL/antispam filters even though they are sent using SMTP-Authentication through a non-banned SMTP server.
It seems that its ISP IP is blacklisted..... Is this normal?
I migrated many domains to a Plesk 12 with lot of email accounts. I need to find a way to mass enable antispam and DR.Web anti virus.
How can I enable to all accounts the antispam with certain parameters Ex. 5 Points and Mark **SPAM** _SCORE_ in the subject and also enable Dr.Web for incoming email.
I tried to understand ASSP by searching in your documentation but nowhere it mentions that when we use a mail client programs. For example:
I install ASSP correctly. I start it. Actually, our spam database is empty. From my understanding, ASSP still let spams and non spams e-mails go through to build its database.
My question is:
Is there a way to know our first 400 or 1000 e-mails are spams in despite to categorize them properly?
How to categorize them on our server when we use Kmail or Outlook to download e-mails from the server?
If I create two folders: spam and nonspam in Outlook or Kmail and move the e-mails to the prosper folders, will it be synchronized with the server automatically?
My host seem to like interfering with spam setting on the server. They had spamassasin installed which works perfectly and i haven't been getting any spam when i enable the software.
All of a sudden all my subscription and a lot of email is rejected and now perfectly legit email is marked as spam.
I fail to understand why use software that reject normal mail.
I have been running ASSP for a long time on a Fedora/Postfix box without a single problem. Recently, however, I have acquired a CentOS/Plesk/Qmail machine and I am having a terrible time getting ASSP to play nicely with qmail.
I am attempting to follow the directions on the assp wiki regarding plesk. I changed qmail to listen on 125 instead of 25 by editing /etc/services. I then restarted everything but it then appeared that mail was going through without authentication. I was successfully able to send mail from an internal address to an external one without a problem, but I think I was able to do so without authenticating myself.
However, when attempting to send mail from an outside address to an internal one, I get a relay denied error message. Obviously ASSP isn't aware of the addresses I have set up on the system.
Also - I attempted to manually run the sh scripts downloaded from the wiki entry, but I kept getting the error message that I couldn't execute binary file, even though I gave the file execute permissions. I even tried adding #!/bin/sh to the top of the file, to no avail....
If anyone has successfully installed assp with Plesk and has authentication and the plesk automation scripts running like they should, please let me know how you did it.
Right now this machine is processing about 3000 emails a day, 90% of which are spam, so I really need to get ASSP installed and running here.
I have a Windows 2003 server running Plesk 8.3, Mailenable with Horde IMP webmail client. I have installed Anti-Spam SMTP Proxy (ASSP) [url] on my server to counter SPAM.
I have configured it with the instructions found here - [url]This configuration works perfectly apart from one issue - whenever I try to send emails from my Horde IMP webmail interface, I get an error saying "unable to set sender to [emailaccount at domain]".
If I deactivate ASSP everything works fine.
I believe this is not an issue with ASSP since no one's complaining on ASSP forums. I posted this issue there and someone suggested it had something to do with how Horde IMP tries to send emails. I posted this to Horde's mailing list too but no one ever answered.
I am interested in ASSP as a anti-spam tool and have heard good things, but I have 1 question I can't seem to find an answer too.
With ASSP is there a way to screen image spam like you can with FuzzyOCR? With ASSP do you even need to scan images at all? Because it waits for the sending server to respond for authentication?
I was running MailScanner / SpamAssasin / FuzzyOCR combo with a couple of chron jobs (to sweep fake bounce email out of the mail que for example) with very effective results, but it took forever to tweak all three to reduce server load. MailScanner was breaking webmail randomly so I have it disabled currently so I get a lot more spam.
I followed the tutorial provided here for installing ASSP but am running into a small problem with exim failing on my vps. I am using ConfigServers csf and lfd and didn't know if there was more modifications needed for ASSP.
my exim panic log shows this:
2007-03-12 00:19:39 socket bind() to port 125 for address 127.0.0.1 failed: Address already in use: daemon abandoned
I think that it may have to be my exim.conf or assp.cfg, but both read the same.
Every week or so, my whitelist in ASSP is getting filled up with @*.de email addresses. Coincidentally, at that same time, I start receiving massive amounts of spam because those addresses are whitelisted.
Has anyone ever had this happen to them? The list of addresses is the same every time it happens, but it really worries me that somehow my whitelist is getting modified without my permission. The assp web interface is disabled (blocked at the firewall) because I update the configuration by just editing the files. SSH access is completely disabled, save for key authentication...So my thoughts are that somehow, an external address is able to modify my whitelist...somehow.
Does anyone have any thoughts or troubleshooting ideas for me?
I installed ASSP Deluxe for cPanel, but one missing feature/config I like, is only allow messages in English, and disregard all other langauges. No I am not reselling so English is fine. How would I change the ASSP config file to only allow English e-mails?
What is ASSP? ASSP is an Anti-Spam SMTP Proxy . The homepage can be found here. ASSP is a lightweight daemon that can filter mail based on various things such as SPF, RBLs, Bayesian word lists, as well as blocking email addresses from getting mail, or having mail filtered.
This tutorial will walk you through getting the admin interface for CPanel setup for ASSP. Currently, a paid user interface can be obtained here (note that I am in no way affiliated with, nor have I tried to use this UI, I am just offering the link to those that might find it useful)
Firstly, the setup: You will need to activate Cpanel PRO (pro.cpanel.net/activate) for your server in order for this to fully work. This activation is currently free. Simply go to the previous mentioned URL and enter your IP address if you have not done so already. Once you have activated CPanel PRO, go into whm->addon modules and check clamav connector, then click on "save". This will install clamav for you to use Once you have done THIS, go to whm->service manager and UNcheck spamd (it is no longer necessary with ASSP), and again click on save/submit. Note that this IS optional, however the purpose of ASSP is to defeat spam before it GETS to SpamAssassin. Once you have done THAT, go into whm -> tweak settings and uncheck SpamAssassin and BoxTrapper mail.
Secondly, the requirements: ASSP needs certain perl modules established To install these, simply login (as root) to your server, and type the following
Code: /scripts/perlinstaller --force Compress::Zlib /scripts/perlinstaller --force Email::Valid /scripts/perlinstaller --force File::ReadBackwards /scripts/perlinstaller --force File::Scan::ClamAV /scripts/perlinstaller --force Mail::SPF::Query /scripts/realperlinstaller --force Mail::SRS /scripts/realperlinstaller --force Tie::RDBM /scripts/realperlinstaller Sys::Syslog /scripts/perlinstaller --force Net::LDAP /scripts/perlinstaller --force Time::HiRes /scripts/perlinstaller --force Tie::DBI Note that the --force is optional, however it will make sure you've got it installed. Do these one at a time as some of these have configurable options to them. One more perl module is needed. Since the later versions of Net::DNS are known to cause issues with RBLs, SPFs and the like, it is advised to use 0.57 . This can be obtained by doing the following:
Code: mkdir /usr/local/assp cd /usr/local/assp mkdir /usr/local/assp/tmp cd /usr/local/assp/tmp wget [url] tar xzf Net-DNS-0.57.tar.gz cd Net-DNS-0.57 perl Makefile.PL make make test make install Do NOT remove the /usr/local/assp/tmp directory as when you update cpanel, it will try to auto update Net::DNS again, so you will want this intact.
Now, let's get with the program here and install ASSP:
Code: cd /usr/local/assp wget [url] unzip -d /usr/local/assp /usr/local/assp/ASSP_1.2.6-Install.zip mv --target-directory=/usr/local/assp /usr/local/assp/ASSP/* mv --target-directory=/usr/local/assp /usr/local/assp/ASSP/.DS_Store rm -rf /usr/local/assp/__MACOSX rm -rf /usr/local/assp/ASSP rm -f ASSP_1.2.6-Install.zip rm -f Win32-quickstart-guide.txt;rm -f freshclam.bat cd /usr/local/assp mkdir pb cd pb touch denysmtp.txt touch exportedextreme.txt touch pbdb.black.db touch pbdb.rbl.db touch pbdb.white.db cd /usr/local/assp mkdir /usr/local/assp/notspam mkdir /usr/local/assp/spam mkdir /usr/local/assp/errors mkdir /usr/local/assp/errors/notspam cd /usr/local/assp wget [url] chmod 755 start wget [url] chmod 755 stop cd /etc/rc.d/init.d wget [url] chmod 755 assp The core of ASSP is now installed. However, the development versions have updated functions to use for users. Of course, this is completely optional, but is recommended completely. This can be done by the following in SSH
Code: cd /usr/local/assp/ mv assp.pl assp.pl_old mv spamdb spamdb.old mv rebuildspamdb.pl rebuildspamdb.pl.old mv repair.pl repair.pl.old mkdir Data mkdir Data/Lists wget [url] wget [url] 000F4555.2/rebuildspamdb.pl wget [url] wget [url] mv assp.css images wget [url] cd Data/Lists wget [url] chmod u+x /usr/local/assp/*.pl Now, let's get it up and running, and configure it, shall we?
Code: cd /usr/local/assp /etc/init.d/assp start You'll see ASSP sending out some messages and then doing nothing. This is ok, and it's the expected response. Now, we need to edit some stuff. Hit ctrl-c (cancel) to shut down ASSP once it's stopped, you'll see the following file in the assp directory - assp.cfg . Edit that with whatever you want for an editor, something like:
Code: nano assp.cfg You want to change a few options immediately just to get it working Look for the lines that are something like:
Code: runAsGroup:= runAsUser:= and change them to be:
Code: runAsGroup:=root runAsUser:=root Then look for the line that is
Code: AsADaemon:= and change it to
Code: AsADaemon:=1 Now, let's change the password just so that we're secure: look for the line that is
Code: webAdminPassword:=nospam4me and change that to
Code: webAdminPassword:=insertrandompasswordhere Now, let's tell ASSP to setup and accept mail for our domains. Look for the line something like
Code: localDomains:= and change that to be
Code: localDomains:=file:/etc/localdomains Almost there, just a couple more changes needed. Look for the line that is something like
Code: smtpDestination:=127.0.0.1:225 and change that to be
Code: smtpDestination:=127.0.0.1:125 (or another port instead of 125, just REMEMBER the port!) and one more change change the line that looks like
Code: listenPort:=125 to
Code: listenPort:=25 Now save and exit the file. If you're using nano/pico, that would be ctrl-x , just make SURE to save the file before you exit! Now, let's get ASSP fired up again
Code: /etc/init.d/assp start let's make sure you have assp starting on system boot:
Code: chkconfig --add assp Let's add a crontab to make sure that ASSP rebuilds the bayesian spam list
Quote:
crontab -e
Code: 10 4 * * * cd /usr/local/assp;/usr/local/assp/rebuildspamdb.pl Occasionally, what I've seen is ASSP will get "hung" on certain things and just kill itself. This fix will work for this, and make sure your ASSP installation is running smoothly
Open up another file on the server, my example will be /bin/asspcheck. In this file, add the following contents
Code: chmod u+x /bin/asspcheck Now, make sure it's called every 60 seconds. Add this to your root crontab
Quote:
crontab -e
Code: * * * * * /bin/asspcheck Now, let's go BACK into WHM and setup the variables needed to get exim to use ASSP In exim configuration editor, click on "advanced editor" Clear out EVERYTHING from all of the existing boxes. Keeping these with data can cause ASSP to not function as it should When you've done that, add the following to the top box:
Code: # assp local_interfaces = 127.0.0.1.125 If you changed this variable to something else
Code: smtpDestination:=127.0.0.1:125 put in the other port, NOT 125, so it would look like 127.0.0.1.whateverporthere
Click on Save Exim will restart and you now have a working installation of assp
Now, let's go to it and work with it a bit, shall we? go to [url], enter the user admin and the password you changed nospam4me to. This will get you logged in and you can tweak the settings as you feel necessary.
ASSP is a great and powerful proxy for any mail server, which blocks using RBLS, whitelists, etc. It is advisable to setup the email interface and let your customers know of this so that you can get them to help you in reporting and addressing spam.
Parts of this howto were taken from this page, however much of that data has been found to be outdated as far as downloads from CVS and the like go, and I've added quite a bit of useful information into it as well.
Go through the ASSP configuration VERY carefully, and ONLY change what you're sure of.
Start with the RBLs, increase the list to 5 and max hits to 2 as suggested.
If you notice problems with this or know how it might be better, hey, feel free to post in here and I'll keep it as updated as possible :)
