Mailing List CGatePro@mail.stalker.com Message #106537
From: Tom Rymes <trymes@rymes.com>
Subject: Re: Blacklist by DNS Name
Date: Fri, 18 Aug 2017 17:12:09 -0400
To: CommuniGate Pro Discussions <CGatePro@mail.stalker.com>
On 08/18/2017 5:01 PM, Tom Rymes wrote:

Perhaps what you are trying to achieve is what we have done using the router (based on advice received on this list, I think). We have these entries in the "Settings:Router" page, and they are designed, if memory serves, to prevent receiving mail from hosts that are using these domains.

*.info = ERROR         ; blacklist .info domains.
*.party = ERROR        ; blacklist .party domains.
*.faith = ERROR        ; blacklist .faith domains.
*.review = ERROR       ; blacklist .review domains.
*.xyz= ERROR           ; blacklist .xyz domains.
*.uno = ERROR          ; blacklist .uno domains.
*.science = ERROR      ; blacklist .science domains.
*.webcam = ERROR       ; blacklist .webcam domains.
*.date = ERROR         ; blacklist .date domains.
*.click = ERROR        ; blacklist .click domains.
*.work = ERROR         ; blacklist .work domains.
*.club = ERROR         ; blacklist .club domains.
*.country = ERROR      ; blacklist .country domains.
*.cricket = ERROR      ; blacklist .cricket domains.
*.link = ERROR         ; blacklist .link domains.
*.mobi = ERROR         ; blacklist .mobi domains.
*.ninja = ERROR        ; blacklist .ninja domains.
*.rocks = ERROR        ; blacklist .rocks domains.
*.space = ERROR        ; blacklist .space domains.
*.top = ERROR          ; blacklist .top domains.
*.website = ERROR      ; blacklist .website domains.

It's been a long time since I implemented that, but I'm pretty sure that's what it does, and that it works as expected.

Can anyone confirm or refute that?

Tom
Replying to my own message here, but I just logged in to our server via telnet and it does seem to work as advertised. I think that the only downside is that the rejection doesn't happen earlier in the process, which would be nice, but this works well.

This is what I got when I manually tried this. I'd suggest that you try it first, then add an entry to the router, then try it again and confirm that the address is now blacklisted.

220 myserver.dom ESMTP CommuniGate Pro 6.1.10 is glad to see you!
EHLO warkesth.faith
501 Unknown command
EHLO warkesth.faith
250-myserver.dom your name is not warkesth.faith
250-DSN
250-SIZE
250-STARTTLS
250-AUTH LOGIN PLAIN CRAM-MD5 DIGEST-MD5
250-ETRN
250-TURN
250-ATRN
250-NO-SOLICITING
250-HELP
250-PIPELINING
250 EHLO
MAIL FROM: <spammer@warkesth.faith>
581 spammer@warkesth.faith address is blacklisted

Hopefully that will be helpful. I implemented this a while back when it became obvious that a huge proportion of our spam was coming from these silly TLDs. Perhaps it's time that I review my junk folder again to add to this list.

Tom

Tom
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster