Technical

On a high level this package fetches emails from a configured inbox and then deletes them after processing.

Flow/process

Required input data from a solution is an application config populated with a microsoft azure application configuration as well as resources. The configuration is used in order to authenticate with the Graph API.

Duplicate check

Sometimes processing of an email can be very slow for different reasons, which might cause multiple tasks being created to handle the same email. Therefore we have added the ability to check if the specific email already have started processing or been added to Lime CRM.

How it works:

Lime admin will automatically add the IDs of the e-mails being processed in sys_data and add a property to the EmailItem called is_processed.

It can easily be done with the function: have_email_been_processed that exists in limepkg_ms_inbox.behaviours or just check the property is_processed yourself.

File size limits

Lime Inbox itself doesn't have a coded limit when it comes to file sizes.

Lime as an application have a limit of files depending on how the files are stored.

Store type	Used in Cloud	Used in On-Prem	Limit in (MB)
SQL	Not supported	Yes (Default)	50
Disk	Not supported	Yes (Can be configured)	No given limit, OS and disk space/speed is the limit
S3	Yes (Default)	Yes (Can be configured)	100
Sharepoint Online	Yes (Can be configured)	Yes (Can be configured)	No given limit, Graph API and timeouts is the limit

Inbox will store different files depending on your configuration.

As a maximum you can store the mail file itself including all attachments (that means total size = sum of body and attachments.)

You can also store each attachment as a separate file and skipping the mail file or even do both.

The most common limit is that the total size of the email and attachments timeout and will cause errors. But when this happen it will be flagged as an error and you can see it in your start page using the Status add-on