[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Stopping email to a customers domain name
- Subject: Re: [cobalt-users] Stopping email to a customers domain name
- From: flash22@xxxxxxx
- Date: Tue Dec 18 21:44:00 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Wed, 19 Dec 2001, Render-Vue wrote:
> Hi Yah,
>
> I have a customer on the server who has just picked up an expired .com
> domain name pertaining to his business. He currently has the .co.nz account
> set-up on the server and I have added the .com to the GUI DNS (minus an MX
> record) and updated the httpd.conf with the appropriate ServerAlias details
> and everything works hunky dory...
> Problem is that with the domain name he purchased there is still a mass of
> email being addressed to it most of it xxx and spam related...the customer
> doesn't want email use for this domain name only the .co.nz version.
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...
somedomain.com MX 0 we-do-not-accept-email
Note that is it not complete domain name, do it' sundeliverable and will
bounce with a DNS error including that as the domain which wouldn't
resolve, assuming it's being delivered from a halfway decently configured
server...
There are nastier things you can do, but i don't recommend them, they can
cause colleratol damage ;P
PS: You may have to do that behind the GUI, i dunno how well it checks
validity of the MX target these days, it didn't used to at all, and i know
a few folks who created interesting mail loops that way
gsh