Univention Bugzilla – Bug 56521
resync fetchmailrc does not meet user expectation
Last modified: 2024-03-07 13:07:29 CET
The command "univention-directory-listener-ctrl resync fetchmailrc" does not resync the known single-drop and multi-drop configurations to the configuration file /etc/fetchmailrc as expected. In fact, the complete configuration is added to the configuration file and the former content remains and is completely ignored. Therefore duplicate entries will be created and in larger customer environments this result may be undetected for a while. fetchmail resync command should work like the other resync commands and check for missing and duplicate entries and correct the file. There was no indication and/or error message in the listener.log that the configuration was just dumped out to fetchmailrc. It contains in debug level 2: 04.09.23 11:55:52.797 LISTENER ( INFO ) : postrun handler: fetchmailrc (prepared=0) and 04.09.23 11:55:55.557 LISTENER ( WARN ) : initializing module fetchmailrc 04.09.23 11:55:56.809 LISTENER ( WARN ) : finished initializing module fetchmailrc with rv=0
This is not a generic UDL `univention-directory-listener-ctrl resync` issue, but specific to the implementation of the "Fetchmail" UDL module. Standard disclaimer: `univention-directory-listener-ctrl resync` must be used carefully!
Changes: The user resync does not duplciate existing entries on the file. Add test to check the listener resync Package: Package: univention-fetchmail Version: 13.0.8-2 Branch: ucs_5.0-0 Scope: errata5.0-6 Package: ucs-test Version: 10.0.20-46 Branch: ucs_5.0-0 Scope: errata5.0-6 Commits: 280f2d048d63c922944cce444be486aea3d9d0f1
QA: advisories: OK no duplication of entries in fetchmailrc after running "univention-directory-listener-ctrl resync fetchmailrc": OK new test: OK Waiting for the overnight test run
QA: no related errors in the overnight test run: OK
<https://errata.software-univention.de/#/?erratum=5.0x977>