Jacek Sałacki

Ian Hawkins, thanks for your questions. 

1. Managing connectors through API -  such functionality is not on our roadmap at this moment. However, your comment will help us to decide about future of Exchange Connector. 

2.  Exchange Connector will pickup all unread emails that are available in the main inbox of your email address. So, cleanup depends on your configuration (i.e. what you are doing with an email after it is forwarded). While Zendesk has a mechanism to prevent duplication of tickets it may not always work 100% due to complexity of email protocols. 

Ian Hawkins , thanks for your comment.

At this moment the best approach is to convert shared mailbox into regular user account or generate credentials for shared mailbox. And use this account or credentials to connect Zendesk with mailbox. 

In fact this approach is more robust, because such connection is not dependent on any personal account credentials. 

Christopher Spitler thanks for that comment. 

We are not preventing any type of mailboxes to connect using Exchange Connector, until one can log-in using as a user associated with that mailbox. For shared mailboxes it means that you would need to create credentials for this mailbox and use those credentials while creating connection. 

Shaun Murray 

connections are set up per each email address separately. So, you may have, for example

support@yourdomain.com configured with forwarding method 

billing@yourdomain.com  configured using Exchange Connector. 

When it comes to MFA, it is transparent for us. Exchange Connector uses OAuth to get authorisation to access Exchange mailboxes. 

Can you give an indication of when this will move from EAP to production? 

At this moment we are not able to share any exact date. However this functionality is under heavy testing and developing, we should be able to share more information soon.  

Curtis Morissette thanks for your comment. Shared mailboxes are important topic for us while building Exchange Connector. To address that well we would like to learn about specific use cases and scenarios related to shared mailboxes and other functionalities related to Exchange Servers. Let me move our discussion to private channel, I'll reach to you through email. 

Hi Willem Auret 

We are still interested in discussing that case. I just reached to you through email, let's move our further discussion to that channel . 

Firehose API is ment to be used as a continuous stream of data from Sell in near real-time. What you are looking for is Sell Core API

Firehose API retains data from last 72 hours. If you try to access position from 4 or 5 days ago it is gone. This indicates 410 HTTP error code.