Thanks Kevin, that seems to do the trick. However in my environment (a school district) for some time now email addresses have taken 2 forms: [EMAIL PROTECTED] And [EMAIL PROTECTED]
So using LDAP it lets in messages addressed to @domain but NOT to @mail.domain. Can I tweak the filter to look for only the username part of the address to get around this? I tried LDAPFilter = proxyaddresses=smtp:USERNAME but that fails on either now. Clearly I don't understand the syntax and meanings of these settings, maybe it can't be done or more things need to be changed. Any suggestions? Thanks, Geoff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sent: Monday, July 09, 2007 12:14 PM To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy Subject: Re: [Assp-user] Help setting up ASSP LDAP validation Geoff Varney wrote: > Hi, > Can someone help me with setting up LDAP in ASSP to validate recipients? I > am working on setting up a new Exchange 2007 server and am not sure how to > get it to query in the proper way. My DCs are Windows 2003. Sure, see below. > I saw a post by Kevin from June 13 (Re: [Assp-user] SPAM-LOW: Re: > Smartermail) where he had planned to post instructions to the wiki (don't > know if this would deal specifically with MS AD or not) but I can't find > anything about this. It was referencing SmarterMail only, for the record it does not expose all it's email addresses via LDAP, it sucks. > Where I need help is how to configure the entries for a single domain > environment. I tested this briefly sending to a valid address and got > rejected. There was an error 89 generated in the maillog, which suggests a > configuration error. I saw another post where someone had this happen > trying to check against Novell eDirectory with the same error. Is it even > possible to talk to MS with this anyway? I'm running exchange 2003, with a 2003 Native Domain. These are the settings I'm using right now. User accounts and Domains are funny validated with LDAP, i don't use the flatfiles for anything but some non AD accounts. The 'ldapLookup' user is a normal account, no admin rights are needed. ---LDAP Setup --- LDAPHOST : 192.168.1.*** LDAPLogin : CN=ldapLookup,OU=Admins,OU=UserAccounts,DC=DOMAIN,DC=LOCAL LDAPPASSWORD : LDAP Password: *******(yeah right) LDAPRoot : LDAP Root container: DC=DOMAIN,DC=LOCAL You have to use the AD domain root if you are using mail enabled Public Folders. ldLDAPFilter : proxyaddresses=smtp:[EMAIL PROTECTED] LDAPFilter : proxyaddresses=smtp:EMAILADDRESS The filters are CaSe SenSITive. :) Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
