Email reader - Performance improvement
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2017 12:29 PM
Hi team!
An issue was identified with platform receiving emails. There are email accounts configured in platform but email are arriving on mailbox (in email server) and taking too long to be read by platform.
User perception: "I am receiving all email from the day at once around 5 PM (near to the end of the day)".
Is there any recommendation (or not) to configure additional "Email Reader" jobs?
Thanks in advance!
Rafael Ramos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2017 01:00 PM
I had a client that needed to read v large emails and when we used IMAP it could lock up the instance for a day
After some investigation, using POP3 and it was running absolutely fine
For that client using POP3 was not a problem,
maybe worth checking in your scenario
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2017 09:42 AM
Hi Julian!
Email accounts are configured to use POP3 protocol to read emails but the mailbox (in exchange server) are configured to use IMAP.
Next test will be done is related to mailbox change to POP3.
How about create additional "Email Reader" jobs? Any comments on this?
Thanks in advance!
Rafael Ramos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2017 08:25 AM
The issue we had was that the mail Daemon was getting stuck - it was in Fuji and Helsinki
Not sure if you can initiate more Daemons but we were reading a few mailboxes for different processes and when the Daemon got stuck, it stopped all inbound emails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2018 10:41 AM
There was a problem in earlier product families where IMAP could severely bog down some circumstances. See KB0690939. That specific issue was resolved in from Istanbul patch 10 and later.