We have a MailExtension using new Apple MailKit API. The extension returns an error from the SecurityHandler's Encode Method based on certain conditions and If an error is reported during mail send 3/4 times, even after user performed a corrective action and hits send again, the same error is is shown by Mail again for couple more times. The attached sample mail extension project returns an error after hitting send if subject line of the mail is “Show Alert”. If we repeat the error 3/4 times then even after changing the subject line the error is reported once or twice more. it is an Apple issue as per our investigation. After the subject line is changed in the mail, each time security handler’s encodeMessage is called, we return it successfully and no error is returned to Apple. Still the old error pop-up appears. I think this is a gap in sync between the remote process that loads the extension and actual Mail.app process. It takes a bit of time to reflect the status of encoding to Mail.app from the remote helper process. This is a timing issue, depends on how fast you keep bombarding the Send. After making the correction of the erroneous condition (in this sample, the subject line) if you wait for ten seconds and then hit ‘Send’ the issue doesn't happen. which suggests its a timing sync issue at Apple end. Code Sample Anyone else seeing this?

Hi, So far in my knowledge of the Mailkit API, a security handler’s encode method is the only place I can alter the RFC 822 data of an email (https://developer.apple.com/documentation/mailkit/memessageencoder/3882902-encode), Any other interface method that gives access to the message data gives a read only access. Can Please confirm if the same understanding is incorrect? Encode method, as the below documentation claims, is supposed to be called once, when the message is sent, but I can see that my extension’s encode method is being called several times during composing of an email. Is this a bug? /// @brief This is invoked when an outgoing message is sent. The supplied @c message will contain the email address of the sender, the recipient email addresses, and the message data being sent. The completion handler should be called with the @c result of applying any encoding if needed based on @c shouldSign and @c shouldEncrypt. If the @c result is not encrypted or signed and does not have any errors, it is assumed the message did not need a signature or encryption applied. In this case the @c data for the result will be ignored. /// @param message - The outgoing message to apply any security mechanisms on. /// @param composeContext - @c MEComposeContext instance which corresponds to the @c message being composed. (void)encodeMessage:(MEMessage *)message composeContext:(MEComposeContext *)composeContext completionHandler:(void (^)(MEMessageEncodingResult *result))completionHandler; I also noticed that mailComposeSessionDidBegin from ComposeSessionHandler is getting called but mailComposeSessionDidEnd isn't when I close the compose window of an email or hit send button. Is this also a bug?

I am looking into mail kit extensions and I can see that a security handler extension is the recommended way to offer encryption functionality for emails, however if user chooses to click the padlock icon in top right side of compose window, he can opt out of encryption and the security handler encode method is not called. Is there a way to force and mandate that user cannot opt out of encryption and a security handler's encode method is always called by Mail? My objective is actually to be able to inspect every mail attachment and depending on my business logic, I want to encrypt some of the mail attachments. So I need to make sure my security handler's encode method is called, always. Any other approach for achieving the same is also welcome.

Hi, In our organisation, we create and ship a plug-in for the MacOS Mail app along with our software package. We have heard that mail plugins are not supported in Mac OS Sonoma any more. https://www.macrumors.com/2023/06/14/macos-sonoma-drops-legacy-mail-app-plug-ins/ Can anyone tell us more details about what changed, what is its impact and any way to achieve similar functionality as the mail plugins offer, going forward. We read that mailkit extensions are a new thing, we could also use any heads up on its capabilities and limitations (if known). Thanks, Tathagata

I have an application that uses a FinderSync extension to show a couple of my application specific menu items when User ctrl+clicks open the context menu on a file in Finder. My Menu appears everywhere except when I move a file in my company MS Onedrive sync folder. My menu items are not visible in the context menu and only MS Onedrive menu items are visible. The same happens with other findersync menu items from other apps like dropbox for example. the menu items vanish whenever a file is moved into MS OneDrive. This didn't use to happen before. Anyone facing this? Is this expected behaviour? Is any change in Mac OS or MS Onedrive may be causing this? I am using latest Mac OS Monetary 12.6.6