Comment 2 Daniel Tröder 2023-09-12 08:24:38 CEST

(In reply to Juan Carlos from comment #0)
> When 5.0-2 support ends we should remove the compatibility for the old
> fetchmail attributes

Please elaborate:

* What attributes should be removed? (Of what object?)
* When were they deprecated?
* Who will be affected by the removal, and how?
* Was / Is there a migration path?

Comment 3 Florian Best 2023-10-05 13:22:55 CEST

Can we really do this? Is it ensured that in the LDAP the new state is used for every existing object?

Comment 4 Juan Carlos 2023-12-21 10:28:40 CET

* What attributes should be removed? (Of what object?)

Extended attributes from user object:

univentionFetchmailServer, univentionFetchmailProtocol, univentionFetchmailAddress, univentionFetchmailPasswd, univentionFetchmailUseSSL, univentionFetchmailKeepMailOnServer

* When were they deprecated?

https://forge.univention.org/bugzilla/show_bug.cgi?id=55575


* Who will be affected by the removal, and how?
* Was / Is there a migration path?

There was a migration script when the #55575 was released.

* Can we really do this? Is it ensured that in the LDAP the new state is used for every existing object?

I have seen cases of users without fetchmail configuration but with remaining fetchmail attributes. e.g only the attribute univentionFetchmailProtocol set. This could be a problem.

Comment 5 Florian Best 2024-01-02 12:14:34 CET

(In reply to Juan Carlos from comment #4)
> * Who will be affected by the removal, and how?
> * Was / Is there a migration path?
> 
> There was a migration script when the #55575 was released.

has the migration been forced during the upgrade?

> * Can we really do this? Is it ensured that in the LDAP the new state is
> used for every existing object?
> 
> I have seen cases of users without fetchmail configuration but with
> remaining fetchmail attributes. e.g only the attribute
> univentionFetchmailProtocol set. This could be a problem.

Sound like we cannot do it.
Are the wold attributes still visible and set-able in UMC?

Comment 6 Juan Carlos 2024-02-09 11:56:39 CET

As we can't remove the attributes yet, we will:

 - Hide attributes in UMC.
 - Force the attribute migration.      
 - Notify the deprecation and future removal in the release notes.

Comment 7 Florian Best 2024-03-08 11:15:14 CET

Is this finished? Should the changed be cherry-picked to UCS 5.1 as well?

univention-management-console-module-diagnostic (8.0.7)
09098d4009f7 | feat(fetchmail): deprecate old fetchmail attributes

univention-fetchmail (15.0.3)
09098d4009f7 | feat(fetchmail): deprecate old fetchmail attributes

Comment 8 Juan Carlos 2024-04-03 12:27:57 CEST

5.1:

univention-management-console-module-diagnostic (7.0.8)
196884f7a797 | feat(fetchmail): deprecate old fetchmail attributes

univention-fetchmail (14.0.6)
196884f7a797 | feat(fetchmail): deprecate old fetchmail attributes

docs
f0abe3792600 | fixup! feat(fetchmail): deprecate old fetchmail attributes

Comment 9 Iván.Delgado 2024-04-03 13:06:17 CEST

QA:
  OK: Master/Backup scenario old attributest can be removed succesfully
  OK: Master scenario old attributest can be removed succesfully
  OK: Code review
  OK: changelog
  OK: changes in 5.1 and 5.2