Gmail: Perlu authentikasi: Difference between revisions
From OnnoCenterWiki
Jump to navigationJump to search
Onnowpurbo (talk | contribs) Created page with "Catatan dari Google Emails without authentication often get email blocked or marked as spam to protect recipients from phishing scams. Unauthenticated emails with attachments..." |
Onnowpurbo (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
Emails without authentication often get email blocked or marked as spam to protect recipients from phishing scams. Unauthenticated emails with attachments might get completely rejected for security reasons. | Emails without authentication often get email blocked or marked as spam to protect recipients from phishing scams. Unauthenticated emails with attachments might get completely rejected for security reasons. | ||
To ensure Gmail can authenticate you: | |||
* Send from the same IP address. | |||
* Keep valid reverse DNS records of your IP address that point to your domain. | |||
* Choose the same address in the "From:" header for every message. | |||
Other recommendations | |||
* Sign messages with DKIM. We don't authenticate messages signed with keys that use fewer than 1024 bits. | |||
* Publish a SPF record. | |||
* Publish a DMARC policy. | |||
Latest revision as of 23:10, 3 October 2019
Catatan dari Google
Emails without authentication often get email blocked or marked as spam to protect recipients from phishing scams. Unauthenticated emails with attachments might get completely rejected for security reasons.
To ensure Gmail can authenticate you:
- Send from the same IP address.
- Keep valid reverse DNS records of your IP address that point to your domain.
- Choose the same address in the "From:" header for every message.
Other recommendations
- Sign messages with DKIM. We don't authenticate messages signed with keys that use fewer than 1024 bits.
- Publish a SPF record.
- Publish a DMARC policy.
