PoshLook
PoshLook copied to clipboard
itadder
[Question] Connection to Outlook?
How to you Plan to Connect to Outlook? Is Using the Outlook Interop Assemblys okay?
Checkout the out the #poshlook slack channel on powershell.slack.com for active development and discussion of Poshlook. I will be hanging out here a lot while working on Poshlook. You can still add issues if you want to the issues tracker for this repo.
Using the REST API might be worth looking into. Consumption could be done with code that works in PowerShell on Linux and Mac.
https://docs.microsoft.com/en-us/outlook/rest/
I will check this out, for now I am looking at EWS API as it supports on perm. Do you of the rest API supports On Perm Exchange aswell. I want to be able to support both on perm and office 365.
Looks like only Exchange 2016. Might not be the best approach if you're looking for backwards compatibility.
https://blogs.technet.microsoft.com/exchange/2016/09/26/on-premises-architectural-requirements-for-the-rest-api/
The most interoperable method would be to use EWS or the Outlook PIA. I would lean towards EWS as the PIA is more directed at interacting with Outlook. The REST API is mostly useless at the moment, but is promising for the future.
So having initially thought out this project I really wanted to actually write up the module to use pop/imap to keep it more open to call the mailboxes but just haven't had time or energy or drive to do this. It was more a thought to build this as an alternative to Outlook not to ONLY work for outlook On Mon, Jun 5, 2017 at 9:01 AM Brandon Andrews [email protected] wrote:
The most interoperable method would be to use EWS or the Outlook PIA. I would lean towards EWS as the PIA is more directed at interacting with Outlook. The REST API is mostly useless at the moment, but is promising for the future.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/itadder/PoshLook/issues/11#issuecomment-306181094, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgvXPCURBmJmLW7D9lUOLR2D2FvtCvuks5sA_t4gaJpZM4No5Rd .
I hear what you're saying, but supporting EWS in the first go round is probably a higher use case than supporting POP/IMAP. Given the target audience of PowerShell and the target audience of this, there is a high overlap with those people who will use this at their jobs, which most likely run Exchange and Outlook. There are plenty of great apps that handle POP/IMAP, but none that handle EWS well aside from Outlook.
The point wasn't to manage anything it was an alternative to a terminal based mail client On Mon, Jun 5, 2017 at 11:48 AM Brandon Andrews [email protected] wrote:
I hear what you're saying, but supporting EWS in the first go round is probably a higher use case than supporting POP/IMAP. Given the target audience of PowerShell and the target audience of this, there is a high overlap with those people who will use this at their jobs, which most likely run Exchange and Outlook. There are plenty of great apps that handle POP/IMAP, but none that handle EWS well aside from Outlook.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/itadder/PoshLook/issues/11#issuecomment-306223936, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgvXLrq4DR-aiPSbsw-JGQ8uD65FYBCks5sBCMzgaJpZM4No5Rd .
I am for now going to stick with ews and imap for future feature. I want to get one feature perfected first, that is display email in a outlike fashion on the CLI.
