Freron MailMate

Comments and changes to this ticket

• You flagged this item as spam.
  

  Olaf April 7th, 2016 @ 11:54 AM

  I've just discovered that it is probably some of Microsoft Exchange infrastructure is encoding the header.

  I also attached a message that can be used for test purposes.

  • 699902.eml 5.1 KB
• 

  benny April 21st, 2016 @ 12:46 PM

  The problem is not base64 and MailMate can handle that.

  The problem is this part:

  Content-Type: multipart/mixed;  
      boundary="_003_D1A05F2440914DEFAF7A082121B5C3A6isocorg_"
  MIME-Version: 1.0
  
  --_003_D1A05F2440914DEFAF7A082121B5C3A6isocorg_
  Content-Type: text/plain; charset="us-ascii"
  
  
  --_003_D1A05F2440914DEFAF7A082121B5C3A6isocorg_
  Content-Type: application/pgp-encrypted;  
      name="PGPMIME Versions Identification"
  

  1. It's multipart/mixed instead of multipart/encrypted.
     
  2. There's a rogue body part (text/plain).

  I'm not really sure what to do about this. I could probably work around number 1, but I'm not sure I should. Number 2 is a bit more tricky (implementation-wise) although MailMate already has the capability to indicate when a message has unencrypted subparts. The problem is that this is also against the standard -- in other words I'm not really sure I should work around it. At least not without warning the user. Do you often get this type of message?

• You flagged this item as spam.
  

  Olaf April 21st, 2016 @ 01:15 PM

  Thanks,

  I did overlook both those factions and misdiagnosed.

  I do not consistently get these.

  I think it has to do with the sending server that is being used. I think it may have something to do with the way that some servers on-path do content checking. I strongly suspect the office365 infrastructure mucking with the mime-encapsulation.

  Apple's Mail does parse these messages. That doesn't really say you should, tough call.

  I suggest you stall the ticket.

  --Olaf

• 

  benny April 21st, 2016 @ 01:36 PM

  • State changed from “new” to “bluesky”

  Ok, I'll mark it as “bluesky” for now, but let me know if you regularly get these messages since then I probably should do something about it.

  Note that if Apple Mail (GPGTools) displays the plain text body part without clearly indicating that it's not encrypted then it would be pretty bad. (Well, Apple Mail already has this kind of bug for S/MIME and they don't seem to care — I reported it years ago.)