@JamesRe2 @SatheeskannaK @Pulkit_Jain_ Thank You for Your support. We found the root cause of this situation with Adobe support:
“
I found the root cause, which is not caused by AJO, not by your SMTP, and not by a profile recipient provider.
The error "Serwer wysłał komunikat" is shown when delivering an email as this is literally hard coded in the HTML of this template, which is coming from a browser extension overlay (a grammar/spell checker / helper tool / quick copy+paste shortcut).
Due to usage of some extension in the browser of who created this template, three <lt-toolbar> blocks were embedded in your email HTML, causing the message to render them and break the AJO structure when it's delivered. This cannot be captured by AJO as it's not considered an error, AJO would flag it only if there was an error on the <lt-toolbar> block structure.
----------------------------------------------------------------------
<lt-toolbar data-lt-adjust-appearance="true" data-lt-force-appearance="light" style="display:none;" data-contenteditable="false">
<lt-div class="lt-toolbar__wrapper lt-toolbar--small" ...>
<lt-div class="lt-toolbar__status-icon lt-toolbar__status-icon--failed">
<lt-span class="lt-icon__tooltip lt-icon__tooltip--top-right">
Serwer wysłał komunikat „Odmowa dostępu" – sprawdź swój adres e-mail
i hasło w ustawieniach i spróbuj ponownie.
</lt-span>
</lt-div>
...
</lt-div>
</lt-toolbar>
----------------------------------------------------------------------
To visualise the above, open the affected template, select "...More" and "Export HTML", on this index.html exported, search for "Serwer wysłał komunikat".
Please note, those are not part of Adobe's email HTML. They are injected by a local browser extension in the creator's browser when they were editing or copying the email content, and that modified HTML has been saved into the AJO template.
Our recommendation to fix this for the future is check with all marketeers involved to create that template to review their active extensions, so you can identify which one caused it and avoid using it when creating a template in AJO.
Thank you for your help and for bringing this again to us along your infrastructure details. I was 100% sure this was not AJO, but that help us to confirm that was not in your SMTP or a recipient's provider.
”