On 3/24/25 17:27, Richard Earnshaw (lists) wrote:
On 23/03/2025 20:26, Toon Moene wrote:
I had the following message when sending test results to gcc-testresults
*starting* today (3 times):
Note that the message is generated by *my* exim4 "mail delivery software"
(Debian Testing) - it is not the *receiving* side that thinks the lines are too long.
Is anyone else seeing this ?
-------- Forwarded Message --------
Subject: Mail delivery failed: returning message to sender
Date: Sun, 23 Mar 2025 18:18:28 +0100
From: Mail Delivery System <mailer-dae...@moene.org>
To: t...@moene.org
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
gcc-testresu...@gcc.gnu.org
message has lines too long for transport
https://datatracker.ietf.org/doc/html/rfc5322#section-2.1.1
So there's a 998 (sic) character limit on the length of any line. I'm guessing
your mail posting tool is not reformatting the message and trying to pass it
straight through. Your SMTP server then rejects it.
I guess your options are to request a 'flowed' encoding type or to reformat the
message with a filter before passing it on to your SMTP server.
R.
Thanks.
I placed a
fold -s -w 300 |
filter in front of the
mail -s
command.
At least I got one simple test passed to the mailing list:
https://gcc.gnu.org/pipermail/gcc-testresults/2025-March/841892.html
Still wonder how I could have used the original for years without having
this problem ...
Kind regards,
--
Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
