Skip to main content
To protect against malware, phishing, and other security risks, MailChannels blocks certain high-risk file attachment types on both inbound and outbound mail. These file types can contain executable code or system components that could harm recipients if opened.
MailChannels’ blocked attachment policy is consistent with the policies of major providers such as Gmail, Microsoft Outlook, Yahoo, and others. For reference, see Gmail’s blocked attachments policy.

Blocked file extensions

The following attachment file extensions are blocked on both inbound and outbound mail:
adeadpapkappxappxbundle
batcabchmcmdcom
cpldiagcabdiagcfgdiagpkgdll
dmgexex_exehta
imginsisoispjar
jnlpjsjseliblnk
mdemjsmscmsimsix
msixbundlemspmstnshpif
ps1scrsctshbsys
vbvbevbsvhdvxd
wscwsfwshxll

Why these file types are blocked

These extensions are associated with files that can run code or alter system behavior:
CategoryExtensions
Executables and installersexe, msi, appx, apk, dmg, iso, cab
Scripts and macrosjs, vbs, ps1, jse, vb, wsf
Shortcuts and control fileslnk, cpl, msc, pif
Virtual disks and imagesiso, img, vhd
Java-related filesjar, jnlp
Diagnostic and config packagesdiagcab, diagcfg, diagpkg
Libraries and system filesdll, sys, lib, xll, vxd
These file types are frequently abused in attacks, may bypass simple scanning, and can execute code without clear user awareness.

How blocking works

When MailChannels detects a blocked file type as an attachment, the message is rejected during the SMTP transaction and the sender receives a bounce (NDR) containing an error such as:
550 5.7.1 [FEB] Your message could not be delivered because it contained an attachment type that is not allowed.
Archives such as ZIP or RAR files may also be blocked if they contain one or more of the blocked file types.

Safe alternatives

Instead of emailing blocked file types, use one of the following approaches:
  • File-sharing services — use enterprise cloud storage, managed SFTP, or a secure portal to share files with intended recipients.
  • Code and scripts — share as text snippets via a developer platform, repository, or collaboration tool rather than attaching executables.
When sharing via a link:
  • Restrict access to intended recipients only.
  • Set an expiration date on the shared link.
  • Enable download notifications where available.
  • Avoid public links unless necessary.

Troubleshooting

If your message was rejected due to a blocked attachment:
  • Do not attempt to bypass the block by renaming the file extension or placing it in a weakly-protected archive — archives may still be scanned and blocked.
  • Use an approved file-sharing method instead.
  • If you believe the file was blocked in error, contact support with the original file name, timestamp, sender and recipient addresses, and the full bounce message text.

FAQ

Why was my attachment blocked even though it’s legitimate? The policy is based on file type risk, not individual intent. These formats are widely abused regardless of the content of any specific file. Will zipping or encrypting the file help? Not reliably. Archives may still be blocked if they contain blocked file types, and encrypted archives cannot be scanned. Use an approved file-sharing service instead. Can an exception be made for my account? No exceptions are made to the blocked attachment policy.