[GH-ISSUE #218] Quarantine self-service #202

New issue

Closed

opened 2026-02-27 11:10:35 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 11:10:35 +03:00

Owner

Originally created by @tonioo on GitHub (Dec 4, 2013).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/218

Originally assigned to: @tonioo on GitHub.

Originally created by Antoine Nguyen on 2012-04-04T18:55:01Z

Quarantine self-service is a feature which requires amavis and modoboa to work
hand in hand: Amavis processes messages and sends out quarantine notifications
via SMTP - modoboa processes quarantine release/delete requests via HTTP.

It is not desirable to let a recipient release a quarantined message by herself
in any case. Security concerns usually dictate which messages may be released by
recipients themselves and which require an operator to inspect it first and
decide whether it may be released or not.

    *Example: Virus quarantine*
    For example a message quarantined because it possibly contains a virus
    might be a content class a recipient might not release by herself.

Whether a recipient can release a quarantined message by herself or whether it
takes operator interaction can be controlled by the amount of information sent
in the quarantine notification.

amavis can send different parts of information, encoded into an HTTP URL. It may
send everything it takes to release a message or only as much as required to
identify the message and start a release request.

Use Case: Recipient may release/delete message
amavis sends everything it takes to release a message i.e. a combination of
quarantine ID and secret ID as part of an URL as notification to the recipient.
Both, quarantine ID and secret ID, are unique to a quarantined message.
The recipients clicks the URL, the browser opens the URL and modoboa creates a
page with details of the message to be released or deleted. The recipients
chooses one of two actions and modoboa carries it out.

Use Case: Recipient may only request to release/delete a message
amavis sends as much as it takes to identify the quarantined message i.e. the
quarantine ID as part of an URL as notification to the recipient. Without the
secret ID, which is also required to release the message, the recipient cannot
release it herself.
The recipients clicks the URL, the browser opens the URL and modoboa creates a
page with details of the message to be released or deleted. The recipients
chooses one of two actions:

delete message
If the recipient chooses to delete the message modoboa carries it out.

release message
If the recipient chooses to release the message modoboa sends a mail with a
release request to the designated admin. The admin receives the message,
clicks the URL and may either release the message to the recipient or send it
to himself e.g. in order to inspect it more closely.

Ideas for future development:

release/delete message within HTML mail message using AJAX
let operator re-scan the message

Originally created by @tonioo on GitHub (Dec 4, 2013). Original GitHub issue: https://github.com/modoboa/modoboa/issues/218 Originally assigned to: @tonioo on GitHub. **Originally created by Antoine Nguyen on 2012-04-04T18:55:01Z** Quarantine self-service is a feature which requires amavis and modoboa to work hand in hand: Amavis processes messages and sends out quarantine notifications via SMTP - modoboa processes quarantine release/delete requests via HTTP. It is not desirable to let a recipient release a quarantined message by herself in any case. Security concerns usually dictate which messages may be released by recipients themselves and which require an operator to inspect it first and decide whether it may be released or not. ``` *Example: Virus quarantine* For example a message quarantined because it possibly contains a virus might be a content class a recipient might not release by herself. ``` Whether a recipient can release a quarantined message by herself or whether it takes operator interaction can be controlled by the amount of information sent in the quarantine notification. amavis can send different parts of information, encoded into an HTTP URL. It may send everything it takes to release a message or only as much as required to identify the message and start a release request. _Use Case: Recipient may release/delete message_ amavis sends everything it takes to release a message i.e. a combination of quarantine ID and secret ID as part of an URL as notification to the recipient. Both, quarantine ID and secret ID, are unique to a quarantined message. The recipients clicks the URL, the browser opens the URL and modoboa creates a page with details of the message to be released or deleted. The recipients chooses one of two actions and modoboa carries it out. _Use Case: Recipient may only request to release/delete a message_ amavis sends as much as it takes to identify the quarantined message i.e. the quarantine ID as part of an URL as notification to the recipient. Without the secret ID, which is also required to release the message, the recipient cannot release it herself. The recipients clicks the URL, the browser opens the URL and modoboa creates a page with details of the message to be released or deleted. The recipients chooses one of two actions: _delete message_ If the recipient chooses to delete the message modoboa carries it out. _release message_ If the recipient chooses to release the message modoboa sends a mail with a release request to the designated admin. The admin receives the message, clicks the URL and may either release the message to the recipient or send it to himself e.g. in order to inspect it more closely. _Ideas for future development:_ - release/delete message within HTML mail message using AJAX - let operator re-scan the message