This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM 9.508-10: Recipient varification with Active Directory still not working?

Hi,

i have tried recipient verification with Active Directory, but that isn't working. I tried several ports (636, 389, 3268,3269) with Domain Controllers IP and FQDN, but i always get the following warning in the SMTP Live Log:

Warning: ACL "warn" statement skipped: condition test deferred: failed to bind the LDAP connection to server DOMAINCONTROLLERIP:636 - ldap_bind() returned -1

I can successfully test server connection and authenticate a user, but recipient verification is still not working. Any ideas?

Regards,

Frank

This thread was automatically locked due to age.

Parents

0 Ol Deda over 6 years ago

Exchange Server must be the AD server to query i think. Primary DC doesnt have information for mailboxes
Cancel
Vote Up 0 Vote Down

Cancel
0 SWeissflog over 6 years ago in reply to Ol Deda

Unknown said:
Exchange Server must be the AD server to query i think. Primary DC doesnt have information for mailboxes

This is not correct! Mailboxes are also linked with the user account in AD... This is also said in webadmin description for this feature.

We use this feature already before 9.506 so it'sworking now. We'll not update to 9.508 at the moment...

regards
Cancel
Vote Up 0 Vote Down

Cancel
0 Franky83 over 6 years ago in reply to SWeissflog

Hi,

thanks for your replies. AD recipient verification was already failing before 9.508-10. I think it has something to do with SSL settings. My domain controller is using a self signed certificate, could it be a problem, that the UTM can't validate the certificate? I don't wan't to use LDAP instead of LDAPs. Do you know a logfile on the UTM which give me a little bit more informations?

regards,

Frank
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 6 years ago in reply to Franky83

Just give it a short try, if it's working without encryption. This would give you the right direction for further steps. Some time ago UTM had problems with LDAPs.

Best

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Louis-M over 6 years ago in reply to Alexander Busch

Wasn't this a bug (on more than one occasion) and you simply re-entered the details in again and it worked?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Louis-M over 6 years ago in reply to Alexander Busch

Wasn't this a bug (on more than one occasion) and you simply re-entered the details in again and it worked?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data