Issue Issue to send mails

[GravuTrad]

Server operating system version

Centos 7.9

Plesk version and microupdate number

Plesk 18.0.52 update 3

Hello.

I have lots of mails not received when they sent by my plesk with this failure since few updates only:

"Remote server returned '550 5.6.0 CAT.InvalidContent.Exception: DataSourceOperationException, proxyAddress: prefix not supported - ; cannot handle content of message......"

What's the problem please?

Thanks.

 

[GravuTrad]

a type of mail with strange text :
Afin de terminer votre adh=E9sion, nous vous invitons =E0 cliquer sur le li=
en suivant dans les 24 heures et de saisir les informations demand=E9es :

 

[Peter Debik]

It could be that your server is sending spam. The French text asks to confirm a membership for something. The error message you get returned is generated by the receiving server and says that the content body is malformed. It will be necessary to examine the content that is received to find out the reason.

 

[GravuTrad]

It's not spam it's one of my site which send the registration procedure.

 

[artalva]

By any chance, are the destination emails from Microsoft? For example, @hotmail.com, @outlook.com, @live.com, etc. They have an issue with encoding and can't handle messages with non-standard characters (like French accents). If you tell me the exact method you're using to send these registrations automatically, we might be able to find a workaround.

 

[GravuTrad]

yes it's correct, they are all from outlook.com (thanks for the report). My site use the php email function to send, and i use the postfix from plesk.

 

[artalva]

Fantastic. Try this: php mail special characters utf8. If the PHP code is handled automatically by some front-end like WordPress, let me know.

 

[GravuTrad]

I use a cms no more developed now but which was a fork of phpnuke. no postfix workaround?

 

[artalva]

Probably possible for the email body, but I don't know how to do it with Postfix. Will have to wait for Microsoft to fix it, and change the email content in the meantime.

 

[GravuTrad]

I use html entities for these special characters so it could be sufficient no? why microsoft have problem with them too?

 

[artalva]

I don't know. Microsoft would have to answer that, and as you can see on that link, they're not very responsive.

 

[Peter Debik]

From practical experience running Mantis Bugtracker I can also say that Office 365 has issues with special chars. In my case it was special characters in email names such as "Max Müller <[email protected]>" or "André <[email protected]>" where the Umlaut "ü" or accent aigu "´ " lead to rejected mails. Although going through their ticket support and several attempts in the source code here to change the mail headers in a way that MS likes it, it was not solved and I finally had to transcribe umlauts to "ue", "oe", "ae" etc.