[Evolution-users] Evolution 3.56.1 NDR: SMTPSEND.BareLinefeedsAreIllegal;

[Milan Crha]

On Tue, 2025-04-29 at 08:10 +0200, Allen Hewes via evolution-users
wrote:
> I am assuming, it's using HTTPS to send?

	Hi,
correct, the Microsoft 365 is about https://, no direct SMTP involved
here. It still construct a MIME message and passes it to the server "as
is", thus it can be Evolution generated the MIME content incorrectly.
What the Exchange server does with the message after it received I
really do not know, only Microsoft developers know.

Having a reproducible steps would really help, but I see it's not that
easy to trigger.

> So this would be for clients delivering e-mail to Exchange
> Online/Office365/Microsoft365 mailboxes wouldn't it?

While the Microsoft page talks about the clients doing a wrong thing,
as you said, and even the recipient's server claims the same error, it
still can be a problem of the Evolution/libcamel, incorrectly creating
the MIME content of the message.

> I am using Forwards are attachments to new e-mails

Okay, that generates a multipart/mixed message. Being the error message
from the server correct, the MIME content did not have a new line at
the end for some reason. That's not part of the message content written
in the composer, it's constructed by the code.

	Bye,
	Milan