{"id":333,"date":"2012-01-18T10:20:30","date_gmt":"2012-01-18T15:20:30","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/01\/exchange-identity-switcher\/"},"modified":"2018-03-13T10:36:30","modified_gmt":"2018-03-13T15:36:30","slug":"exchange-identity-switcher","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/01\/exchange-identity-switcher\/","title":{"rendered":"Exchange Identity Switcher"},"content":{"rendered":"

One of the most common questions that our support team receives with Hosted Exchange is \u201cHow can my client choose which email address I want to send as?\u201d and many partners are shocked to hear the answer \u201cYou can\u2019t\u201d. <\/p>\n

The above limitation has always existed in Exchange as you can only have one \u201coutgoing\u201d address. Sure, you can create another profile in Outlook and send via SMTP or create a distribution group and add send-as rights..but what do you do if you\u2019re on hosted exchange and you don\u2019t have the freedom to control addresses and configurations at will or find it rather rudimentary? <\/p>\n

*Drum roll*<\/b> <\/p>\n

Now you can\u2026 <\/p>\n

For the first time (as far as I can tell for any hosting provider) partners\/clients will have the ability to control their outgoing address in our Hosted Exchange. <\/p>\n

Utilizing our API and a brand new API designed by the ExchangeDefender team for direct client Exchange interaction we now can extend the ability for clients to control their outgoing address on the fly. <\/p>\n

The current beta product is a windows based application and will soon be converted to an Outlook 2010 plugin. <\/p>\n

<\/p>\n

If you or your clients are interested in test driving this software please reach out to me directly: travis@ownwebnow.com<\/a>. <\/p>\n

Note:  This only applies to rockerduck.<\/em> <\/p>\n

Travis Sheldon
VP, Network Operations, ExchangeDefender
(877) 546-0316 x757
travis@ownwebnow.com <\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,8],"tags":[],"class_list":["post-333","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-hosted-services"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/333","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=333"}],"version-history":[{"count":1,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/333\/revisions"}],"predecessor-version":[{"id":1368,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/333\/revisions\/1368"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}