Bug 56983 – Silently ignoring a missing mailPrimaryAddress with fetchmail-single-drop configurations may lead to emails not being delivered

Bug 56983 - Silently ignoring a missing mailPrimaryAddress with fetchmail-single-drop configurations may lead to emails not being delivered


Summary:	Silently ignoring a missing mailPrimaryAddress with fetchmail-single-drop con...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Mail
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Mail maintainers
QA Contact:	Mail maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2024-01-15 14:28 CET by Christian Kowarzik
Modified:	2024-01-15 17:06 CET (History)
CC List:	2 users (show)

See Also:	56482
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.137
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023080321000237
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christian Kowarzik 2024-01-15 14:28:38 CET

Package: univention-fetchmail
Version: 13.0.7-3

With package univention-fetchmail-13.0.7-3 a solution to Bug #56482 is shipped which just silently removes fetchmail-single-drop configurations from /etc/fetchmailrc for a user when the mailPrimaryAddress is not set.

This will lead to emails from the remote mailbox not being retrieved and delivered.

As fetchmail-single-drop configurations depend on the mailPrimaryAddress it should not be possible to save a user-object with fetchmail-single-drop configurations if the mailPrimaryAddress is not set.

Instead a notification should be shown like it is the case with various other configurations that depend on a valid mailPrimaryAddress.

For instance with mail forwardings and missing mailPrimaryAddress the notification "The LDAP object could not be saved: Not all needed information was entered: Primary e-mail address must be set, if messages should be forwarded for it." is shown and the user-object not saved.

Also to activate a user for the OX App Suite a mailPrimaryAddress must be set. Otherwise the notification "The LDAP object could not be saved: The primary mail address is required for Open-Xchange users. Currently the users' primary mail address is not set." is shown and the user-object not saved.