{"id":7,"date":"2006-11-02T21:25:18","date_gmt":"2006-11-03T01:25:18","guid":{"rendered":"http:\/\/www.ownwebnow.com\/blog\/2006\/11\/exporting-exchange-smtp-addresses\/"},"modified":"2006-11-02T21:26:46","modified_gmt":"2006-11-03T01:26:46","slug":"exporting-exchange-smtp-addresses","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2006\/11\/exporting-exchange-smtp-addresses\/","title":{"rendered":"Exporting Exchange SMTP Addresses"},"content":{"rendered":"<p>One of the most common Exchange questions we get is <em>\u201cHow do I export all the SMTP addresses on my Exchange server?\u201d<\/em><\/p>\n<p dir=\"ltr\">First of all, SMTP addresses are part of the User object in the Microsoft Active Directory. Active Directory is an LDAP-based database and by using LDIF (LDAP Data Interexchange Format) you can run queries against this database. You can use <a href=\"http:\/\/support.microsoft.com\/kb\/237677\">ldifde<\/a> to accomplish this.<\/p>\n<p dir=\"ltr\">The following ldifde syntax will export the proxyaddress list for each user object in the directory on the server SERVERNAME.DOMAIN.TLD:<\/p>\n<blockquote style=\"margin-right: 0px\" dir=\"ltr\"><p>ldifde -f C:\\DATA.ldf -s SERVERNAME -d &#8220;dc=DOMAIN,dc=TLD&#8221; -p subtree -r &#8220;(objectClass=user)&#8221; -l &#8220;cn,proxyaddresses&#8221;<\/p><\/blockquote>\n<p dir=\"ltr\">\n<p dir=\"ltr\">The data is then dumped in C:\\DATA.ldf. But suppose your server name was SBSBOX.MYDOMAIN.LOCAL. The syntax changes to:<\/p>\n<blockquote style=\"margin-right: 0px\" dir=\"ltr\">\n<p style=\"margin-right: 0px\" dir=\"ltr\">ldifde -f C:\\DATA.ldf -s sbsbox -d &#8220;dc=mydomain,dc=local&#8221; -p subtree -r &#8220;(objectClass=user)&#8221; -l &#8220;cn,proxyaddresses&#8221;<\/p>\n<\/blockquote>\n<p style=\"margin-right: 0px\" dir=\"ltr\">If you open it up with notepad you\u2019ll see a number of entries in this file:<\/p>\n<blockquote style=\"margin-right: 0px\" dir=\"ltr\">\n<p style=\"margin-right: 0px\" dir=\"ltr\">dn: CN=Administrator,CN=Users,DC=MYDOMAIN,DC=LOCAL<br \/>\nchangetype: add<br \/>\ncn: Administrator<br \/>\nproxyAddresses: smtp:Administrator@MYDOMAIN.LOCAL<br \/>\nproxyAddresses: SMTP:Administrator@mydomain.com<br \/>\nproxyAddresses: smtp:postmaster@mydomain.com<br \/>\nproxyAddresses: X400:c=US;a= ;p=MYDOMAIN;o=Exchange;s=Administrator;<br \/>\nproxyAddresses: smtp:postmaster@MYDOMAIN.LOCAL<\/p><\/blockquote>\n<p style=\"margin-right: 0px\" dir=\"ltr\">Nothing very private in here, just the display name and a few containers along with the proxyAddresses. Now another interesting bit \u2013 notice how there are both SMTP and smtp addresses here? What is the difference you may wonder? SMTP is the default <em>SMTP<\/em> address and <em>smtp<\/em> are the additional addresses and aliases.<\/p>\n<p style=\"margin-right: 0px\" dir=\"ltr\">The process is quick and convenient but unfortunately it does not export proxyAddress attributes from other objects such as distribution lists and public folders. For that you can use a <a href=\"http:\/\/www.ownwebnow.com\/blog\/media\/ExportAddresses.vb\">third party script<\/a>, such as <a href=\"http:\/\/www.ownwebnow.com\/blog\/media\/ExportAddresses.vb\">this one<\/a> that our friend emailed over. Simple vbScript that will create a list of users and addresses in C:\\EmailAddresses.txt.<\/p>\n<p style=\"margin-right: 0px\" dir=\"ltr\">Pick your way but as you can tell, exporting SMTP addresses in Exchange is a piece of cake.<\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-7","post","type-post","status-publish","format-standard","hentry","category-exchangedefender"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/7\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=7"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=7"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}