Skip to content

Documentation

Attachments and malware scanning

Where attachments are stored, how every upload is scanned for malware, and the limits that apply.

Where
.env (Docker Compose) · values.yaml (Kubernetes) · eventier.env (Linux server)
Permission
Admin of the host, cluster or server (self-hosted)
Updated
October 2026

Overview

Only allowed file types are accepted, up to 10 MB each, and file names are cleaned before they are stored.

Each workspace has a storage quota for attachments: 5 GiB by default (ATTACHMENT_ORG_QUOTA_BYTES).

Every upload is scanned for malware before it is stored: request and reply uploads, portal form files, support-case replies, knowledge base media, profile photos, emailed attachments and admin imports.

Downloads check the scan result. A file stored without a scan is refused while scanning is required.

On the cloud edition, scanning is always on. A self-hosted install can turn it off.

Step by step

  1. 01

    Store attachments in an S3-compatible bucket

    By default a self-hosted install keeps attachments on its own disk. For production, use AWS S3, Cloudflare R2 or MinIO.

    • Each workspace gets its own folder (key prefix) in the bucket
    • Cloudflare R2 also needs the two S3_ settings shown
    .env or eventier.envbash
    ATTACHMENT_STORAGE_DRIVER=s3
    ATTACHMENT_S3_ENDPOINT=<endpoint URL>
    ATTACHMENT_S3_BUCKET=<bucket name>
    ATTACHMENT_S3_REGION=<region>        # auto on Cloudflare R2
    ATTACHMENT_S3_ACCESS_KEY_ID=<key id>
    ATTACHMENT_S3_SECRET_ACCESS_KEY=<secret>
    
    # Cloudflare R2 only
    S3_SERVER_SIDE_ENCRYPTION=none
    S3_CHECKSUM_MODE=when_required
  2. 02

    Use your own scanner

    Docker Compose and Kubernetes include clamd. To use a clamd you already run, point EvenTier at it.

    • Set CLAMAV_HOST and CLAMAV_PORT
    • Kubernetes: set clamav.enabled: false and env.config.CLAMAV_HOST, or clamav.external: true when the host is in your own Secret
    • Give clamd 3 to 4 GB of memory and a persistent signature folder
  3. 03

    Turn scanning off (self-hosted)

    One setting stores uploads without a scan. Files stored while it is off stay unscanned after you turn it back on.

    • Docker Compose or a server: ATTACHMENT_MALWARE_SCANNER=off; on Docker Compose the clamav service then does not start
    • Kubernetes: clamav.enabled: false
    • The cloud edition treats off as a mistake and refuses uploads
    .env or eventier.envbash
    ATTACHMENT_MALWARE_SCANNER=off
  4. 04

    Scan without internet access

    Turn signature downloads off and copy the signature files in. Air-gapped installs has the steps for each path.

Upload outcomes

What an upload returns, and whether the file is stored.

OutcomeResponseStored
Clean scan result201Yes, marked clean
Malware found422 MALWARE_DETECTEDNo; a security event records the signature and file hash
Scanner down, loading signatures, timed out or failed503 SCANNER_UNAVAILABLENo
Scanning required but no scanner set up503 SCANNER_NOT_CONFIGUREDNo
Workspace over its storage quota413 ATTACHMENT_QUOTA_EXCEEDEDNo
Download of a file stored without a scan, while scanning is required403 ATTACHMENT_NOT_SCANNEDAlready stored; the download is refused

Good to know

  • Emailed attachments are retried while the scanner is unavailable, instead of being dropped.
  • Profile photos and import files don't count toward the quota, but a workspace already over it can't upload them either.