Re: Microsoft's "Modern Authentication"
Christer Mjellem Strand <[email protected]> Fri, 05 Mar 2021 17:22:09 +0100
| Newsgroups | gmane.mail.mulberry.user |
|---|---|
| Message-ID | <ABE88B979F74A2D5CB12A330@plopp> |
>>> There was no message to your reply. >> >> It shows just fine here, so I suspect it's just [some Microsoft >> client] failing to comprehend multipart/signed. Not an entirely >> unfamiliar problem, I'm afraid; Microsoft's MIME handling has always >> been abhorrent, across their many attempts over the years at doing >> mail. All the more reason to use a sensible MUA (read: Mulberry) >> instead :) > > I am indeed using Mulberry on a Mac, but there was just a MIME > signature attachment, which I didn't want to chance opening. Oh! Then I suspect the answer may be your list settings. I've seen cases where when MLMs like Mailman or Sympa are set to tamper with the MIME parts before delivery, they will sometimes end up scrubbing parts you don't want scrubbed. Like Sympa will scrub the text/calendar part of a multipart/alternative when you're just trying to get rid of an unwanted text/html part. Extra frustrating when the sending client fails to understand the meaning of "alternative" - hello Outlook - so the remaining text/plain part doesn't actually contain the details of the event. Sounds here like Mailman is scrubbing the text/plain part for you, and leaving only the application/php-signature part, which certainly isn't much use on its own! The copy I received through the list had both, so our subscription settings probably differ. >> Anyway, I'll re-send it unsigned, so it's easier to read in inferior >> clients ;) > > Thanks - that worked! Good, I'll try to remember switching it off for this thread. -- Christer Mjellem Strand System Administrator