On 25/03/2025 10:52, Toon Moene wrote:
> On 3/25/25 11:32, Richard Earnshaw (lists) wrote:
>> On 24/03/2025 22:08, Toon Moene wrote:
>>> 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
>>
>> There's nothing in that post that looks even remotely close to 300 chars, 
>> let alone 998.  So I'm not sure what would be going on.
>>
>> R.
> 
> But this one has:
> 
> https://gcc.gnu.org/pipermail/gcc-testresults/2025-March/841925.html
> (the failing Fortran tests).
> 

LOL.  Yeah, not the most memorable of test names :)

R.

Reply via email to