When checking the logs for Salesforce core email you may occasionally notice that some of the entries may unexpectedly have a recipient that starts with "warmup". They may look similar to warmup@sp5.ia5.siterelay.mta.salesforce.com. This happens when the MTA (Mail Transfer Agent) that normally services the traffic has been the target of a migration of many organization that significantly increased the amount of traffic it is handling. To mitigate any potential issues, we spread this new load across many other target Salesforce MTAs in a process known as IP Warmup.
Warmup ensures the best reputation for the MTAs that serve your organization to ensure the highest email deliverability. The warmup process involves relaying email back to the MTA that originally serviced the organization or to other Salesforce MTAs that can absorb the additional load. On the Internet rapid email volume increases cause red flags for mail/spam filters and consequently bad reputations for MTAs. For more information on this process, search your favourite search engine for terms similar to "email warming up and MTA reputation".
Salesforce generally uses a 30 day warmup mechanism that on day one of the new load starts relaying most of any new email load to other Salesforce MTAs to reduce the impact. This avoids a sudden volume spike in email sent from the MTA receiving the newly added traffic. After this the volume of email relayed to other Salesforce MTAs is gradually reduced back to zero over a 30 day period at which point the target MTA is then responsible for sending all the email, and no load balancing is taking place. In the email logs in Setup each email that has been involved in this process will show an extra R and D email event line tracking the receive and send via the warmup MTA. For email log reference see this article.
004397549

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.