Univention Bugzilla – Bug 56969
Newly created and valid fetchmail-multi-drop configuration is not entered in /etc/fetchmailrc
Last modified: 2024-01-16 11:03:58 CET
Package: univention-fetchmail Version: 13.0.7-3 If the mailPrimaryAddress of a user is not available, this is now logged in the listener.log. I would find it more helpful if the users were at least shown a message. At the moment, however, users may not even notice if there is a fetchmail-single-drop configuration but no mailPrimaryAddress, which may result in emails not being delivered. The behavior of the OX App Suite for fetchmail would be more extensive than a hint, because a user can only be activated for the OX App Suite if a mailPrimaryAddress exists. If a user does not have a mailPrimaryAddress, a corresponding message appears and the user object is not saved. Here is the error in the bug solution: For the creation of fetchmail-multi-drop configurations, no mailPrimaryAddress is required, because yes, with multi-drop the recipient email address comes on the envelope header. Nevertheless, a newly created and valid fetchmail-multi-drop configuration is not entered in /etc/fetchmailrc, but the same error "Adding user to "fetchmailrc" failed. Missing mailPrimaryAddress attribute in user" is logged in the listener.log.
UCS: 5.0-5 errata907 Installed: admin-dashboard=3.0 fetchmail=6.3.26 letsencrypt=2.0.0-2 mailserver=12.0 open-xchange-guard=2.10.6-ucs1 ox-connector=2.2.7 oxseforucs=7.10.6-ucs10 prometheus-node-exporter=2.0.1 4.4/prometheus=2.35.0-5 (In reply to Mirac Erdemiroglu from comment #0) > Package: univention-fetchmail > Version: 13.0.7-3 > > If the mailPrimaryAddress of a user is not available, this is now logged in > the listener.log. > > I would find it more helpful if the users were at least shown a message. > > At the moment, however, users may not even notice if there is a > fetchmail-single-drop configuration but no mailPrimaryAddress, which may > result in emails not being delivered. > > The behavior of the OX App Suite for fetchmail would be more extensive than > a hint, because a user can only be activated for the OX App Suite if a > mailPrimaryAddress exists. If a user does not have a mailPrimaryAddress, a > corresponding message appears and the user object is not saved. > > Here is the error in the bug solution: > > > For the creation of fetchmail-multi-drop configurations, no > mailPrimaryAddress is required, because yes, with multi-drop the recipient > email address comes on the envelope header. > > Nevertheless, a newly created and valid fetchmail-multi-drop configuration > is not entered in /etc/fetchmailrc, but the same error "Adding user to > "fetchmailrc" failed. Missing mailPrimaryAddress attribute in user" is > logged in the listener.log.
I have created to new bugs for the mentioned topics to address them separately and more specifically. Bug 56983 (Silently ignoring a missing mailPrimaryAddress with fetchmail-single-drop configurations may lead to emails not being delivered) Bug 56985 (fetchmail-multi-drop configurations must not be removed from /etc/fetchmailrc just because no mailPrimaryAddress is set)