We have GroupWise 2014 customers requesting have the same functionality they have with GW2012 with Dlists associated with eDirectory Groups. Note: These customers are using Dynamic Groups.
Note: We opened the next SR # 10966277091 were the support engineers suggested me to open this EH.
The maintenance event that syncs changes is called the "Default Directory Synchronization Event" as can be see in this screenshot.
https://db.tt/Aamh5Bg5
As you can see, mine is set by default to run each night at 1:00 AM and this is likely where the customers is running
https://db.tt/jBOiB3Ax
With this happening more often, we needed to create a new scheduled events and have them run during another time of the day. This would be the only way of getting it to happen more.
by: Walter L. | over a year ago | Administration
Comments
Cornell release has add the ability to set the MTA dir sync to more that once a day.
This is absolutely needed. We use the Cisco Ironport to allow only valid e-mail addresses to come in (LDAP Accept Query). With GW2012 and earlier, the eDirectory DL object had the address in the mail= attribute so it worked. BUT. With 2014, these objects are deprecated and new DLs do not automatically associate. We CAN associate manually with an AD or eDir Group object BUT when we hit Publish E-Mail, while it says it's successful, it actually pushes the address to the EmailAddress= attribute (which our accept query does not see) and the BIG problem here is that values of that attribute in eDirectory contain a leading 7#, so bob@abc.com or list123@abc.com would be 7#bob@abc.com or 7#list123@abc.com.
This makes searching infinitely MORE difficult.
We need the same kind of publishing as with a user. In eDirectory, push to mail= attribute OR if we HAVE TO use EmailAddress, can we ditch the 7#? In Active Directory, the publish ONLY puts out the primary e-mail address but does NOT populate the proxyAddress attribute which is how AD does it.
Can this be fixed such that PUBLISH to AD pushes the addresses like it would do for a user ... primary address is in proxyAddress as SMTP:list123@abc.com and all secondary e-mail addresses are smtp:list123@abcotherdomain.com
One suggestion that was made was to use the MTA LDAP server. The problem here is that this is an all-or-nothing solution with respect to e-mail address. If a user has a possible combination of 15 e-mail addresses but we only want to make two public, we cannot do that right now. So the MTA LDAP won't help us here.
Bottom line:
We would like the Publish Email to do what it does for users on both eDir and AD.