Rob Wood

This feature has been implemented in the above PR and will be available in the latest pre-release builds. Note that it will only display if the message has a plain...

Repro: ``` using System.Net.Mail; using System.Net.Mime; using System.Text; var smtpClient = new SmtpClient("localhost") { Port = 25, }; var mailMessage = new MailMessage { From = new MailAddress("[email protected]"), Subject =...

Further advice if you are seeing this bug. Try make sure your client is using the 8BITMIME extension, which forces UTF8. This should avoid the issue. SMTP4DEV is probably not...

PR #1344

Build 3.3.3-ci20240306100 should now be available. https://dev.azure.com/rnwood/smtp4dev/_build/results?buildId=2229&view=artifacts&pathAsName=false&type=publishedArtifacts

Pleased to confirm that I have created https://github.com/rnwood/smtpserver/pull/173 which addresses this issue in the server component. The message will now not be decoded and re-encoded with the wrong encoding in...

The PR has now been updated with what I think is a quite complete fix. The source and raw tabs have also been adjusted to detect the encoding from the...

@ballaballaballa Can you share the correct text for the body?

I've tested åäö with a variety of encodings including just-send-8-bit iso-8859-1 and I can't reproduce it. If we take this word as an example from what you are seeing: >...

@ballaballaballa I'm pretty sure that this shows that your client is sending UTF-8 encoded content but declaring it as ISO-8859-1. I believe Wireshark is assuming UTF-8. Can you select one...