Error Reference

Email attachment blocked: file type not allowed

Email attachment blocked: file type not allowed

Where this appears

This error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow attempts to process an inbound or outbound email notification containing an attachment. The error occurs during email processing when the attachment file extension is found on the system's blocked extensions list, preventing the email from being sent or received successfully.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Email attachment blocked: file type not allowed" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

The attachment file extension is included in the 'glide.email.attachment.blocked_extensions' system property which contains a comma-separated list of restricted file types. (high likelihood)

The attachment has a potentially dangerous file extension like .exe, .bat, .scr, or .vbs that is blocked by default security settings to prevent malware transmission. (high likelihood)

A custom business rule or script is adding additional file type restrictions beyond the standard system property configuration. (medium likelihood)

The file extension is being incorrectly detected due to multiple extensions or unusual file naming conventions that trigger the security filter. (low likelihood)

Fix

Step 1: Navigate to System Properties > All Properties and search for 'glide.email.attachment.blocked_extensions' to view the current list of blocked file extensions.

Step 2: Check the System Log at System Diagnostics > Log > Application Log to identify the specific file extension that triggered the block and the email notification involved.

Step 3: Verify the attachment file extension against the blocked extensions list to confirm it matches one of the restricted types.

Step 4: If the file type should be allowed, modify the 'glide.email.attachment.blocked_extensions' system property by removing the problematic extension from the comma-separated list.

Step 5: Review any custom business rules on the Email table or related notification tables that might implement additional file type restrictions.

Step 6: Test the email notification by manually triggering it or waiting for the next scheduled send to verify the attachment now processes successfully.

Step 7: Monitor the System Log after changes to ensure no new security vulnerabilities are introduced by allowing previously blocked file types.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue