Attachments are discarded from inbound email despite their total size being below maximumIssue The system property glide.email.inbound.max_total_attachment_size_bytes controls the total size of attachments that can be allow to process in the ServiceNow instance. It can happen that an attachment (or multiple attachments) seem not to reach that threshold but the attachments are removed.CauseThe ServiceNow instance needs to convert the attachments with base64 before they can be added to teh attachment table, this adds approximately 37% to the size of the attachment(s).ResolutionThe property that controls this is glide.email.inbound.max_total_attachment_size_bytes. The code will take in attachments until the total size exceeds what's in this property then the rest are dropped. If the first attachment processed exceeds this property then all subsequent attachments are ignored. The attachment size used is the size of the base64 encoded attachment, not the size that you'll see on your disk. Base64 encoded files tend to be about 37% larger than their binary counterparts but this gets worse for very small files. Especially taking into account that there could be many small attachments the overhead generated by the base64 conversion the 37% is not an exact number.You can add 37% to the system property glide.email.inbound.max_total_attachment_size_bytesRelated LinksKB0521772 notes that the ServiceNow email servers have an encoded size limit of an inbound email is 75MB and 25MB for outbound email. It also notes that encoding can increase the size of the original attachment by 1.3 - 1.4x. Therefore a limit of 50MB in total for an inbound email and 18MB in total for outbound email are reasonable expectations. This total includes the entire email - HTML, plain text, attachments, headers and any encoding overhead.