Repository navigation
v1.0.104
The message tester looks inside zip attachments
MailScanner does not only test an attachment's own name: for an archive it unpacks the members and tests each member's stored path (folders included) against the separate Archives: Filename Rules file, whose stock very long filename limit is 150 characters, not the 255 of the top-level file. A photo in a folder with a descriptive name can be blocked that way while the message tester said every attachment was allowed.
- Test message /
msfe-ng conf test-messagenow read a zip's table of contents and report every member —path/in/zip (in archive.zip) → deny by archives.filename.rules.conf (.{150,}: …)— exactly as the engine would judge it, and the prediction counts those members as blocked. - An encrypted member is reported as refused unless Allow Password-Protected Archives is on.
- Members are not unpacked: the
Archives: Filetype Rules(which need the bytes) and nested archives stay with the engine, and the transcript says so. Zip64 archives are reported as unread rather than guessed.
Wiki: Config. Upgrade: msfe-ng upgrade, or the Service tab.