If I had to spend hours regularly maintaining it I would probably
migrate it away, too. My setup has been working fine with minimal
intervention for many years.
On 10/08/2014 11:49 PM, Al Hopper wrote:
I used to run my own DNS, email, SPAM filtering etc. Several years ago
I got a Google Enterprise account, which you can associate with your own
domain. Since day one, its been virtually 100% SPAM free. I used to
have to spend hours every couple of months
configuring/re-configuring/tweaking/testing the SPAM filters etc. Since
this account setup, I've never spent a single minute worrying about spam
etc. and it's well worth the $50/user/year for me. If you do a "dig
logical-approach.com <http://logical-approach.com> mx" you'll see the
email from this domain going to Googles email servers. And, if you
look at the DNS servers for the domain (dig logical-approach.com
<http://logical-approach.com> ns), you'll see that I'm running DNS using
Amazon Web Services Route 53 ($0.50/month/domain).
Worth every $0.01 IMHO and highly recommended.
ref: Google Enterprise
<http://www.google.com/enterprise/apps/business/pricing.html> and AWS
Route53 <http://aws.amazon.com/route53/>
Regards,
On Wed, Oct 8, 2014 at 10:35 AM, Robert Moskowitz <[email protected]
<mailto:[email protected]>> wrote:
Something to think about for a wintery night. :)
I am on so many lists that have gotten me so much spam that I need
some help. Even with all that gets bounced away, I can get 500-1000
spams per day.
Part of this whole arm adventure is to see how it performs.
On 10/08/2014 11:21 AM, Gordan Bobic wrote:
On a somewhat tangentially related note, do you really
need to use spamassassin? I find I solved most of my
spam problems by:
1) Nolisting
http://en.wikipedia.org/wiki/__Nolisting
<http://en.wikipedia.org/wiki/Nolisting>
I extend this approach (using iptables) to have primary
_and secondary_ set to -j REJECT TCP connections, tertiary
that accepts and works, and 1-3 after that with -j TARPIT.
Downside - you need multiple IPs.
2) Spamhaus RBLs
3) clamav-milter
This kept me almost completely spam free for years.
Recently, I implemented an additional filter:
4) uri-milter (no package - you'll have
to compile it yourself)
This filters based on URIs in the body of the email,
and I only implemented it due to one particular type
of spam that was getting past the other levels of
filtering.
clamav-milter and uri-milter are both implemented in
C, i.e. they are fast and relatively lightweight,
or at least as lightweight as anything that has to
process the whole body of the email can be.
You may find the above filtering stack is sufficient
for your needs, and it will put a LOT less strain on
your limited hardware than something as bloated and
slow as spamassassin.
Gordan
_________________________________________________
users mailing list
[email protected] <mailto:[email protected]>
http://lists.redsleeve.org/__mailman/listinfo/users
<http://lists.redsleeve.org/mailman/listinfo/users>
_________________________________________________
users mailing list
[email protected] <mailto:[email protected]>
http://lists.redsleeve.org/__mailman/listinfo/users
<http://lists.redsleeve.org/mailman/listinfo/users>
--
Al Hopper
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
