but you can still edit settings via conf files i'm guessing right? Hmmm, i might install this.
Mods, sorry if this is off topic for this thred
but you can still edit settings via conf files i'm guessing right? Hmmm, i might install this.
Mods, sorry if this is off topic for this thred
Blindness isn't a disability, it's a gift!
GW Hosting, Your dedicated home on the web!
I've been using my method for blocking spam inside WHMCS for a long time now and not once has an email been blocked in the system from a genuine person. I make regular checks in mail (cPanel) and there are no signs of emails being classed as spam unless it actually is spam.
Spam Assassin works well and will continue to use it.
It's the MSFE (Mail Scanner Front End) that isn't free, mailscanner itself is. Personally, I installed the other apps myself as I needed them, since it takes about 5 minutes each through shell. 20 minutes work to save $80 seemed a good bet to me.
MSFE is well worth paying for, and it comes with installation and configuration of Mailscanner that can be time consuming.
This is an older post, but I thought I'd contribute the answer for others. If you want to enable Spam Assassin filtering on piped mail, you can do something like this. This is for a qmail MTA on a CentOS server:
I use three support departments: info, support, and billing. I allow unregistered users to submit to [email protected]. I 'POP' this address and enable aggressive Spam Assassin filtering on it. For the other addresses, I 'pipe' them using the technique above, but also require the user to be registered if not submitting from the web interface.Code:| /usr/bin/spamassassin | php -q /var/www/vhosts/mydoman.com/httpdocs/whmcs/pipe/pipe.php
Hope this helps.
We use WHMCS for our company and also use the ticketing system built-in. We use Google Apps as our primary mail service, but have the WHMCS running on our Linux Server. We have all of our email going through Postini spam filter first, and we have never once received a piece of spam in our ticketing system, and have never had a legitimate email that should have gotten through get blocked. It's not only good for preventing spam in the ticketing system, but just from preventing spam in general.
<<snipped>>
Just an idea.
In the same page, add the keyword "unsubscribe" to the blocked words tab, i found spam sometimes includes a BS link to unsubscribe, or a line telling you to send an email to [email protected]
I also:
Block "no-reply" and "noreply" in the blocked email addresses.
Now THAT is somthing to include in the wiki^
Spam Assasin has dont the job. Thanks for the easy information.
Professional Web Hosting without Downtime period.
http://www.webhostmelbourne.com
Dewlance Best Web Hosting
Cheap Windows VPS, Reseller & Master Reseller Hosting Provider
Quad Ultra Core Server
I realize this is an old thread but I wanted to post my fix to get it working with Directadmin/Exim and piping to spamassassin.. I simply added the following pipe and it's working perfectly.
the -f means, if for some reason spamd is down, send mail normally to account. the -e means send to another application.Code:"| /usr/bin/spamc -f -e /bin/php -q /home/admin/public_html/pipe/pipe.php"
I'm sure this will work for other applications as well. The quotes on either end are required by directadmin.. but may work without those in your application.
Is there a fix for cpanel ..
Professional Web Hosting without Downtime period.
http://www.webhostmelbourne.com
As far as cpanel goes, i assume exim is your mail server, it should be more or less the same, the path to php and spam assasin will be different but a quick check on your server, or google will tell you all you need to know.
Failing that contact your administration to ask them these paths, they should also have an idea of the correct line to use to forward through spamassasin.
Speaking of ConfigServer Security & Firewall with regards to Box Trapper, here is what Chirpy says about it (as seen in the Check Server Security recommendations):
We always disable Box Trapper and strictly use SpamAssassin.Having boxtrapper enabled can very easily lead to your server being listed in common RBLs and usually has the effect of increasing the overall spam load, not reducing it. You should disable it in WHM > Tweak Settings > BoxTrapper Spam Trap
Rick
██ UBERHOST
██ NEXT GENERATION HOSTING
Personalized uber-support provided around the clock since 2005
Dedicated • VPS • Reseller • Shared • Design • Visit UberHost »
Have you managed to find a solution to this yet. We are receiving emails like that daily. One simple solutiuon for me would be to have a script that looks for a specific word in the email and trashes all others. So instead of looking for ***SPAM*** and trashing those emails, it would look for MYCODE and trasj all emails that do not have MYCODE in the subject line.
We are in the process of building an addon that used AKISMET for spam detection on forms and when they get past spamassassin on email piping. Become a beta tester here:
http://forum.whmcs.com/showthread.ph...eta-Testers%29
So far it's blocking about 18 out of 20 we've received. The others that it's not caught, we've submitted to AKISMET via a "report spam" button we've added to the WHMCS ticketing system.