Change Details

Google has announced [[ https://support.google.com/mail/answer/81126 | new requirements ]] for sending email to gmail accounts effective 2024-02-01. This is a tracking task to review what (if anything) is required for GitLab to be compliant. === Requirements for all senders === * [x] Set up SPF or DKIM email authentication for your domain. * [x] Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. * [x] Use a TLS connection for transmitting email. * [ ] Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher. * [x] Format messages according to the Internet Message Format standard (RFC 5322). * [x] Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery. * [x] If you regularly forward email, including using mailing lists or inbound gateways, add ARC headers to outgoing email. === Requirements for high-volume senders === I don’t have data on this atm but I would not be surprised if we’re over the 5k emails per day threshold. * [x] Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none. * [x] For direct mail, the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain. This is required to pass DMARC alignment. * [x] Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body.

Google has announced [[ https://support.google.com/mail/answer/81126 | new requirements ]] for sending email to gmail accounts effective 2024-02-01. This is a tracking task to review what (if anything) is required for GitLab to be compliant. === Requirements for all senders === * [x] Set up SPF or DKIM email authentication for your domain. * [x] Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. * [x] Use a TLS connection for transmitting email. * [x] Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher. * [x] Format messages according to the Internet Message Format standard (RFC 5322). * [x] Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery. * [x] If you regularly forward email, including using mailing lists or inbound gateways, add ARC headers to outgoing email. === Requirements for high-volume senders === I don’t have data on this atm but I would not be surprised if we’re over the 5k emails per day threshold. * [x] Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none. * [x] For direct mail, the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain. This is required to pass DMARC alignment. * [x] Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body.

Google has announced [[ https://support.google.com/mail/answer/81126 | new requirements ]] for sending email to gmail accounts effective 2024-02-01. This is a tracking task to review what (if anything) is required for GitLab to be compliant. === Requirements for all senders === * [x] Set up SPF or DKIM email authentication for your domain. * [x] Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. * [x] Use a TLS connection for transmitting email. * [ * [x] Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher. * [x] Format messages according to the Internet Message Format standard (RFC 5322). * [x] Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery. * [x] If you regularly forward email, including using mailing lists or inbound gateways, add ARC headers to outgoing email. === Requirements for high-volume senders === I don’t have data on this atm but I would not be surprised if we’re over the 5k emails per day threshold. * [x] Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none. * [x] For direct mail, the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain. This is required to pass DMARC alignment. * [x] Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body.