Hi Quan!
Thanks for the initiative of the follow up!
> To have a look at the planned tickets, please visit
https://github.com/linagora/james-project/issues.
We cannot expect people from the community to read a Linagora specific
bugtracker
IMO we should sum up the planned tickets for JMAP
Hi everyone,
This is another follow-up to our recent work on the Postgres topic.
In the last sprint:
- We migrated fully JPA code to Postgres. No more JPA code in the
postgres-app now. So at this moment, we had a fully functional IMAP server
on top of Postgres.
- We solved the flags concurrently
Hi everyone,
Yet another following up on our recent Postgres work.
In the last sprint, our team successfully migrated the mailbox core module
`apache-james-mailbox-postgres` fully from JPA to Postgres. We did some
performance tests with the IMAP server backed by Postgres-app and the
result was
Thanks for the write up Quan!
I would add that we shall rights ADRs about important decisions on the
PostgreSQL implementation.
So far I identified...
- table structure for the postgresql mailbox
- how deletes are handled
- concurrency control for flag updates
Those ADR would be opened
Hi everyone,
This is a follow-up on the Postgres implementation topic. We have been
working on this topic for a while and your feedback and expertise about
Postgres would be helpful :-)
For short:
- On the progress: We have implemented the SubscriptionMapper,
UsersRepository, DomainList, and
Hi Benoit,
This topic has been discussed for years, I'm happy you finally draw a plan for
it.
To me, the aim for Postgres is small to middle size deployment with minimal
dependencies.
In that regard, having an implementation that spans across all infrastructure
needs is a must have.
So my
I somehow messed up my email config and the following message never reached
the list (but never got a nack either so it took me a week and 2 emails
without response to detect the problem)
Hello Benoit
I think having a postgresql backed mailbox server sounds great
It should not come as a
great job fact-checking this assumption, at least with smoke tests...Envoyé
> depuis mon appareil Galaxy
> Message d'origine De : Wojtek Date :
> 10/10/2023 16:05 (GMT+07:00) À : James Developers List
> Objet : Re: Building a PostgreSQL mailbox for
> James? H
Developers List Objet : Re:
Building a PostgreSQL mailbox for James? Hi Benoit,Please see comments below.On 06/10/2023 23:48, Benoit TELLIER wrote:> Hey there!> > The goal: deliver James "stateless
email server" concept to smaller deployments than those addressable with the
make great job fact-checking this
assumption, at least with smoke tests...Envoyé depuis mon appareil Galaxy
Message d'origine De : Wojtek Date :
10/10/2023 16:05 (GMT+07:00) À : James Developers List
Objet : Re: Building a PostgreSQL mailbox for
James? Hi Benoit,Please see
make great job fact-checking this
assumption, at least with smoke tests...Envoyé depuis mon appareil Galaxy
Message d'origine De : Wojtek Date :
10/10/2023 16:05 (GMT+07:00) À : James Developers List
Objet : Re: Building a PostgreSQL mailbox for
James? Hi Benoit,Please see
Hi Benoit,
Please see comments below.
On 06/10/2023 23:48, Benoit TELLIER wrote:
Hey there!
The goal: deliver James "stateless email server" concept to smaller deployments
than those addressable with the Distributed server.
Why Postgres? Rock solid. And more options than other SQL stores
Hey there!
The goal: deliver James "stateless email server" concept to smaller deployments
than those addressable with the Distributed server.
Why Postgres? Rock solid. And more options than other SQL stores (see below)
The requirements would be:
- Leverage the blobStore for binary storage
13 matches
Mail list logo
