Bulk email download from outlook365












0















I am trying to download/access on daily basis, all the emails exchanged over outlook365 by employees of an organization, who obviously uses outlook365. After download finishes I'll be running some background jobs on these emails.



I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.



I am exploring upcoming graph as of now, to see if it helps solving this. I also have another way out by routing these emails to lets say AWS SES or apache james and accessing/downloading from there, thus avoiding throttling all together. But I am trying to avoid additional servers in deployment as of now.



My question -



Has anybody experienced this issue and what was if at all any reliable way around while using outlook supported email APIs?










share|improve this question























  • Did you checked this link: stackoverflow.com/questions/28670593/… .

    – Alina Li
    Nov 13 '18 at 2:27











  • Thanks, I have tried something similar not exact the same.

    – bhushan
    Nov 19 '18 at 12:08
















0















I am trying to download/access on daily basis, all the emails exchanged over outlook365 by employees of an organization, who obviously uses outlook365. After download finishes I'll be running some background jobs on these emails.



I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.



I am exploring upcoming graph as of now, to see if it helps solving this. I also have another way out by routing these emails to lets say AWS SES or apache james and accessing/downloading from there, thus avoiding throttling all together. But I am trying to avoid additional servers in deployment as of now.



My question -



Has anybody experienced this issue and what was if at all any reliable way around while using outlook supported email APIs?










share|improve this question























  • Did you checked this link: stackoverflow.com/questions/28670593/… .

    – Alina Li
    Nov 13 '18 at 2:27











  • Thanks, I have tried something similar not exact the same.

    – bhushan
    Nov 19 '18 at 12:08














0












0








0








I am trying to download/access on daily basis, all the emails exchanged over outlook365 by employees of an organization, who obviously uses outlook365. After download finishes I'll be running some background jobs on these emails.



I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.



I am exploring upcoming graph as of now, to see if it helps solving this. I also have another way out by routing these emails to lets say AWS SES or apache james and accessing/downloading from there, thus avoiding throttling all together. But I am trying to avoid additional servers in deployment as of now.



My question -



Has anybody experienced this issue and what was if at all any reliable way around while using outlook supported email APIs?










share|improve this question














I am trying to download/access on daily basis, all the emails exchanged over outlook365 by employees of an organization, who obviously uses outlook365. After download finishes I'll be running some background jobs on these emails.



I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.



I am exploring upcoming graph as of now, to see if it helps solving this. I also have another way out by routing these emails to lets say AWS SES or apache james and accessing/downloading from there, thus avoiding throttling all together. But I am trying to avoid additional servers in deployment as of now.



My question -



Has anybody experienced this issue and what was if at all any reliable way around while using outlook supported email APIs?







exchangewebservices office365api






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 '18 at 7:35









bhushanbhushan

1




1













  • Did you checked this link: stackoverflow.com/questions/28670593/… .

    – Alina Li
    Nov 13 '18 at 2:27











  • Thanks, I have tried something similar not exact the same.

    – bhushan
    Nov 19 '18 at 12:08



















  • Did you checked this link: stackoverflow.com/questions/28670593/… .

    – Alina Li
    Nov 13 '18 at 2:27











  • Thanks, I have tried something similar not exact the same.

    – bhushan
    Nov 19 '18 at 12:08

















Did you checked this link: stackoverflow.com/questions/28670593/… .

– Alina Li
Nov 13 '18 at 2:27





Did you checked this link: stackoverflow.com/questions/28670593/… .

– Alina Li
Nov 13 '18 at 2:27













Thanks, I have tried something similar not exact the same.

– bhushan
Nov 19 '18 at 12:08





Thanks, I have tried something similar not exact the same.

– bhushan
Nov 19 '18 at 12:08












1 Answer
1






active

oldest

votes


















0
















I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.





Inefficiency code is more likely the cause of the throttling then blaming the API (eg if your not using batching, requesting more properties then you need etc) so the first thing you should do make sure you optimize the code as all the client based API's are throttling similarly. 0.1- 1 million over the time-span of day isn't that many emails to process in my experience with EWS especially if your using Impersonation where throttling cost would be dispersed across the mailboxes your accessing.






share|improve this answer
























  • Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

    – bhushan
    Nov 19 '18 at 12:00













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257632%2fbulk-email-download-from-outlook365%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0
















I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.





Inefficiency code is more likely the cause of the throttling then blaming the API (eg if your not using batching, requesting more properties then you need etc) so the first thing you should do make sure you optimize the code as all the client based API's are throttling similarly. 0.1- 1 million over the time-span of day isn't that many emails to process in my experience with EWS especially if your using Impersonation where throttling cost would be dispersed across the mailboxes your accessing.






share|improve this answer
























  • Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

    – bhushan
    Nov 19 '18 at 12:00


















0
















I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.





Inefficiency code is more likely the cause of the throttling then blaming the API (eg if your not using batching, requesting more properties then you need etc) so the first thing you should do make sure you optimize the code as all the client based API's are throttling similarly. 0.1- 1 million over the time-span of day isn't that many emails to process in my experience with EWS especially if your using Impersonation where throttling cost would be dispersed across the mailboxes your accessing.






share|improve this answer
























  • Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

    – bhushan
    Nov 19 '18 at 12:00
















0












0








0









I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.





Inefficiency code is more likely the cause of the throttling then blaming the API (eg if your not using batching, requesting more properties then you need etc) so the first thing you should do make sure you optimize the code as all the client based API's are throttling similarly. 0.1- 1 million over the time-span of day isn't that many emails to process in my experience with EWS especially if your using Impersonation where throttling cost would be dispersed across the mailboxes your accessing.






share|improve this answer















I've option of doing this via EWS APIs, but the throttling policies are turning out to be pain and affecting the predictability of the system, because of throttling policies. Daily no of emails to be accessed could range from 0.1- 1 million or above.





Inefficiency code is more likely the cause of the throttling then blaming the API (eg if your not using batching, requesting more properties then you need etc) so the first thing you should do make sure you optimize the code as all the client based API's are throttling similarly. 0.1- 1 million over the time-span of day isn't that many emails to process in my experience with EWS especially if your using Impersonation where throttling cost would be dispersed across the mailboxes your accessing.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 13 '18 at 3:52









Glen ScalesGlen Scales

11.7k11116




11.7k11116













  • Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

    – bhushan
    Nov 19 '18 at 12:00





















  • Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

    – bhushan
    Nov 19 '18 at 12:00



















Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

– bhushan
Nov 19 '18 at 12:00







Thanks for response. Batching, reading only properties that are needed is already in place. I can't use impersonation, because I don't have list of employees beforehand with me in order to impersonate. I am going to try restricting the duration further let's say hourly instead of a day, and then introduce some delays hopefully that'll solve the issue.

– bhushan
Nov 19 '18 at 12:00




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257632%2fbulk-email-download-from-outlook365%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Florida Star v. B. J. F.

Error while running script in elastic search , gateway timeout

Adding quotations to stringified JSON object values