Hello

We have a hosting at some provider where our dns zonefile is located for our domain as example domain.com.
At the same Provider our webhosting for domain.com and our os ticket sytem is installed.

our mails are at microsoft's 365 cloud services.

If some message is outgoing from osticket to our domain "domain.com" it get send to spam.
I saw something about SPF what did not pass.
Because this, i'm thinking about, that i need some SPF-Record for the Webserver we use.
Is that right, what i'm thinking?
Is it safe enough to just add "domain.com" to our existing line "v=spf1 include:spf.mailjet.com include:spf.protection.outlook.com -all" like "v=spf1 include:domain.com include:spf.mailjet.com include:spf.protection.outlook.com -all" or do i need to ask the webhoster what is hould add there?

Greetings,
calgia

  • KevinTheJedi replied to this.

  • KevinTheJedi

    I sucessfully configured Microsoft 365 as Mailserver.
    It did not work, because i dont got redirected to the login page from microsoft 365 for authenticate the shared mailbox. since i resolved the problem it works now as it should.

    thanks

    sincerely
    calgia

      calgia

      It sounds like you don’t have SMTP properly configured for your system email. When SMTP fails (or is not configured at all) the system uses the local webserver to send mail on behalf of your domain (usually via sendmail). If that’s the case and your domain doesn’t have SPF properly configured then mail will likely not pass SPF checks and will likely be marked as spam. Ideally, in normal scenarios, you want to configure SMTP so that outbound mail from the system is sent through your mail provider's servers which will ensure the best chance of deliverability.

      If you can’t configure SMTP then yes, definitely configure SPF. You may want DKIM setup as well. However, we can’t tell you which records to use are as we do not run your DNS nor mailserver. You would need to contact your mail administrator and/or hosting provider to get the appropriate records to add to your DNS.

      With all this being said, to configure SMTP for an O365 email you first need to upgrade to v1.17.5/v1.18.1, install/activate the OAuth2 plugin, ensure URL Rewriting is enabled and allowed on your webserver/site, and configure Modern Authentication (OAuth2 - Microsoft) for the system email. Here is our OAuth2 Authorization Guide (Modern Authentication for Emails) with full instructions on how to configure it. Once Modern Auth is configured you’ll simply input O365's SMTP info, enable SMTP on the Outgoing tab, and Save Changes to test the connection. If it gives you a green banner then you can do a final test using the Admin Panel > Emails > Diagnostic tool.

      Cheers.

          KevinTheJedi

          I sucessfully configured Microsoft 365 as Mailserver.
          It did not work, because i dont got redirected to the login page from microsoft 365 for authenticate the shared mailbox. since i resolved the problem it works now as it should.

          thanks

          sincerely
          calgia

            Write a Reply...