PostgreSQL support

[ntalfer]

Hi @axllent

Thanks for your amazing work on Mailpit.
At my company we're currently using Mailhog in staging.
We're maintaining a fork in which we added PostgreSQL support (instead of MongoDB) to leverage AWS Aurora.

We would like to move to Mailpit as it provides on awesome set of features and is actively maintained.
Sadly in-memory/sqlite/rqlite does not fit our needs.
You may already have been asked the question about adding PostgreSQL storage in Mailpit, but I didn't find any trace of it.

Would you be interested in a contribution or do you prefer to stick with in-memory/sqlite/rqlite?

Thanks!

[axllent]

Hi @ntalfer. Thanks for your suggestion. At this point I think I should state that there are no plans to introduce support for other database types. I understand that this may not be ideal for every situation, however SQLite has provided a very stable and performant database for Mailpit. To address the network-related instances, support for rqlite was added (which is also SQLite, just over a network). Also you wouldn't have found any previous references to PostgreSQL as this is literally the first enquiry I have had about that :)

I am curious however as to why you specifically need PostgreSQL / AWS Aurora support?

[ntalfer]

Hi Ralph

Thanks for your reply.
Here at Doctolib, our staging platform runs on AWS spot instances and we send up to ~400k messages/day (yeah, in staging!), db is erased every night. Spot instances can be reclaimed at any time therefore it's not convenient to use in-memory or sqlite. Our operations team is also not keen on maintaining AWS EBS volumes and have a no knowledge of rqlite. They push teams to use Aurora as it's managed by AWS.

Thank you again for your work.
We'll go with a fork. Don't hesitate to ping me if you get similar requests and change your mind, I'll be happy to contribute.

Nicolas

[axllent]

Hi Nicolas,

Whilst I'd love to support multiple database types, the reality/ irony is that there is little "standard" about "SQL" :) I have experimented with various integrations, but it really complicates things - from the schema management / database structures, to the data queries, to the search functionality. I'm not saying it's impossible, I'm saying it's a real pain to maintain properly.

Just for clarity, Mailpit does not support in-memory data - the temporary (default) just uses a temporary SQLite database which is deleted on exit - this restricts memory usage.