Understood, but the salesdroid is who is going to lose the commission/sale. He will be on your side. And for the record even Ameritech will do proper rDNS for frigging home customers that run email servers on their home dsl. It was one phone call to support for me......this companies position on this issue is way out of the norm. WAY out of the norm.
It can't hurt to raise a stink. It is perfectly fine to use a cname, but it doesn't do you any good and leaves you open to errors. Most advise against it. Your might want to try having outgoing server helo the crappy ISP provided name. That way at least when the receiver rDNS's the helo name it will match the dns on the IP address. But you are still up against the people that flag/filter against 'static' and 'pool'. You are going to get rejected and will have to sort that out one at a time with the recipient. How much it will happen to you I can't guess. And put up an SPF record. The cleaner you are the better your chances. Find out what your IP address is going to be. Run it through some of the popular RBL lookups and make sure it isn't dirty. Seriously, I see nothing but pain in your future if you do this. > -----Original Message----- > From: N Parr [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2008 2:28 PM > To: NT System Admin Issues > Subject: RE: Reverse DNS Advice for outbound email > > I wish it was the sales droid, this is one of their head admins telling > me this. And their reason is because their ip assigner upstream > requires it for auditing of their ip space. > > -----Original Message----- > From: Kennedy, Jim [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2008 1:21 PM > To: NT System Admin Issues > Subject: RE: Reverse DNS Advice for outbound email > > You really should have full 'circular' dns if you are going to run an > email server. Is it required by the RFC's? no, it most certainly is > not. > But many people check on it and refuse on it. And that naming scheme > they are using will trigger a LOT of filters out there besides the > missing circular DNS. > > You are the customer. Tell the salesdroid to fix this problem or you > will not change to them. You really need to draw the line on this one, > imho. They do not meet your needs....... > > > > > -----Original Message----- > > From: N Parr [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, May 28, 2008 1:38 PM > > To: NT System Admin Issues > > Subject: Reverse DNS Advice for outbound email > > > > We host our own email and we are changing our primary ISP. Per their > > policy they will not change the Reverse DNS of our static IP to be > > anything other than mortonrb-pool5-static-4.ispxxx.com. I have > > control of my DNS records and can set that as an MX but I'm kind of > > worried about some spam filters having issues with such a long DNS > > name with the word "pool" in it when trying to send mail. Using > their > > > mail server as a smart host is out of the question because if they go > > down our ASA box will automatically fail over to our secondary ISP > and > > > be unable to connect to their down mail server. Do you think using > > this long DNS name will cause issues trying to send outbound email. > > BTW my DNS is hosted with network solutions and they don't support > TXT > > > records so I can't create an SPF. > > Thanks > > Niles > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
