LDAP, Barracuda, and hierarchical names

HCL Domino Domino Forum
1

My Barracuda spam firewall will resolve all aliases except hierarchical names using Domino’s LDAP. Any name I use in the “User name” field in the address book works except for the hierarchical name. Apparently the “/” character is the problem?

testaccount@mydomain.com

works but

testaccount/xyz@mydomain.com

fails when the Barracuda (or another spam filter I use) checks the name in LDAP.

I have put a lot of time trying to figure this out but nothing seems to work.

Ideas? Is the “/” character something special in LDAP?

Thanks for any help.

2

Subject: LDAP, Barracuda, and hierarchical names

Hi,

The ‘/’ isn’t special in LDAP, it’s special in Notes/Domino though and things can get tricky when translating names back and forth.

Is Barracuda trying to look up names in Domino LDAP, or is there a 3rd party LDAP (e.g., Active Directory) involved in this mix?

+josh

3

Subject: RE: LDAP, Barracuda, and hierarchical names

Hi Josh,

Thanks for the response, hope you can help.

Yes, the Barracuda is trying to look up the name in Domino LDAP as I have some email coming from the outside to the hierarchical name addresses. My other spam filter exhibits the same behavior.

I have contacted IBM/Lotus support and they can reproduce the problem but haven’t found a solution yet. I have tried a lot of things without success and I’m thinking there is going to have to be some kind of custom LDAP rule employed to make this work.

  • Richard
4

Subject: RE: LDAP, Barracuda, and hierarchical names

Hmmm…

You really need to turn on debug for the Domino LDAP server to figure out what in the heck Barracuda thinks it’s looking for.

Set this INI variable: LDAPDEBUG=7

Send a test mail in that’s addressed to a hierarchical-style e-mail address and paste the debug back here so I can see what search filter Barracuda is sending.

+Josh

5

Subject: RE: LDAP, Barracuda, and hierarchical names

The problem is with the Barracuda and I have an open support case with them, no fix yet. It indeed has a problem with the "/’ character tho.

I have enabled LDAP successfully on my IronPort appliance, so I know it works now.

Main thing I had to do was to put lookup addresses in the Short name/UserID field and using the query string (uid={a}) on the appliance. Got this working with the helpful folks at IBM/Lotus support.