Closed titanism closed 3 months ago
PR submitted https://github.com/postalsys/mailauth/pull/61 @andris9
Thanks for bringing this up. I was not aware that PSL was so out of date. The proposed parse-domain module is an ESM and incompatible with mailauth, so I went with the tldts module instead. See cab894b54a3544b33a641f377783db67a43bec0e
can you release new version to npm per #62 ? Thank you Andris. 🙏
After additional investigation, it turned out that while the psl
module was outdated, it handled pay-dartford-crossing-fine.service.gov.uk
correctly. The DMARC record from service.gov.uk
does not apply for pay-dartford-crossing-fine.service.gov.uk
. So, there was nothing wrong from the start.
DMARC lookups are not returning accurate data right now due to the
psl
library being used.An example use case is a
headerFrom
ofnoreply@pay-dartford-crossing-fine.service.gov.uk
.Since it is not returning
service.gov.uk
in thepsl.get('pay-dartford-crossing-fine.service.gov.uk')
invocation, theorgDomain
is not being properly looked up and therefore the DMARC policy returned isnone
, when it should actually be this one:We are submitting a pull request now to swap out
psl
in favor of a different more maintained project.