...

The email itself will still be send via the Spacewell email server, but the email will look like it originated from the specified client email address. This can lead to the email being labeled as spam by a receiving mail server. This is most often the case if the receiving mail server is the same as the server the email pretends to be from. (So any email send via Workplace Management to the employees of the client)

There are several steps options that can be taken to prevent this problem.

Add an SPF (Sender Policy Framework) record to the clients DNS

By adding having the client add the necessary SPF record to your there DNS, the receiving mailserver can verify that Workplace Management is allowed to send emails on behalf of your domain. The following inclusion needs to be done on your the DNS:

include:_spf.axxerion.com

If you would like to have more information in regards to SPF, please refer to the documentation that can be found online like this post from DMARCIAN.

Testing the

...

SFP record

If you want to test if you added the spf record is added correctly, you can use free online tool to see if the spf record is available. Easy to use tools are:

...

If the above options are not sufficient or you would like to use your own mailserver, that is also possible. Navigate to “Setup > Email”. Fill in the following fields (be aware: these values should be provided by your IT department):

Mail host: Fill in the host for the e-mail Mail port: Fill in the required port User name: The username with which the mailserver should be accessed Mail password: The username with which the mailserver should be accessed Use SSL Connection: If you would like to use the SSL variant of the connection to the mailbox TLS Mode: Select the TLS mode that you would like to use (leave it on “Default” if unknown)

Image Modified

Limitation

When using your own mailbox, there is one major limitation compared to using the native mail feature in Workplace Management. When Workplace Management sends an e-mail to the client server and it fails, it will not retry this e-mail. The simple reason is that if the system would do this, it might be blocked due to a possible identification as a DDoS attack (“spamming” the server with requests). In case the native e-mail feature is used, an e-mail is retried for 24 hours before failing.

...