Re: Own Public DNS Server

In my limited experience, there is at least a third case.

I have five static IP addresses from Road Runner Business Class in Orange
County, CA. I have all of my DNS records correct, my greeting matches my MX
record, and the only thing I did not have was a PTR record. I kept getting
my mail bounced when sending to domains hosted by GoDaddy and when sending
to AOL users. As soon as I had RR set up my PTR record, mail worked for all
domains.

The same thing happened at a client who had AT&T DSL. It was running for
three years without a PTR, and then one day, mail started getting blocked to
various domains. I had AT&T add a PTR, and presto, it worked again.

I now have an SPF record as well, with a hard-fail at the end. It sometimes
causes problems with web developers who write bad contact forms, ones that
send out with the email address of the person filling out the form, which is
forging the actual sender.

Gregg Hill





"Leythos" <void@xxxxxxxxxxx> wrote in message
news:MPG.22ac881f4fc5bdec989897@xxxxxxxxxxxxxxxxxxxx
In article <908F5769-5E50-484C-B2A3-41EA26BFB743@xxxxxxxxxxxxx>,
cyberdudeiq@xxxxxxxxxxxx says...
From my understanding, the fact that mail doesn't get through to some
servers doesn't mean they categorize it as spam but simply the fact that
there is no "certificate" that indicates its true origin. Maybe I'm wrong
in
my understanding but, my issue is not really spam. Please let me know if
this information matches with your understanding.

Your issue is that your email is being blocked as spam or other.

There are two cases for other people blocking your emails sent to them:

1) Your IP/ISP is on a public block list or is listed as a Dynamic IP

2) You don't have a proper public DNS A/C/MX record for your sending
domain name.

As an example, I could set my server to send from APPLE.COM and it would
mostly be rejected as my sending IP does not resolve to any APPLE.COM
address spaces and certainly I can't create A/C/MX records for that
domain name pointing back to my public IP.

As for IP/ISP on block lists, or you being on a listed Dynamic IP, well,
you need to search the block lists sites and see if your IP shows up on
them.

http://www.webmaster-toolkit.com/spam-block-list-checker.shtml

http://www.spamhaus.org/sbl/

Check your Public DNS info here:
http://www.checkdns.net/quickcheckdomainf.aspx

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)


.

Relevant Pages

  • Re: Own Public DNS Server
    ... servers doesn't mean they categorize it as spam but simply the fact that ... my issue is not really spam. ... You don't have a proper public DNS A/C/MX record for your sending ... As for IP/ISP on block lists, or you being on a listed Dynamic IP, well, ...
    (microsoft.public.windows.server.sbs)
  • Re: Own Public DNS Server
    ... A mismatched PTR record? ... SpamAssassin, for example, will severely punish the spam rating of a message coming from a machine with no PTR record. ... So, in this case, in the scenario laid out (the poster indicated his ISP has *no* rdns for him, and has delegated DNS to the IP, so they *won't* set it up for him either) I can see where an in-house DNS server is the way to go. ... At the same time, proper email headers, proper A/C/MX/Text records will ...
    (microsoft.public.windows.server.sbs)
  • Re: Mail bouce
    ... More than likely your server does not have a PTR record. ... ISP's are using Reverse lookups to reduce SPAM to their servers, ...
    (microsoft.public.exchange.connectivity)
  • Re: Spam issue
    ... Try creating an SPF record in the Public DNS and implementing SenderID ... There's one user in our network who gets a lot of spam since last week. ... seems to be sent out of that users mail account. ...
    (microsoft.public.windows.server.sbs)
  • Re: Emails Getting Marked as Spam
    ... I would make sure the PTR record for the sending host resolves to something, perhaps add SenderID/SPF record if there isn't one already, check some of the decent RBLs on a regular basis if the IPs are listed, keep any eye on mail queues/message tracking/reports to determine if any internal hosts or SMTP VSes are compromised/spamming/relaying... ... It seems since switching to exchange more of our emails seem to be more easily marked as spam by other spam filters for instance. ...
    (microsoft.public.exchange.admin)
Loading