Forum Discussion
554 5.7.1
- 5 years ago
Too much information posted here, so I'll just deal with the pertinent issue:
1. HughesNet has many users on a contracted email server, so DKIM isn't going to be feasible.
2. They have a DMARC policy and a published SPF record in the DNS record, it's just set up to soft fail for anything not in their passable IP spec.
The problem is the soft fail. They know about it. They also know about the TLS issue. As I said, they use a subcontracted email server, so they're at their mercy.
If this is a problem, I recommend getting your own gmail (or other free email account) and use that instead.
apparently hughesnet doesnt do this;
Sign messages with DKIM. Gmail doesn't authenticate messages signed with keys that use fewer than 1024 bits.
Publish a SPF Record.
Publish a DMARC policy.
Too much information posted here, so I'll just deal with the pertinent issue:
1. HughesNet has many users on a contracted email server, so DKIM isn't going to be feasible.
2. They have a DMARC policy and a published SPF record in the DNS record, it's just set up to soft fail for anything not in their passable IP spec.
The problem is the soft fail. They know about it. They also know about the TLS issue. As I said, they use a subcontracted email server, so they're at their mercy.
If this is a problem, I recommend getting your own gmail (or other free email account) and use that instead.
Related Content
- 4 years ago
- 10 months ago