chillout2k / gulag Goto Github PK

Dockerize it

prevent DoS

Check if DB is initialized (select something expected from DB?) in entrypoint and source /gulag.sql if necessary.

The original email gets wrapped by an outer message with details on the exception/reasons of failure. Currently the IMAP UID-MOVE command is being used, which made it necessary to upgrade the docker base image to debian:buster (python 3.7), as the imaplib module on debian:stretch (python 3.5) does not support the MOVE command.

• SPA/jqgrid (overview)
• Basic authentication with external LDAP support or local passwd file (two accounts: read-only and admin)
• Release feature
• Bounce feature (for discarded mails)
• pdf preview feature
• Download email/attachments (zip password-secured)
• Execute attachments/URIs in sandbox
• Scan attachments with opswat API
• Scan attachments/uris with virustotal API
• Feed IoCDB with FQDNs, URIs and files

Compare new incoming email messages against quarantined messages by SSDEEP. Finally, let the MTA decide to accept, or to reject (soft/hard) the incoming email.

Images should be built for cross-stage deployments

The admin's API key is the only one, which is managed outside the app. All other API keys should be managed by REST API and stored in backend (database)

Gulag quarantine should not rely on an external IMAP server. The base config could consist of at least two accounts, one for inbound and the other one for outbound quarantine mailbox. Both email addresses should be configured by ENV vars as well as their passwords. All account information will be stored in a passwd like file dedicated for dovecot.

For webmail based access to the quarantine

See decoded contents without opening quarantined mail