What Changed in the New Frappe Mail and Mail-Server?

[edardev]

Question: What Changed in the New Frappe Mail and Mail-Server?

I’m a bit confused about the recent changes to Frappe Mail and Mail-Server:

• Frappe Mail
• Frappe Mail-Server

Was there a major architectural change as well? I know it still in development mode and not prod ready I guess.

Would appreciate any insights—thanks!

[Sagar_Sharma]

There have been mostly architectural changes. The previous setup was easy to manage and performance-efficient but was difficult to set up and maintain due to multiple repositories. Previously, we used Haraka MTA for SMTP, which retrieved messages from a RabbitMQ cluster for delivery and processed inbound emails in reverse order. Now, we have switched to the Stalwart Mail Server, using SMTP for message submission and IMAP for retrieving received emails. This transition consolidates everything into a single repository (frappe/mail) for Frappe Mail, simplifying maintenance.

[edardev]

@Sagar_Sharma

There have been mostly architectural changes. The previous setup was easy to manage and performance-efficient but was difficult to set up and maintain due to multiple repositories. Previously, we used Haraka MTA for SMTP, which retrieved messages from a RabbitMQ cluster for delivery and processed inbound emails in reverse order. Now, we have switched to the Stalwart Mail Server , using SMTP for message submission and IMAP for retrieving received emails. This transition consolidates everything into a single repository (frappe/mail) for Frappe Mail, simplifying maintenance.

I really like this new architectural approach! Leveraging other open source projects with Frappe integration enhances scalability, performance, and security. Consolidating everything into a single repository makes maintenance more efficient while still allowing for flexibility and future improvements.

Is this setup ready for production use, or is it still in the testing phase?