Freron MailMate

Comments and changes to this ticket

• 

  benny April 27th, 2015 @ 09:11 AM

  I'm getting the reports. If you launch from a Terminal window then I think there should be some additional output when you trigger the crash:

  /Applications/MailMate.app/Contents/MacOS/MailMate
  

  I cannot reproduce it. Do you both sign and encrypt? Do you have the preview enabled in the Composer window? Does it appear, in the preview, that MailMate can encrypt the message?

• You flagged this item as spam.
  

  Paul April 27th, 2015 @ 10:11 AM

  OK, I think the cause is clear: I Bcc all emails to my own address.

  But should this cause a fatal error?

  $ /Applications/MailMate.app/Contents/MacOS/MailMate 2015-04-27 19:59:02.793 MailMate[34508:507] Invalid color System, labelColor (warning given only once)
  2015-04-27 19:59:06.710 MailMate[34508:507] *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
  2015-04-27 19:59:06.710 MailMate[34508:507] *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
  Warning: Decoding empty text body for id 1251121
  Warning: Decoding empty text body for id 1251121
  Warning: Decoding empty text body for id 1251121
  Warning: Decoding empty text body for id 1251121
  Warning: Decoding empty text body for id 1251121
  Warning: Decoding empty text body for id 1251121
  Fatal: Bcc recipients are not supported for S/MIME encrypted messages
  Abort trap: 6
  $

• 

  benny April 27th, 2015 @ 01:10 PM

  • State changed from “new” to “reproduced”

  I had completely forgotten about this. Bcc is tricky because it really requires separate emails to be created, one for each recipient encrypted for that recipient only. (Well, your problem is a special case which does not necessarily require that kind of care.)

  The best fix would be to automatically create these emails, but it's not straightforward how to best do this. A quicker fix would be to simply refuse to try to send the email when Bcc is combined with encryption -- or let the user allow MailMate to encrypt to all recipients (the problem is that I think the email addresses could be deduced from this although I'm not sure -- might also not be the same for S/MIME and OpenPGP).

  But I should focus on the “best fix” since this would also make it possible to “Bcc” in a “nice way” -- actually putting the recipient address in the To header for each recipient. (The standard bcc method uses the standard “undisclosed recipients” which might not always be desirable.)

• You flagged this item as spam.
  

  Paul April 28th, 2015 @ 12:23 AM

  Thanks.

• You flagged this item as spam.
  

  Paul November 2nd, 2015 @ 06:45 AM

  Hope this one can be fixed sometime soon as well.

  Thanks,

  Paul.

• 

  benny November 2nd, 2015 @ 02:32 PM

  Given that I probably won't have time for a proper fix soon then it might be better if I introduce a hidden preference to allow bcc'ing yourself. Try this after the next update:

  defaults write com.freron.MailMate MmBccEncryptionCheckDisabled -bool YES
  

  This should allow you to encrypt when bcc'ing. (It requires a certificate exists for the bcc address.)

  (I've also changed it such that an error message is generated instead of the current fatal error.)