sydneyli
sydneyli
If this generally looks OK to you, I think there are two more things to do before landing this: - [ ] writing the final DB migration script - [...
> @sydneyli is this still WIP? No longer! tis ready
These reports should follow [TLSRPT](https://tools.ietf.org/html/rfc8460).
> I'm having the same issue, anything I can do? @Sh4d1 Could you send more details to `[email protected]` ? Just the domain would suffice for now.
Ah, that's correct-- the form endpoint fetches cached information for the time being instead of conducting a new scan. That shouldn't be too difficult to fix!
Hey @TheNavigat, sorry for my slow response here, and for the lack of context that exists on this bug! There are some refactoring PRs still in the pipeline that might...
Hi @dol! Yes, we're pushing `policy.json` since it also specifies the server hostnames you might expect, in the absence of DNSSEC support. We're being initially conservative about the domains that...
There's a great comment by @jgillula on #88 about what we think re: transitioning to MTA-STS support. > Once they are RFCs and implemented in software, we should support these....
Thanks for the report, @foxcpp! RULES.md has gotten out-of-date, and we need to lint the JSON file for trailing commas.
Thanks for the report! I’ve forwarded the note to our tech ops team and we’ll look into alternative sending services.