As part of the Enhanced Technical Setup with Customer Sender Address, the Scheer IMC project manager clarifies the relevant issues directly at the beginning of the implementation project.
Especially when sending via the Scheer IMC mail server with the customer's sender address, it is important to set an SPF record, and the Scheer IMC project manager will provide all relevant information in this regard.
The Sender Policy Framework (SPF) is an open standard that specifies a technical procedure to prevent the forgery of sender addresses.
More specifically, the current version of SPF (called SPFv1 or SPF Classic) protects the sender address of the envelope used to deliver messages. Furthermorre, SPFv1 allows the owner of a domain to set their policies for sending mail, such as which mail servers they use to send mail from their domain.
This technology requires two sides to work together:
-
The owner of the domain publishes this information in an SPF record in the domain's DNS zone, and when another mail server receives a message claiming to come from that domain.
-
the receiving server can verify that the message matches the domain's stated policy. For example, if the message comes from an unknown server, it may be considered a forgery.
This SPF record may look like the following: http://domain.com IN TXT "v=spf1 a mx include:spf.imc-hosting.com -all" (more detailed information is always provided by the Scheer IMC project manager).
Important note:
-
Setting this SPF record is the responsibility of the customer.
-
As soon as the entry has been set on the customer side, the customer informs the Scheer IMC project manager.
-
The entry is then checked by the Scheer IMC hosting site and the setup is completed.
A later removal of the SPF record can result in mails no longer reaching the users.
Supplementary note:
In the standard case, the Technical Setup assumes that the LMS sends mails under a single sender address. The LMS also allows the use of several sender addresses (e.g., different sender addresses per provider/client). This can make sense in a scenario with internal and external users, for example, where the LMS is also available under several URLs and different names are used for both target groups.
In this case, effects must be carefully considered, and all of the above settings must be ensured for each sender address.