[Mimedefang] OT: DNS A records to somedomain.com

[Cormack, Ken]

I've seen the reverse occur.... Where broken remote mail servers, failing to
do successful MX lookups against your domain to find your target mail
server, suddenly start trying to send port 25 connections to the web server
listed in the A record.  The resulting rejections/bouncebacks they receive
lead them to complain that your mail servers are broken.  It can sometimes
take some convincing to tell them "no... It's YOUR server that's broken...
You're trying to send mail to my web server."

Ken


-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com
[mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of Joseph
Brennan
Sent: Wednesday, April 02, 2008 9:09 AM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] OT: DNS A records to somedomain.com



Steffen Kaiser <skmimedefang at smail.inf.fh-bonn-rhein-sieg.de> wrote:

>
> There had been a post a while ago claiming that the amount of SPAM grew
> up dramatically after he/she added an A record for the second level
> domain.

Was this a case where the A record IP address was the mail host?

It's hard to imagine that we'd be getting even more spam if the
A record columbia.edu accepted mail!  But maybe so.

Joseph Brennan
Lead Email Systems Engineer
Columbia University Information Technology



_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang