Forums
New posts
New posts
Search forums
Market
Domains/Websites Wanted
.com Domain Market
gTLD Domain Market
ccTLD Domain Market
Web3 Domain Market
Third-Level Domain Market
Adult Domain Market
What's New
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Account Upgrade
Premium Members Directory
Log in
Register
What's New
calendar
Search
Search
Search titles only
By:
New posts
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Enjoy unlimited access to all forum features for FREE! Optional upgrade available for extra perks.
Forums
Other
Off Topic
Any New Ideas For Dealing With Spam?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="katherine" data-source="post: 2221324" data-attributes="member: 63835"><p>I prefer to run my own mail servers mainly for <u><strong>privacy</strong></u> reasons, but also for ultimate control. The problem with third party systems is that you depend on their antispam setup, sometimes you can't even whitelist or blacklist senders as you like, which is a shame and the least I would expect from a mail service...</p><p>The basics: deny connections from IP addresses with no PTR (reverse DNS lookup) set, or invalid domains. This alone will field out the majority of spam.</p><p>Occasionally, some legitimate mail originate from poorly configured servers, so I can still whitelist them on a case by case basis.</p><p>Then you can use spamassassin combined with realtime blacklists like Sorbs etc.</p><p>I made a few tweaks as well, for example the 'zombie' machines that keep pounding your mail server are blocked at firewall level.</p><p></p><p>One big benefit is that I have access to the mail server logs, so if I missed an important mail, I can still spot the problem and fix it. I am in control.</p><p></p><p>To get back to the original question, I have often found that analyzing the headers helps determine the best formula to thwart a particular type of spam. Because some persistent spammers use the same scripts, same machines again and again. The only thing that changes is their template, and the IP address because they keep rotating them and switch from one host to another (hello intrust !). But some patterns remain over time.</p><p>I am still getting a bit of spam but less and less, now it's a very small percentage of the hundreds of mails I get per day.</p><p></p><p>One final note:</p><p>Years ago, I rented out a dedi server but I found out that the default configuration was not optimal at all. For example, the PTR/DNS settings I've mentioned were not set. So spamassassin was doing all the work and processing spam that should have been rejected before it even had a chance to enter the mail server. The setup was not optimal and placing a heavy, unnecessary load on the server. What I mean is, whichever server you use is perhaps not fine-tuned as it should be.</p></blockquote><p></p>
[QUOTE="katherine, post: 2221324, member: 63835"] I prefer to run my own mail servers mainly for [U][B]privacy[/B][/U] reasons, but also for ultimate control. The problem with third party systems is that you depend on their antispam setup, sometimes you can't even whitelist or blacklist senders as you like, which is a shame and the least I would expect from a mail service... The basics: deny connections from IP addresses with no PTR (reverse DNS lookup) set, or invalid domains. This alone will field out the majority of spam. Occasionally, some legitimate mail originate from poorly configured servers, so I can still whitelist them on a case by case basis. Then you can use spamassassin combined with realtime blacklists like Sorbs etc. I made a few tweaks as well, for example the 'zombie' machines that keep pounding your mail server are blocked at firewall level. One big benefit is that I have access to the mail server logs, so if I missed an important mail, I can still spot the problem and fix it. I am in control. To get back to the original question, I have often found that analyzing the headers helps determine the best formula to thwart a particular type of spam. Because some persistent spammers use the same scripts, same machines again and again. The only thing that changes is their template, and the IP address because they keep rotating them and switch from one host to another (hello intrust !). But some patterns remain over time. I am still getting a bit of spam but less and less, now it's a very small percentage of the hundreds of mails I get per day. One final note: Years ago, I rented out a dedi server but I found out that the default configuration was not optimal at all. For example, the PTR/DNS settings I've mentioned were not set. So spamassassin was doing all the work and processing spam that should have been rejected before it even had a chance to enter the mail server. The setup was not optimal and placing a heavy, unnecessary load on the server. What I mean is, whichever server you use is perhaps not fine-tuned as it should be. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Other
Off Topic
Any New Ideas For Dealing With Spam?
Top
Bottom