System Email setup for Users will mark their Office365 emails as ready in a couple of seconds.

@martingaxiola We have the same issue, but it is not happening to everyone. I only have 1 individual reporting this as of now… 

We created several system email accounts for individuals with Incoming Mail Processing checked so that they can email (from themselves) out of Acumatica and it will be suffixed with the email tag so it captures replies, etc.

I’m not sure how to resolve either, but I just came across this issue… 

Hello @martingaxiola ,

This is not the issue, but an existing product design described in the help article mentioned.

If you have selected the IMAP protocol, every email successfully collected from the server will be marked as read on the server.

Please note that product changes and feature requests are out of the scope of Support programs. Such cases are routed to the Acumatica Feedback Portal where you can submit your idea, communicate with the Product team, and track the feature status. Shipped features and enhancements can be viewed in the Release Notes of major versions.

Hi @martingaxiola , did you receive anymore information on this? My client is having the same problem.

Hi @Irina , so is there no temporary workflow until the change is released outside of creating an email account with the POP3 protocol?

I am going to try to have a support person from Acumatica have a quick meeting for the support person to see the issue and he can replicate and be able to explain the problem. Just as FYI, this is something that happen after upgrade to 2020R2, issue keeps happening on IMAP or POP3. I will keep you guys updated on this. 

Note - as a workaround to keep processing individual users’ system email accounts, we changed the Email Tag Prefix to “[A0”, created a root folder on their email account called “ACM”, set up Outlook rules on each user to route these emails to the “ACM” folder, then pointed their system email accounts to that root folder instead of Inbox. This might not be ideal for a large number of users, however, because it required that our IT staff set up Outlook rules on each employee’s instance.

I can provide further details/screenshots if desired. 

Hey @Carynb, 

Here are the steps we took. It’s not perfect, but it got us a bit further. Our goal was:

1. Allow individual users to have a system email account for their “personal” company email while avoiding the marking of read emails in the inbox
2. Reroute Acumatica activity email traffic
3. Allow users to reply to emails in Outlook and have those replies captured in the activity record in Acumatica.

First, we created a new root folder in Outlook called “ACM”. Note: this is not a subfolder of the Inbox. Right-click the email address, select New folder. 

Next, we changed the root folder to point to the “ACM” folder in the system email account so Acumatica could process incoming mail for this folder instead of the Inbox.

Then, we changed the email tag prefix under Email Preferences in Acumatica, to “[A0”. We felt that this would be unique enough to identify and isolate the email activities that generate within Acumatica. 

Back in Outlook, we set up a rule to reroute these emails into the “ACM” folder.

We set up another rule to move replies to external emails back into this folder so Acumatica could process.

Note: the changing of the tag and custom outgoing rule was designed because we wanted users to be able to reply in Outlook for Acumatica activities, and have those replies captured back in the activity record in Acumatica. Because of that, we set up these rules directly on each individual’s Outlook instance on their computer (not on the web). You or others may not need this and can simply set up different rules, perhaps on the web. 

Also worth noting is that our users chose to live with the fact that there may be duplicate activity records if more than one individual is copied on an email. 

Hope this helps!