Configure email settings

SPF record

Ensure the SPF record of the domains used as the sender  include:oclcspf3.oclc.org. 

Any old references can be removed:

• 193.240.184.7
• include:spf.hostedwise.nl
• include:oclcspf1.oclc.org
• include:oclcspf2.oclc.org

DKIM records

In order to sign the email, the following records must be created in the domains used as the sender. Once this is configured, it must be communicated to OCLC so the email can be signed:

wise1._domainkey CNAME 300 dkim1.wise.oclc.org.
wise2._domainkey CNAME 300 dkim2.wise.oclc.org.
wise3._domainkey CNAME 300 dkim3.wise.oclc.org.
wise4._domainkey CNAME 300 dkim4.wise.oclc.org.

DMARC record

When a DMARC record is set for a sender domain, the SPF record must be modified and the DKIM records placed. If not this does not happen, the OCLC mail server will be designated as a spammer. If this is not possible, the branch must be set to never be able to send mail. (This is only possible from Wise version 7.0.6).

Provision bounce parser

Since repeatedly sending from an incorrect address causes the mail server to be classified as a spammer. it is very important to turn on the bounce parser. This quickly removes incorrect addresses from the database, so that they are no longer used again.

SPF

An SPF record indicates which servers are allowed to send mail from a domain name. This is a TXT record in the DNS of that domain. For example, for bibliotheek.nl, an SPF record can exist if:

bibliotheek.nl.         3600    IN      TXT     "v=spf1 ip4:1.2.3.4 ip4:100.100.100.100 ip4:123.123.123.0/24 include:oclcspf3.oclc.org include:_spf.google.com ~all"

This means that mail may be sent from the mentioned IP addresses and from the addresses set in oclcspf3.oclc.org and _spf.google.com. There can only be 1 SPF record per domain. Determining the addresses in the SPF record should not require more than 10 DNS lookups. An ip4: reference does not cost a lookup, but an include: and mx: reference.

DKIM

When an e-mail is sent from a domain, the message can be signed, so that the content cannot be changed in transit. By signing, it can be checked that the email actually comes from the domain of the sender's address.

From time to time keys are used, and multiple DKIM records are usually set. This allows older e-mails to be validated for a while when the new key is put into use. To indicate which key is used, DKIM has a so-called selector. Wise uses the selectors wise1, wise2, wise3, and wise4.

These keys must be included in the DNS of the sending domain, but the Wise server must know them in order to sign the mail during sending. To make this possible, OCLC publishes the DKIM records and a reference to these DNS records must be included in the DNS of the sending domains.

To check a DKIM record, for example, MXToolbox (fill in the form as "domain:wise1" to check selector wise1) or dmarcian can be used.

DMARC

DMARC is used to enforce a policy that determines what to do if SPF or DKIM are incorrect. A DMARC record looks like
_dmarc 3600 IN TXT "v=DMARC1; p=none; rua=mailto:youraddress@yourdomain.com"

p= indicates the policy, which can be 'none', 'quarantine' and 'reject'. Notifications about rejected mail are sent to the rua= address. It is advisable to always try DMARC with 'none' first and keep a close eye on the reports, to see if any adjustments to SPF or DKIM are needed. If everything seems to be in order, a stricter policy can be enforced. Never start with 'reject', because there is a good chance that a lot of valid mail will be refused.

To check a DMARC record, for example, MXToolbox or dmarcian can be used.

For more information see for example https://mailtrap.io/blog/dmarc-explained/

Do I need to create the DNS records in my internal or external DNS?

These must be created in the external DNS.

From which address are the emails sent from Wise?

The mail is sent from "envelope address" or MAIL-FROM: <wise systemname>@wise-emea.oclc.org.
However, the customers normally only see the FROM: address, which uses the address set in the branch.
The MAIL-FROM: address is used for the "technical" handling, any bounces are sent here.

How can I see which bounces have been processed and what the result is?

The bounce parser tries to handle as many bounces as possible automatically. A daily report is written in the dashboard in the Manager. The processed bounces can optionally be consulted in the query tool in the Manager in the table actor_e_bounces. If a bounce has actually been processed, the bounce counter at the borrower's e-mail address is incremented. This can be consulted in the table actor_e_bounces with species='EML'. When too many bounces have occurred, the type of EML is converted to EMLB, and Wise no longer uses this address. It can still be consulted in the Client in tab 4 of the customer administration. For those that are not able to be processed, bounces are sent to an e-mail address that has been agreed with the Wise administrator.