Re: [cobalt-users] Stopping email to a customers domain name

[flash22@xxxxxxx]

On Wed, 19 Dec 2001, Jeff Lasman wrote:

> flash22@xxxxxxx wrote:
> 
> > You can deflect some of it by actully having an MX, that is unresolvable,
> > that will bause it to bounce before connecting to the mail server, tho it
> > won't stop the stupid mass mailer programs as half of them don't bother to
> > check for MX records...
> 
> Having an MX that doesn't resolve is definitely a good way to get your
> IP#s blocked by reputable ISPs.

Hmm, I'm curious what reputable ISP are still trying to send email to a
domain that hasn't been registered for monets...:P

I Did point out there were side effects to doing that, and i certainly
wouldn't recomment it as a long term configuration, but it does send a
clear message back that mail is not wanted for that domain, there is no
requirement that a particular domain accept email if it doesn't send any.

I am curious who would blacklist a domain for not accepting email, and how
they would notice it unless they were sending it unsolicited email?

I mean, if it's not running any mail services, there isn't anything to
bounce, no users can opt-in to anything, so , where is any legitimite
email going to *come* from ?

Granted, the domain whois data had better point someplace appropriate ;P

[Jeff's note about this possibly wandering off the thread of the list
noted , so i wont' follow this too far, but 2 people have mentioned being
'listed' , the only place i can think of that might do such is
rfc-ignorant.org, and i really don't think they would have cause for it]

gsh