Re: [mailop] Earthlink trouble with our PTR

[Vladimir Dubrovin via mailop]

Any filtering is an evil and there is not any standard on how to
implement spam filtering. Any spam filter has false positives, and
Earthlink probably  accepts false positives from this rule because it's
effective.

DKIM and DMARC require message DATA to be sent, especially corporate /
smaller ISPs admins do not have domain reputation data and prefer spam
messages to be rejected before DATA, so validating PTRs and HELO/EHLO is
quite common and is not specific to Earthlink.

DKIM/DMARC authenticate mesage content's author and doesn't put any
guarantee on message content. You can send DKIM-signed spam message to
millions of recipients via botnet and it passes DKIM/DMARC checks, but
it fails PTR checks in most cases.

There are a lot of technical things affecting deliverability. With
different mail system you can have different issues because oif this.
Some time ago I've compiled a checklist you can find useful:

https://team.mail.ru/technical-recommendations-for-email-senders/


14.12.2017 17:27, Ryan Prihoda пишет:
>
>
> What about SPF, DMARC, DKIM ? I am sending 250k/day and only Earthlink
> seems to care. How many checks are actually necessary ?
>
> -Ryan
>
> On 12/13/2017 03:32 PM, Vladimir Dubrovin via mailop wrote:
>>
>>
>> Not only Earthlink cares, it's a standard procedure.
>> This validation confirms your IP really belongs to the domain.
>> This is standard validation for PTR everyone does, without this
>> validation you can set PTR to arbitrary domain (e.g. example.com).
>> Not everyone rejects messages based on this check, but it's also an
>> option, see e.g.
>> http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
>>
>>
>> 14.12.2017 0:02, Ryan Prihoda пишет:
>>>
>>> William,
>>>
>>> Yes our PTR is set correctly, but our domain does resolve to a
>>> different IP. Why does only Earthlink care about that ? Seems silly.
>>>
>>> Sincerely,
>>>
>>> *Ryan Prihod**a
>>> *Systems Administrator
>>>
>>>
>>> *dyna**ConnectionsCorp.
>>> *1101 S. Capital of TX Hwy.
>>> Bldg. H, Suite 130
>>> Austin, Texas 78746
>>> rprih...@dynaconnections.com 
>>> www.dynaconnections.com 
>>>
>>>
>>> On 12/13/2017 02:47 PM, W Kern wrote:

 its misleading.

 We saw that a few weeks ago.

 Make sure the FQDN you reverse zone file provides, also resolves
 back to the same IP.

 We were just as confused. The PTR was there, but because of a typo
 it didn't resolve.

 Fixed that and Earthlink was happy.

 Sincerely,

 William Kern

 Pixelgate Networks.


 On 12/13/2017 12:21 PM, Ryan Prihoda wrote:
>
> Hello all,
>
> We are getting errors from one of our servers.
>
> 550 ERROR: No or mismatched reverse DNS (PTR) entries
>
> When, in fact there is only one record for that IP. Can anyone
> from Earthlink look into this for us ?
>
> Sincerely,
>
> *Ryan Prihod**a
> *Systems Administrator
>
>
> *dyna**ConnectionsCorp.
> *1101 S. Capital of TX Hwy.
> Bldg. H, Suite 130
> Austin, Texas 78746
> rprih...@dynaconnections.com 
> www.dynaconnections.com 
>
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



 ___
 mailop mailing list
 mailop@mailop.org
 https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>>
>>>
>>>
>>> ___
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>
>>
>> -- 
>> Vladimir Dubrovin
>> @Mail.Ru
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


-- 
Vladimir Dubrovin
@Mail.Ru

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[t...@pelican.org]

On Thursday, 14 December, 2017 15:35, "Rob McEwen"  said:
 

> I think that the importance of FCrDNS, and of setting FCrDNS up with a
> PTR record ending with the sender's PRIMARY domain name (or at least
> using an important domain - not some throwaway or utility domain - so
> that both identity AND that domain's "good reputation" is properly
> attributed to the IP) -  has received far too little attention over the
> years.
 
Also, it's possibly (at least for old-timers) such a fundamental *host* thing 
that no-one thought to put it down in terms of a *mail* checklist.  Way back 
when, if you were installing mail01.example.com ready for connecting to the 
Internet, you made damn sure "mail01.example.com. IN A 192.0.2.1" and 
"1.2.0.192 IN PTR mail01.example.com." were present and correct, maybe even 
before starting the OS install.  The only incremental for mail was to make sure 
you were HELOing as the same hostname, or at least something under example.com.
 
Especially now that there's a lot of bigger organisations with more separation 
of responsibility, maybe it's more important for the "mail team" to have a 
check-list item that the "OS team" and the "DNS team" have done the right thing 
in what they're providing (or that the request to those teams asks for the 
right thing)...
 
Regards,
Tim.
 ___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Michael Orlitzky]

On 12/14/2017 09:27 AM, Ryan Prihoda wrote:
> 
> What about SPF, DMARC, DKIM ? I am sending 250k/day and only Earthlink
> seems to care.

Out of the box, SpamAssassin will penalize you too:

https://wiki.apache.org/spamassassin/Rules/RDNS_NONE

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Rob McEwen]

On 12/14/2017 10:09 AM, Ryan Prihoda wrote:
What I was saying is FCrDNS /that /important to fail delivery when the 
others are readily available to verify ?


I think that the importance of FCrDNS, and of setting FCrDNS up with a 
PTR record ending with the sender's PRIMARY domain name (or at least 
using an important domain - not some throwaway or utility domain - so 
that both identity AND that domain's "good reputation" is properly 
attributed to the IP) -  has received far too little attention over the 
years.


SPF, DMARC, and DKIM get so much attention - but FCrDNS is at least as 
important! Most likely, those espousing SPF, DMARC, and DKIM probably 
just assume that everyone already knows to do FCrDNS - but there are 
still many mail admins out there who haven't implemented FCrDNS, or 
haven't implemented it optimally.


--
Rob McEwen
 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Ryan Prihoda]

Yes, I have proper SPF DMARC and DKIM set. What I was saying is FCrDNS 
/that /important to fail delivery when the others are readily available 
to verify ? I am not trying to push back , just understand. I'll be 
fixing this issue as soon as we can.


So, what other email authentications methods am I missing? SPF DKIM 
DMARC FCrDNS, anything else I don't know about?


Thanks,

Ryan

On 12/14/2017 08:41 AM, Vick Khera wrote:
On Thu, Dec 14, 2017 at 9:27 AM, Ryan Prihoda 
> 
wrote:



What about SPF, DMARC, DKIM ? I am sending 250k/day and only
Earthlink seems to care. How many checks are actually necessary ?


You should look to implement SPF and DKIM for sure.

As for only earthlink seeming to care, how do you know this? You 
cannot reliably and accurately measure inbox placement. Just because 
they don't block you at the gate doesn't mean you are not being 
penalized for having inconsistent DNS.



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Renaud Allard via mailop]

If you want to be a good neighbour, you should have a restrictive (not
~all) SPF, DMARC, DKIM and a FcRDNS coherent with your HELO. If you have
all that, you should be able to send to anyone (besides hotmail).
Obviously, you should also not be in any major blacklists.

On 12/14/2017 03:27 PM, Ryan Prihoda wrote:
> 
> What about SPF, DMARC, DKIM ? I am sending 250k/day and only Earthlink
> seems to care. How many checks are actually necessary ?
> 
> -Ryan
> 
> On 12/13/2017 03:32 PM, Vladimir Dubrovin via mailop wrote:
>>
>>
>> Not only Earthlink cares, it's a standard procedure.
>> This validation confirms your IP really belongs to the domain.
>> This is standard validation for PTR everyone does, without this
>> validation you can set PTR to arbitrary domain (e.g. example.com). Not
>> everyone rejects messages based on this check, but it's also an
>> option, see e.g.
>> http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
>>
>>
>> 14.12.2017 0:02, Ryan Prihoda пишет:
>>>
>>> William,
>>>
>>> Yes our PTR is set correctly, but our domain does resolve to a
>>> different IP. Why does only Earthlink care about that ? Seems silly.
>>>
>>> Sincerely,
>>>
>>> *Ryan Prihod**a
>>> *Systems Administrator
>>>
>>>
>>> *dyna**ConnectionsCorp.
>>> *1101 S. Capital of TX Hwy.
>>> Bldg. H, Suite 130
>>> Austin, Texas 78746
>>> rprih...@dynaconnections.com 
>>> www.dynaconnections.com 
>>>
>>>
>>> On 12/13/2017 02:47 PM, W Kern wrote:

 its misleading.

 We saw that a few weeks ago.

 Make sure the FQDN you reverse zone file provides, also resolves
 back to the same IP.

 We were just as confused. The PTR was there, but because of a typo
 it didn't resolve.

 Fixed that and Earthlink was happy.

 Sincerely,

 William Kern

 Pixelgate Networks.


 On 12/13/2017 12:21 PM, Ryan Prihoda wrote:
>
> Hello all,
>
> We are getting errors from one of our servers.
>
> 550 ERROR: No or mismatched reverse DNS (PTR) entries
>
> When, in fact there is only one record for that IP. Can anyone from
> Earthlink look into this for us ?
>
> Sincerely,
>
> *Ryan Prihod**a
> *Systems Administrator
>
>
> *dyna**ConnectionsCorp.
> *1101 S. Capital of TX Hwy.
> Bldg. H, Suite 130
> Austin, Texas 78746
> rprih...@dynaconnections.com 
> www.dynaconnections.com 
>
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



 ___
 mailop mailing list
 mailop@mailop.org
 https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>>
>>>
>>>
>>> ___
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>
>>
>> -- 
>> Vladimir Dubrovin
>> @Mail.Ru
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> 
> 
> 
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> 



smime.p7s
Description: S/MIME Cryptographic Signature
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Vick Khera]

On Thu, Dec 14, 2017 at 9:27 AM, Ryan Prihoda 
wrote:

>
> What about SPF, DMARC, DKIM ? I am sending 250k/day and only Earthlink
> seems to care. How many checks are actually necessary ?
>
>
You should look to implement SPF and DKIM for sure.

As for only earthlink seeming to care, how do you know this? You cannot
reliably and accurately measure inbox placement. Just because they don't
block you at the gate doesn't mean you are not being penalized for having
inconsistent DNS.
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Ryan Prihoda]

What about SPF, DMARC, DKIM ? I am sending 250k/day and only Earthlink 
seems to care. How many checks are actually necessary ?


-Ryan

On 12/13/2017 03:32 PM, Vladimir Dubrovin via mailop wrote:



Not only Earthlink cares, it's a standard procedure.
This validation confirms your IP really belongs to the domain.
This is standard validation for PTR everyone does, without this 
validation you can set PTR to arbitrary domain (e.g. example.com). Not 
everyone rejects messages based on this check, but it's also an 
option, see e.g.

http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname


14.12.2017 0:02, Ryan Prihoda пишет:


William,

Yes our PTR is set correctly, but our domain does resolve to a 
different IP. Why does only Earthlink care about that ? Seems silly.


Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 


On 12/13/2017 02:47 PM, W Kern wrote:


its misleading.

We saw that a few weeks ago.

Make sure the FQDN you reverse zone file provides, also resolves 
back to the same IP.


We were just as confused. The PTR was there, but because of a typo 
it didn't resolve.


Fixed that and Earthlink was happy.

Sincerely,

William Kern

Pixelgate Networks.


On 12/13/2017 12:21 PM, Ryan Prihoda wrote:


Hello all,

We are getting errors from one of our servers.

550 ERROR: No or mismatched reverse DNS (PTR) entries

When, in fact there is only one record for that IP. Can anyone from 
Earthlink look into this for us ?


Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop




___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop




___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



--
Vladimir Dubrovin
@Mail.Ru


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Vladimir Dubrovin via mailop]

Not only Earthlink cares, it's a standard procedure.
This validation confirms your IP really belongs to the domain.
This is standard validation for PTR everyone does, without this
validation you can set PTR to arbitrary domain (e.g. example.com). Not
everyone rejects messages based on this check, but it's also an option,
see e.g.
http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname


14.12.2017 0:02, Ryan Prihoda пишет:
>
> William,
>
> Yes our PTR is set correctly, but our domain does resolve to a
> different IP. Why does only Earthlink care about that ? Seems silly.
>
> Sincerely,
>
> *Ryan Prihod**a
> *Systems Administrator
>
>
> *dyna**ConnectionsCorp.
> *1101 S. Capital of TX Hwy.
> Bldg. H, Suite 130
> Austin, Texas 78746
> rprih...@dynaconnections.com 
> www.dynaconnections.com 
>
>
> On 12/13/2017 02:47 PM, W Kern wrote:
>>
>> its misleading.
>>
>> We saw that a few weeks ago.
>>
>> Make sure the FQDN you reverse zone file provides, also resolves back
>> to the same IP.
>>
>> We were just as confused. The PTR was there, but because of a typo it
>> didn't resolve.
>>
>> Fixed that and Earthlink was happy.
>>
>> Sincerely,
>>
>> William Kern
>>
>> Pixelgate Networks.
>>
>>
>> On 12/13/2017 12:21 PM, Ryan Prihoda wrote:
>>>
>>> Hello all,
>>>
>>> We are getting errors from one of our servers.
>>>
>>> 550 ERROR: No or mismatched reverse DNS (PTR) entries
>>>
>>> When, in fact there is only one record for that IP. Can anyone from
>>> Earthlink look into this for us ?
>>>
>>> Sincerely,
>>>
>>> *Ryan Prihod**a
>>> *Systems Administrator
>>>
>>>
>>> *dyna**ConnectionsCorp.
>>> *1101 S. Capital of TX Hwy.
>>> Bldg. H, Suite 130
>>> Austin, Texas 78746
>>> rprih...@dynaconnections.com 
>>> www.dynaconnections.com 
>>>
>>>
>>>
>>> ___
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


-- 
Vladimir Dubrovin
@Mail.Ru

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Ryan Prihoda]

Thanks for the article. I'll see what I can do to resolve this with the 
higher ups.


On 12/13/2017 03:10 PM, Renaud Allard via mailop wrote:

You should have a look at this article:
https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS

On 12/13/2017 10:02 PM, Ryan Prihoda wrote:

William,

Yes our PTR is set correctly, but our domain does resolve to a different
IP. Why does only Earthlink care about that ? Seems silly.

Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 


On 12/13/2017 02:47 PM, W Kern wrote:

its misleading.

We saw that a few weeks ago.

Make sure the FQDN you reverse zone file provides, also resolves back
to the same IP.

We were just as confused. The PTR was there, but because of a typo it
didn't resolve.

Fixed that and Earthlink was happy.

Sincerely,

William Kern

Pixelgate Networks.


On 12/13/2017 12:21 PM, Ryan Prihoda wrote:

Hello all,

We are getting errors from one of our servers.

550 ERROR: No or mismatched reverse DNS (PTR) entries

When, in fact there is only one record for that IP. Can anyone from
Earthlink look into this for us ?

Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop




___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Renaud Allard via mailop]

You should have a look at this article:
https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS

On 12/13/2017 10:02 PM, Ryan Prihoda wrote:
> William,
> 
> Yes our PTR is set correctly, but our domain does resolve to a different
> IP. Why does only Earthlink care about that ? Seems silly.
> 
> Sincerely,
> 
> *Ryan Prihod**a
> *Systems Administrator
> 
> 
> *dyna**ConnectionsCorp.
> *1101 S. Capital of TX Hwy.
> Bldg. H, Suite 130
> Austin, Texas 78746
> rprih...@dynaconnections.com 
> www.dynaconnections.com 
> 
> 
> On 12/13/2017 02:47 PM, W Kern wrote:
>>
>> its misleading.
>>
>> We saw that a few weeks ago.
>>
>> Make sure the FQDN you reverse zone file provides, also resolves back
>> to the same IP.
>>
>> We were just as confused. The PTR was there, but because of a typo it
>> didn't resolve.
>>
>> Fixed that and Earthlink was happy.
>>
>> Sincerely,
>>
>> William Kern
>>
>> Pixelgate Networks.
>>
>>
>> On 12/13/2017 12:21 PM, Ryan Prihoda wrote:
>>>
>>> Hello all,
>>>
>>> We are getting errors from one of our servers.
>>>
>>> 550 ERROR: No or mismatched reverse DNS (PTR) entries
>>>
>>> When, in fact there is only one record for that IP. Can anyone from
>>> Earthlink look into this for us ?
>>>
>>> Sincerely,
>>>
>>> *Ryan Prihod**a
>>> *Systems Administrator
>>>
>>>
>>> *dyna**ConnectionsCorp.
>>> *1101 S. Capital of TX Hwy.
>>> Bldg. H, Suite 130
>>> Austin, Texas 78746
>>> rprih...@dynaconnections.com 
>>> www.dynaconnections.com 
>>>
>>>
>>>
>>> ___
>>> mailop mailing list
>>> mailop@mailop.org
>>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>>
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> 
> 
> 
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> 



smime.p7s
Description: S/MIME Cryptographic Signature
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[Ryan Prihoda]

William,

Yes our PTR is set correctly, but our domain does resolve to a different 
IP. Why does only Earthlink care about that ? Seems silly.


Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 


On 12/13/2017 02:47 PM, W Kern wrote:


its misleading.

We saw that a few weeks ago.

Make sure the FQDN you reverse zone file provides, also resolves back 
to the same IP.


We were just as confused. The PTR was there, but because of a typo it 
didn't resolve.


Fixed that and Earthlink was happy.

Sincerely,

William Kern

Pixelgate Networks.


On 12/13/2017 12:21 PM, Ryan Prihoda wrote:


Hello all,

We are getting errors from one of our servers.

550 ERROR: No or mismatched reverse DNS (PTR) entries

When, in fact there is only one record for that IP. Can anyone from 
Earthlink look into this for us ?


Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop




___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Earthlink trouble with our PTR

[W Kern]

its misleading.

We saw that a few weeks ago.

Make sure the FQDN you reverse zone file provides, also resolves back to 
the same IP.


We were just as confused. The PTR was there, but because of a typo it 
didn't resolve.


Fixed that and Earthlink was happy.

Sincerely,

William Kern

Pixelgate Networks.


On 12/13/2017 12:21 PM, Ryan Prihoda wrote:


Hello all,

We are getting errors from one of our servers.

550 ERROR: No or mismatched reverse DNS (PTR) entries

When, in fact there is only one record for that IP. Can anyone from 
Earthlink look into this for us ?


Sincerely,

*Ryan Prihod**a
*Systems Administrator


*dyna**ConnectionsCorp.
*1101 S. Capital of TX Hwy.
Bldg. H, Suite 130
Austin, Texas 78746
rprih...@dynaconnections.com 
www.dynaconnections.com 



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop