it very nice news and thanks for all efforts
The git is not really clear. What is it you are trying to accomplish with this change?
the goal for the email inbox is for users to have an email inbox within frappe with emails linked to customers and suppliers and general docs
aswell as transparency to allow users to see all communications between a peticular supplier
5 Likes
It is really a very good job. When it will be ready for use.
1 Like
Ok, so this makes sense. How do you separate a frappe “inbox” with linked communications to various documents in the platform with regular inbox emails that don’t need to be inside frappe?
currently there isnt a means to sort out the unessicary emails it’s designed as a full inbox like outlook and will sync read and unread
we are certainly open to idea’s
i am thinking maybe blacklisting some emails but the email syncing is designed to get all emails in ure inbox
Hii Robert
I am trying to open the email inbox in beta version but it is not responding
hi @dufani1
the beta demo is not currently configured for the inbox to work will add to the list
3 Likes
Hello
Thanks @RobertSchouten and @IAGAdmin , it’s great job .
i think should make email id unique in ERPNEXT , so can’t enter one email address for to contact ( supplier , customer , or lead ) .
i don’t know how you are going to manage contact with more than one email ID .
Thanks all ERPNEXT team .
Regards
Ok. So I am getting a better sense of what you are trying to do here. I would suggest the work being done is to better integrate with POP3, IMAP and MAPI based mailboxes so you can get mails from pretty much every platform out there, including MS Exchange. I would suggest that in the integration, you don’t attempt to replace an email client like Outlook as that is simply a lot of work. I think it would be better to enable ICS integration with the frappe calendar so I can attach it to my Outlook client (or gmail for that matter) and then use a custom smtp header in the messages. Then as frappe is scanning my mailbox for emails to process, it looks at the custom header to know what to pull into frappe and what to ignore.
From a workflow perspective I would think that the frappe user is initiating emails from within the platform and not Outlook or another email client, so frappe can insert the header at that time. It will then get carried in all replies and can be reinserted if needed in any replies to the replies, etc. Then you can separate regular corporate emails from those that could be associated with conversations that are occurring within documents in frappe/erpnext and I can continue to use whatever email client I want to use. Mac users might prefer iMail for example, so again the more frappe integrates with standard mailbox and calendar protocols the more useful it becomes and you don’t have to try and recreate all the features of an email/groupware client in frappe.
My $0.02 for what its worth.
the issue with that is what if it’s a customer sending the first email theres no way to modify the header for frappe to know it’s meant to be recieved
yeah it sure was a lot of work and it’s not going to force users 2 stop using outlook or imail it’s just an alternative
2 Likes
Great news!
Thanks @RobertSchouten, @IAGAdmin and everybody working on integrating this feature!
1 Like
please Robert
what dose awaiting password mean in email setting?
regards,
hi @dufani1
awaiting password is for accounts u dont know the password for so when u assign the account to a user the user will b prompted for a password for the account
but maybe the label should be “prompt assigned user/s for password”
1 Like
Thanks Robert
I think the lable shold be ( Password will assign by user)
Hello guys, @RobertSchouten, @IAGAdmin, @rmehta, and others
I just saw ‘hiri’ email client, and it has a nice workflow, that can may be integrated in the new inbox.
ERpnext already has all the parts built-in, but maybe not yet glued together in a nice workflow.
SEND TASKS TO YOUR TEAM
Send actionable emails and delegate others to your team. Sending tasks using Hiri reduces ambiguity about who needs to do what.
@pee, you mean to integrate Hiri into Frappe Framework? I can’t see how that would be possible with Hiri being closed source proprietary software, but maybe I misunderstood your idea.
Moreover, they support only Microsoft-based email services, which also doesn’t look like a nice approach.
1 Like
@strixaluco, I refered to hiri for inspiration on email useability and best practices (and certainly not for their code!) 
See the video link on how they handle email conversations and delegations.
For example the use of ACTION and FYI fields. The ACTION emails can then be automatic converted to erpnext’s TODO’s for example.
So I refer to the workflow they are using, that’s seems nice,
and IF the new inbox does not have that functionality yet,
then maybe it is a good idea to implement that kind of workflow in erpnext new inbox.
1 Like
Sorry, probably I read your message too fast
Yes, the workflow is pretty nice, but before implementing similar workflow in Frappe, it’s better to check if there are no any patents on it.
@strixaluco, It is just a workflow, and the reason why I liked it, is that I adopted this workflow myself years ago, by tagging my work emails with ACTION or FYI, so the person receiving it knows if he needs to do something or just read/ignore the email.
I read this principle many many years ago in a book about good management practices used at succesful companies. I am not sure, but I think it was the method used by Jeff Bezos at Amazon, but again I could be wrong.
Anyway I doubt there are any patents on this because lots of people already use this for years.