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 ISP
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
The PTR check is a lot older than checking for SPF, DKIM, and DMARC.
It's probably a 15+ year old MTA rule and you're getting blocked
before Earthlink would even have the chance to check for
authentication via DKIM or SPF. (And I'm not even sure if they do,
personally.) So yes, DKIM/SPF matter, els
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
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 leas
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 a
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
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
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 belo
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,
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,
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.
>
>
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
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
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**ConnectionsCor
15 matches
Mail list logo
