> If I enter 'ou="Tech Department",...' I get the message Object not > found. . .
As spaces are totally legit in LDAP without any escaping (except at the beginning or end of URIs--but who's going to do that on purpose?), the "most correct" reference in LDAP terms is to leave out all single/double quotes and just stick with the plain string: OU=Tech Department,OU=Admin Building,DC=example,DC=com However, there's an outstanding bug in exchange2aliases itself: it doesn't parse arguments with embedded spaces. Force-escaping the spaces themselves should help, though: OU=Tech\20Department,OU=Admin\20Building,DC=example,DC=com Note to anyone else who's listening: this will also solve the problem of grabbing mail-enabled public folders from the space-ridden system area: CN=Microsoft\20Exchange\20System\20Objects,DC=example,DC=com --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.mailmage.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.mailmage.com/products/software/freeutils/exchange2aliases/download/release/ http://www.mailmage.com/products/software/freeutils/ldap2aliases/download/release/ --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
