LDAP Object-Verification in Gateway objects
Currently it's only possible to verify against LDAP to check whether a user exists or not, it's not possible to check if it's a mail-enabled group, distributorlist or public folder. It would be great if it would be possible to define the object it will be tested against.
Rene Baumann
shared this idea
Hello again,
For anybody else that may be looking at this changing the objectclass=* fixed the issue. If you are experiencing similar issues and setting the objectclass=* does not fix it for you please contact our technical support team for assistance.
Thanks,
-
We'll do further testing and will let you know what we figure out.
-
Rene Baumann
commented
BTW I tested these queries with Softerra LDAP Browser and Microsoft LDP with both having positive match, but always dropping the connection in MDaemon gateway setup.
-
Rene Baumann
commented
Your query is quite right, I created the same filter for me, but even with a true filter it is still not working. (My opinion is that MDaemon filters for user in the ldap reply and without user it drops the connection).
I was forwarded by Excelsis (german reseller) which verified that only user queries are working in gateways and proposed to raise an improvement idea in your Idea engine
-
Rene Baumann
commented
Hi,
my usual environment is using MDaemon as a Exchange Gateway-filter. MDaemon uses an internal 'fake-domain' filtering inbound eMails. The destination system is adresses using a gateway with LDAP receipient verification.
LDAP is checked against Windows AD.
This works if the final receipient is a user mailbox, but it fails if the receipient is a distribution list or public folder.
The final error is something like 500 5.1.1 no such user (which is true, since it's a distribution list in that case). So it would be great, if the object could be changed to something else not only accepting user.