Documents are created from IMAP only when emails are UNREAD

[michalls01]

Document creation via Email is not working for all emails after upgrading to V14 (it works flawlessly on the V13 running in parallel). Both sites are connected to Office 365, no errors in the Error Log. Sending of emails is working fine on both sites. Both sites are hosted on Frappe Cloud.

[git-avc]

¿Are this emails marked as "read" in O365?

[michalls01]

@git-avc Hello, it seems that documents are created from IMAP emails only when the email is unread, even though the "Email Sync Option" setting is set to "ALL". This only applies to V14 (since we have multiple Erpnext instances connected to the same mailbox, when an email is synchronized, its marked as read and thus not synchronized in another Erpnext instance). Also, when users access the mailbox directly and mark an email as read, it is not synchronized.

Thank you for the hint!

[git-avc]

Yes, we face the same issue with O365

[trustedcomputer]

I encountered the same issue after upgrading to V14. I have since reverted to V13 for production but I still have the old V14 VM lying around. I saw both issues of the emails getting marked "read" on the server side as well as only downloading if the mail was unread on the server side. This was with self-hosted HCL Domino as the IMAP server. In my troubleshooting, I narrowed it down to somewhere in the code for uidvalidity. But it was beyond me how to track it down further. I had a workaround for the emails being marked read on the server. I could try to dig that up if you are interested. But really it needs to be looked at by someone with some in-depth knowledge of the IMAP protocol.

[khanhtranchi]

Hi @michalls01 @put3r-r00t3r,

I have same problem too with postale.io

Does the v13 is stable than v14 ? Because I'm need to apply this system to my company, so I think the v14 is the upgrade version, will less bug than v13, but how the error of old function like email occurs :(. Would you suggest me in advance ?

Thanks so much.

[trustedcomputer]

@khanhtranchi In my opinion and experience, v13 is more stable than v14 because its new features have had more time to have the bugs worked out, whereas the new features in v14 have not.

For example, the separation of the HRMS and Payments modules into their own apps that happened in v14 still has problems, the HRMS app just recently made it to version 1.0.0, and the Payments app when installed shows itself as 0.01, development.

As another example, there is the issue of the breadcrumbs for many of the sales items like Sales Order, Sales Invoice, Quotation, etc.... that show as part of the Retail module such as "E > Retail > Sales Invoice" in the top left of the screen instead of "E > Sales > Sales Invoice".

Also, I was never able to get some of the ERPNext Integrations like GoCardless working in v14, but it worked perfectly going back to v13.

Not to mention this issue about the emails being marked as read on the server when fetched as well.

[IgorA100]

Many months have passed, but the problem is not solved on version 14 :(
I still have this problem.
ERPNext: v14.20.3 (version-14)
Frappe Framework: v14.31.0 (version-14)