Bug 32998 - Review UCR variable descriptions for mail packages
Review UCR variable descriptions for mail packages
Status: NEW
Product: UCS
Classification: Unclassified
Component: Mail
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-29 09:43 CET by Sönke Schwardt-Krummrich
Modified: 2020-06-22 18:57 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Typo/text changes, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2013-10-29 09:43:53 CET
The following UCR variables of package univention-antivir-mail are still without UCR description:

mail/antivir/banned/basic_ext: yes
mail/antivir/banned/double_ext: yes
mail/antivir/banned/file_type: no
mail/antivir/banned/long_ext: no
mail/antivir/banned/mime_type: no
mail/antivir/banned/rfc2046: yes
mail/antivir/scanner: clamav
mail/antivir/spam: yes
clamav/archive/maxfiles: 1000
clamav/archive/maxfilesize: 10M
clamav/archive/maxrecursion: 5
clamav/checks: 24

+++ This bug was initially created as a clone of Bug #30945 +++

The UCR variable descriptions for the packages in base/ should be reviewed:

- Are descriptions missing?
- Are they comprehensible and self-contained?
- Are the syntactical options obvious for the user?
- Quality of the English translation

./univention-horde4/debian/univention-horde4.univention-config-registry-variables
./univention-mail-cyrus-murder/debian/univention-mail-cyrus-murder.univention-config-registry-variables
./univention-fetchmail/debian/univention-fetchmail.univention-config-registry-variables
./univention-mail-postfix/debian/univention-mail-postfix.univention-config-registry-variables
./univention-spamassassin/debian/univention-spamassassin.univention-config-registry-variables
./univention-mail-cyrus/debian/univention-mail-cyrus.univention-config-registry-variables
./univention-antivir-mail/debian/univention-antivir-mail.univention-config-registry-variables
./univention-postgrey/debian/univention-postgrey.univention-config-registry-variables
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2013-10-29 09:48:06 CET
In univention-mail-cyrus the UCR variable "mail/cyrus" is also undocumented.
Comment 2 Daniel Tröder univentionstaff 2015-05-08 09:14:14 CEST
mail/cyrus is now documented in component/dovecot/univention-mail-cyrus. It will be [un]set when univention-mail-cyrus is [un]installed. → Bug #38479
Comment 3 Dirk Ahrnke univentionstaff 2020-01-08 14:48:43 CET
I havent seen any other documentation dealing with the "mail/antivir/banned" UCRvs beside https://help.univention.com/t/von-amavis-blockierte-e-mail-anhange/222 and not sure if I should point a customer to it.
Comment 4 Sönke Schwardt-Krummrich univentionstaff 2020-01-14 09:58:33 CET
(In reply to Dirk Ahrnke from comment #3)
> I havent seen any other documentation dealing with the "mail/antivir/banned"
> UCRvs beside
> https://help.univention.com/t/von-amavis-blockierte-e-mail-anhange/222 and
> not sure if I should point a customer to it.

If that still works, I see no reason why the information should not be released to the customer.