|
|
|
Corrections on the last added comment:
============================== So when a user is removed from LDAP (Active Directory) and appears as inactive, but is present in QB group (which is an AD group itself), then we are not able to send build notifications to that particular group as the inactive user appears in its list. QB collects all emails and send the email in a batch to be efficient. So no easy way to solve this. However QB has a special maintenance step to remove obsolete LDAP users from QB database, and the step can be found in "Maintenance > Remove Obsolete Account Step". To use it, schedule a maintenance configuration to run this step periodically.
Hi Robin,
Please confirm the version is which this step is present. We are using version 5.0.16 and we couldn't find this step under Maintenance in QB. Hello, I am following up on this issue. I would like to know the version is which "Maintenance > Remove Obsolete Account Step" is present. We are using version 5.0.16 and we couldn't find this step under Maintenance in QB. Thanks
|
This happens in case of AD (Active Directory) groups. In our scenario, we have AD groups created, we add those AD groups to QuickBuild and provide the appropriate permissions and use LDAP authentication to provide the mapping of the login user with the AD group.
So when a user is removed from LDAP (Active Directory) and appears as inactive, but is present in QB group (which is an AD group itself), then we are able to send build notifications to that particular group as the active user appears in its list.
This is causing a maintenance overhead, as each time this issue is reported, we have to go check if there is an inactive user in the group and then have to manually delete it.
When QB is not able to send notifications, it gives below mentioned error:
Problem while sending MIME mail:
Cased by: Invalid Addresses
Cased by: 550 #5.1.0 Address Rejected.