Known Limitations¶
Signature Detection¶
The add-in detects email signature regions and excludes signature images (logos, social media icons, etc.) from the attachment selector. Detection works by looking for HTML markers that email clients insert around signature content.
| Email client | Status |
|---|---|
| Outlook Desktop / Web | Detected |
| Outlook Mobile / Mac | Detected |
| Gmail | Detected |
| Proton Mail | Detected |
| Apple Mail | Not detected |
| Other clients | Not detected |
Apple Mail does not add any identifiable HTML markers to its signatures, so the add-in cannot distinguish signature images from regular inline images. Those images will appear in the Embedded images section of the attachment selector instead.
Inline Images¶
Emails often contain images embedded in the body (pasted screenshots, inline photos). To show these in the saved email, the add-in matches each image to its attachment — by the attachment's content id when the email provides one, otherwise by comparing the filename in the image's CID reference against the attachment's filename.
When matching succeeds, the image is displayed normally in the saved email body. When matching fails, the image is replaced with a placeholder and the original is still kept as an attachment — it just can't be shown inline.
Common reasons a match fails:
- The email client rewrites attachment names or CID references during forwarding or replying.
- The email passed through a mail gateway that modified the HTML.
- Two attachments share the same filename, so the add-in can't tell which one an image refers to. A content id match is exact, so this only affects emails without content ids.
A common example is Outlook for Mac: some installations rename attachments to img-<UUID> (e.g. img-1128e903-4cbc-4820-b667-e09ff67cf975) instead of the original filename, so the attachment filename no longer matches the one in the image's CID reference. This is specific to individual machines — the same Outlook version works correctly on other computers, and there is no server-side workaround.
Shared Mailboxes¶
The add-in works in shared mailboxes, with a few things to know:
What works:
- Saving emails from a shared mailbox in Outlook on Windows, Mac, and the web.
- Each saved email is credited to the person who saved it, using their own Lime CRM login.
- The "already saved" marker on an email is visible to everyone in the shared mailbox, so colleagues can see it's been taken care of.
What doesn't work:
- Outlook on iOS and Android — Microsoft doesn't support add-ins in shared mailboxes on mobile. The add-in still works there for your own mailbox.
- Older Outlook versions — on classic Outlook for Windows, shared mailbox support requires version 2304 (April 2023) or later.
- Signing in to the shared mailbox directly with its own password — always access it through your own account.
If the add-in doesn't show up when using Open another mailbox in Outlook on the web, ask your IT administrator to install the add-in for the shared mailbox as well.
Conditional Access on Mobile (iOS and Android)¶
If your organisation uses Microsoft Entra Conditional Access, the add-in cannot sign in to Lime CRM in Outlook for iOS or Android.
On mobile, Office add-ins run inside the operating system's web view (WKWebView on iOS, Android WebView) rather than a Microsoft Edge–based control. Microsoft does not support Conditional Access for Office add-ins on iOS or Android. The web view can't present the device identity the policy requires, so sign-in fails — usually with error 530001 ("You can't get there from here").
This is a Microsoft platform limitation that the add-in cannot work around. Enrolling or marking a device as compliant does not resolve it, because the policy blocks the web view itself.
What to do:
- Use the add-in in Outlook on the desktop or on the web, where Conditional Access is supported.
- Or, if mobile use is required, an IT administrator can adjust the Conditional Access policy to allow it — at the cost of some of the protection the policy provides.