lohaband.blogg.se

Communigate pro temporary blacklist
Communigate pro temporary blacklist











communigate pro temporary blacklist communigate pro temporary blacklist

I would like to see some discussion about use of cloud though. Talking of spam, I find that the DNS blocklists reject a lot of this, and it is also particularly nice that this technique rejects the message before delivery is accepted - meaning that you don't generate backscatter spam bounce messages for rejected traffic. Been doing this myself with a FreeBSD/Exim/Dovecot setup since before spam was really a problem (and I've since added SA-Exim to the mix for spamassassin integration). Better in fact, since you're in control of your own destiny. Set it up right, and it's as hands-off experience as you'd be used to from the likes of Gmail and Yahoo.

communigate pro temporary blacklist

Dealing with the rest is not complex or expensive, and until only last week, the only on-going costs needed were for an Internet connection and power, I've only recently bought a domain to replace the freebie one I was using from yi.org. The important bit: make sure your server doesn't unwittingly relay spam. Mail stack these days is Postfix and Dovecot on Gentoo Linux. In 2010 that was retired for a little Intel Atom box that's been running my site ever since. Later we had an IBM Netfinity rackmount server with a PIII 550MHz CPU and 5 SCSI HDDs between 18GB and 72GB. First mail server was a Dual Pentium PRO with 3 2GB SCSI HDDs running Slackware and using sendmail. I've been doing it since 2001/2002, and most of it with hand-me-down second-hand equipment. I suppose some people think that running a server is rocket science.













Communigate pro temporary blacklist