Hello Ray,
what kind of configuration are you currently using?
It is expected for the domain to have an associated e-mail to be used, but from what I can see you have now changed the MX record (it is now marked at not configured) and no e-mail addresses for pinderrehabservices.com have been created on the hosting space.
I remain available.

Hi Eric,  Thanks again for your prompt response!

I changed the website email form to my email address as the <customer_Email_Address> is not working, and I'm about to go and check on the office365 side of the settings, has here main emails have stopped working.

I will attached a link of the DNS settings, if I change the DNS, do I need to do anything on the hosted side for emails?

will send two attachements.

Here is the second attachement

I had asumed, that if I changed the DNS record, this would be all that I would have todo, but maybe I'm missing other changes in the DNS.

My Registrar is godaddy.

Hello Ray,
the expected configuration is to use the included e-mail addresses available, and not external providers such as Outlook, so if you use the preconfigured settings for exporting (choosing WebSite X5 Hosting so that you don't need to manually add the parameters) the configuration will not work: at the moment, all e-mails generated from your website are sent by a noreply address present by default, as no address was created yet.
You have two options:

1) Revert to the MX record listed in the hosting panel and create an address associated with the domain pinderrehabservices.com, so that it cane used to send e-mails. With this configuration, you can keep exporting with the "WebSite X5 Hosting" option.
2) Leave the Outlook MX record, and configure this address so that the website can use it to send e-mails. You will need to switch to "Other provider" and manually add all FTP and database parameters for your WebSite X5 Hosting space (you can find them in the web hosting panel here on the Help Center) and use the necessary settings from Outlook in the E-mail tab.

I remain available.

Hi Eric,
For business accounts, its quite common to use the secure office365 server for business emails.

Are you saying that with Websitex5 hosting, its not possible for the hosted websites to use microsoft office365 as a secure mail server?

Thanks

Ray

Hello Ray,
not with the default configuration: our hosting is mainly meant as a simplified configuration to allow users to export without much hassle, without having to configure parameters before being ready to go.
This means you would need to switch to the "Other webspace provider" and manually set up the parameters if you instead wish to go ahead with this e-mail configuration.
Apologies for the inconvenience.

Hi Eric,  Ok, I'll prepare to move to an external hosting where more control options are available to support office365 email serving.

I did discover that my mail.com account appeared to be having problems with the formatting of the notification email, while others appeared to be ok.

Cheerz

Ray

Hello,
once you do, in order to remove the DNS configuration on the hosting space you can follow the steps in the screenshots below.

I remain available.

Hi Eric,  I have been doing some research into different approaches to get around this.  Would you please review the attached and see if any of these are possible from the websitex5 hosting side?

Short answer:This is a mail‑authentication issue: your website must authenticate to Microsoft 365 (or relay through an allowed IP) before Office 365 will accept messages that claim to come from your business addresses. The two practical fixes are (A) configure your site to send via Exchange Online SMTP (authenticated, port 587) using a dedicated mailbox or app credential, or (B) set up an Exchange Online SMTP relay (IP‑based connector) if your host can provide a static public IP and allow outbound port 25.

Why this is happening

• Office 365 rejects or flags messages that appear to be sent from your domain but are not authenticated by Exchange Online or an approved relay; that looks like spoofing to Microsoft and to receiving spam filters. SPF/DKIM/DMARC checks and connector rules enforce this.

• Your web host’s built‑in phpmail() likely sends mail directly from the webserver IP without authenticating to Office 365, so messages from your business addresses are treated as forged. Non‑business addresses may pass because they don’t match your domain’s SPF/DKIM.

Quick decision table (options at a glance)OptionHow it worksProsConsSMTP Client Submission (Auth, port 587)PHP connects to smtp.office365.comwith mailbox credentialsWorks from any host; authenticated; reliableRequires a mailbox and SMTP AUTH enabled; may need app password/MFA adjustments. SMTP Relay via Connector (IP auth, port 25)Create Exchange connector allowing your server IP to relayNo mailbox credential needed; good for apps/devicesRequires static public IP and port 25 open; host must support it. Direct SendSend directly to Office 365 without authentication for internal deliverySimple for internal-only deliveryNot suitable for sending to external recipients; still needs SPF/DKIM care. Third‑party transactional SMTP (SendGrid/Mailgun)Site sends via external SMTP API; deliverability handled by providerEasiest if host blocks SMTP ports; good deliverabilityExtra service cost; requires DNS setup for domain.Recommended step‑by‑step (most likely to work for you)

1. Prefer SMTP Client Submission first (if your host allows outbound TLS on port 587):

   • Create a dedicated mailbox (e.g., no-reply@yourdomain) in Office 365.

   • In your PHP code use a proper SMTP library (PHPMailer or similar) to connect to smtp.office365.com:587 (STARTTLS) and authenticate with that mailbox. Do not use mail().

2. If SMTP AUTH is blocked by tenant security, follow Microsoft guidance to enable SMTP client submission or create an app password / conditional access exception as needed.

3. If your host can provide a static IP and port 25 is open, request an Exchange Online connector (SMTP relay) and add the host IP to the connector and to your SPF record. This avoids per‑mailbox auth.

4. Update DNS: ensure SPF includes spf.protection.outlook.com (or the relay IP), and configure DKIM/DMARC for best deliverability.

Troubleshooting & next actions

• If your host blocks outbound SMTP or won’t give a static IP, moving hosts is one option — but first try a third‑party transactional service (SendGrid/Mailgun) which works over API/port 443.

• Test by sending via authenticated SMTP from the server and check Exchange message trace / headers to confirm authentication.

Final recommendation

Consider switching your site to authenticated SMTP (smtp.office365.com:587) using a dedicated mailbox and PHPMailer. If your host cannot support that or cannot provide a static IP for a connector, then either use a transactional email provider or consider a host that allows SMTP relay. These approaches are standard and documented by Microsoft.

Hello Ray,
to clarify, what have you tried at the moment?
Did you already check what I had mentioned in an earlier reply, using the "Other Webspace Provider" mode in order to manually set the parameters?

"2) Leave the Outlook MX record, and configure this address so that the website can use it to send e-mails. You will need to switch to "Other provider" and manually add all FTP and database parameters for your WebSite X5 Hosting space (you can find them in the web hosting panel here on the Help Center) and use the necessary settings from Outlook in the E-mail tab."

Hi Eric,  Good morning.  I think I missunderstood.  I thought you were suggesting that I switch to another Webspace provider.  Let me relook at your recommendations and report back.