NMC2 (AP9631) SMTP fails to send via Ionos, workaround uses gmail
APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-3006:12 AM. Last Modified: 2024-03-0801:24 AM
NMC2 (AP9631) SMTP fails to send via Ionos, workaround uses gmail
On investigation, this error appears to have been happening since early April 2020 (firmware 6.8.2) and occurs with firmware 6.8.8, 6.9.4 and 6.9.6.
Mail is configured to use the "custom" server, by recipient (authenticated SMTP, port 465, implicit SSL/TLS). Only one recipient is defined.
Attempts to send mail via smtp.ionos.co.uk (Ionos, formerly 1 and 1) fail with the following error (description from the Ionos web pages):
+++
554 Transaction failed, reject due to policy restrictions
Problem:
The email was rejected by the IONOS SMTP server because the standards defined in RFC 5321 and RFC 5322 were not adhered to.
Solution:
The email client must meet the following criteria:
The header lines of the email must contain exactly one valid "Date" line according to RFC 2822.
The following header lines may only exist once: From, Sender, To, CC, Subject
The header lines mentioned must be syntactically correct
Note: The To and CC lines can contain multiple recipients.
In accordance with the recommendations from RFC7103, incorrect messages are not automatically corrected by IONOS, otherwise DKIM signatures become invalid. For more information about DKIM signatures, see the IONOS article Configuring DMARC Records for a Domain.
+++
As a workaround, configuring the mail server to use smtp.gmail.com with authenticated SMTP, implicit SSL/TLS and port 465 works.
I recall something similar a few years ago, where the NMC2 mail server did not send via what was then 1and1 using authenticated SMTP with SSL/TLS. That was resolved by a firmware update. It would seem that the current firmware (since 6.8.2) has a problem in the way that SMTP messages are sent, such that the Ionos SMTP server rejects them.