<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">My response would be to tell the sender that their email is non-conforming to email standards, that you are unable to read it, and that they will have to resend it through another provider. Don’t fall to this kind of pressure. Put the onus where it belongs.</div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Sep 2, 2024, at 5:22 AM, Robert M. Münch <robert.muench@saphirion.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">Hi,</p>
<p dir="auto">I just received an RPMSG message, and it looks like Microsoft uses the next <em>non-industry standard</em> to force people to use their technology.</p>
<p dir="auto">For background information, see: <a href="https://openrpmsgfile.com/" style="color: #3983C4;">https://openrpmsgfile.com/</a></p>
<p dir="auto">I'm wondering how to deal with this. I don't want to use a crappy viewer application or fragment my workflow over several proprietary tools.</p>
<p dir="auto">Did anyone else have to deal with such messages already?</p>
<p dir="auto">Viele Grüsse</p>
<p dir="auto">--<br>
Robert M. Münch</p>
</div>
</div>
<span>_______________________________________________</span><br><span>mailmate mailing list</span><br><span>Unsubscribe: https://lists.freron.com/listinfo/mailmate</span><br></div></blockquote></body></html>