#1702 mailmate_command.* - Code Signature Invalid - MailMate

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#1702 ✓closed

mailmate_command.* - Code Signature Invalid

Reported by Ryan Olton | February 27th, 2017 @ 04:06 PM

I recently installed Little Flocker (https://www.littleflocker.com) and noticed that some items (mailmate_command.* files) from MailMate that were not signed properly. Is there a way to get these signed just like the main MailMate application?

What are these mailmate_command.* files doing, by the way?

Screen_Shot_2017-02-27_at_10.56.43.png 125.2 KB
Screen_Shot_2017-02-27_at_10.56.59.png 124.1 KB
Screen_Shot_2017-02-27_at_11.01.31.png 140.5 KB

Comments and changes to this ticket

benny March 1st, 2017 @ 07:55 AM
- State changed from “new” to “closed”
These files are not signed at all. They are part of MailMate's bundle system (a plugin system in MailMate). Usually these are “simple” scripts. Some bundles are included with MailMate and some are (safely) downloaded depending on what is enabled in the Bundles preferences pane. In this case, you can disable the use of premailer by disabling HTML embedding in the Composer preferences pane.

I'll think about if this could be resolved in a different way somehow. Security-wise, the risk is that some other (evil) application is allowed to overwrite the bundles fetched by MailMate (e.g., replacing premailer), but in that case such an application would already have more direct means to do harm.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.