Hello,
I remember you. Have you tried without your extra ckeditor plugin and script to
add signatures? Because when testing with my own sogo server, there were no
problem to send an email to you.
Quentin
From: users-requ...@sogo.nu <users-requ...@sogo.nu> On Behalf Of Baptiste TANDA
Sent: lundi 4 novembre 2024 17:12
To: Baptiste TANDA (forum-s...@abcreseau.com) <users@sogo.nu>
Subject: Re: [SOGo] Error code 552 5.2.0 Message contains bare CR and is
violating 822.bis section 2.3
Hi everybody,
Concerning our issue, we've made some more tests. We sent an email using the
"mail" command directly from our mail server (see below) :
mailx -s "Mail with HTML body" \
-r <mailto:m...@abcreseau.com> "u...@domain.fr" \
-a "Content-Type: text/html" \
tanda.bapti...@orange.fr <mailto:tanda.bapti...@orange.fr> <<EOF
<html>
<body>
<h1>HTML mail with é à è characters</h1>
<p>This is the HTML body of the mail.
Cariage Return
</p>
</body>
</html>
EOF
The mail arrived on our test address (tanda.bapti...@orange.fr
<mailto:tanda.bapti...@orange.fr> ) without any issues. We think that the
encoding in the SOGo Webmail is wrong and causing the bug, but we didn't find
any fix yet.
Does anyone has any idea to solve this issue?
Le 21/10/2024 à 16:48, Baptiste TANDA (forum-s...@abcreseau.com
<mailto:forum-s...@abcreseau.com> ) a écrit :
Hi everybody,
Our SOGo mails are refused by the mail server @orange.fr with the following
error :
"552 5.2.0 Message contains bare CR and is violating 822.bis section 2.3"
We've investigated the issue and noticed that this happen everytime we use a
special french character ("à" for example) and/or when we have several lines in
our mail (at least 2 lines).
We also noticed that in such cases, and only in such cases, a header is added :
"Content-Tranfer-Encoding: quoted-printable"
It does not happen when we have a single simple line in our email body without
any special characters.
By the way, we can send attachment without any issue, as long as there is no
"...quoted-printable"
The server is a Debian 11 with Exim4 (4.94.2-7) and SOGo (5.11.2.20241016-1)
Any idea how to solve that issue ?
