Univention Bugzilla – Bug 48436
Extend default sieve script to optionally discard/reject mails with a certain spam level
Last modified: 2021-05-14 16:34:20 CEST
A customer wanted the default sieve script to discard mails that exceed a certain spam level (10.0) in this case. The default sieve script is currently not able to do that. It can only move spam to another folder, if it exceeds a configurable spam level.
If I'm not wrong, removing any mail is a violation of the Post- und Fernmeldegeheimnisses here in Germany and you are with one foot in jail if you try this.
(In reply to Sönke Schwardt-Krummrich from comment #1) > If I'm not wrong, removing any mail is a violation of the Post- und > Fernmeldegeheimnisses here in Germany and you are with one foot in jail if > you try this. That might be but I'm no lawyer... I think the customer told me that that only applies to mail that's already been delivered.
No lawyer here, too, but iirc you need something called "Pre-Queue Filtering" to not violate german laws (https://www.uni-due.de/zim/services/e-mail/mailpolicy-details.php#pre-queue-filtering). Sieve is too late in the process to be compliant.
> "Pre-Queue-Filtering" Correct. In this case, the mail is scanned before it is transferred to your area of responsibility. If spam or viruses are detected, the mail server can reject the mail at the last moment without ever having been responsible for it. Disadvantage of this method: You have to use the same amount of resources to scan mails and deliver them locally, but the mails usually get into your own area of responsibility slower. (In reply to Valentin Heidelberger from comment #2) > That might be but I'm no lawyer... I think the customer told me that that > only applies to mail that's already been delivered. AFAIR something like this applies (or not... depending on what exactly your mailserver is doing): §206 Abs. 2 Nr 2 StGB, Verletzung des Post- und Fernmeldegeheimnis durch Unterdrückung der Sendung §303a Abs. 1 2 Var. StGB, Datenveränderung durch Unterdrückung
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.