Loading

Organization Migration and Email Best Practices

Fecha de publicación: May 12, 2024
Descripción

Migrations can occur for a variety of reasons. One of the common scenarios is for orgs to migrate to Hyperforce.

Following org migrations, our Mail Transfer Agents (MTAs) have the most intact reputation possible on the Internet. Traffic is phased in slowly to preserve the reputation of the MTAs. Some excessive load or traffic increases may trigger the throttling mechanisms of some ESPs (email service providers) such as Microsoft, Mimecast, or Proofpoint.   A best practice may be to consult with your ESP for advice about their mechanisms for mitigation for your Domain before your migration.


Throttling often manifests as greylisting. In this regard, the ESPs system won’t deliver email on the first try, but pass an SMTP code that causes our MTAs to try to send the email again a few minutes after the initial connection. This can cause a minute or two delay in delivery to the destination server. Greylisting of this nature clears after about 24 hours. Occasionally some ESPs persist this for longer.

Solución

To ensure a seamless transition, organizations should:

  1. Use dynamic mechanisms, such as SPF and DKIM to remove the need to update the access list with pertinent IPs.
    1. It is not recommended to use IP access lists to update access.
  2. Read the knowledge article for IP updates related to your instance.
  3. If using an email relay that tends to depend on IP access lists, also check the supplied IPs in the knowledge article.
  4. Contact your internal email team or ESP if you observe repeated retries of the same email delivery attempt during email log checks. Request either team to address any throttling or greylisting put in place for emails from Salesforce.
    1. Retries are marked as T in the mail event column in the email logs

Note: To complete the form, refer to the Remote Host column in the email logs within Salesforce Setup, specifically looking for public IP interfaces.


Note: Public IP interfaces do not start with 10.xxxx. These are the internal Salesforce IPs initiating the email, not the ones communicating with your or the customer’s ESP or MTA


Mimecast Anti-Spoofing: See this solution specifically for Mimecast IP-based anti-spoofing errors

Número del artículo de conocimiento

001186478

 
Cargando
Salesforce Help | Article