On Fri, Mar 30, 2018, at 1:13 PM, Abhilash Raj wrote:
On Fri, Mar 30, 2018, at 12:00 PM, Chris McMacken wrote:
Thanks for the prompt response.
Why does the application store messages on the local disk?
It is how our queuing system is built, every queue is stored on disk and messages in intermediate states like when being processed or decorated inside Mailman Core as stored on disk. *Most* of these isn't the problem, since the emails are sent out pretty fast, it's the held messages waiting for approval or broken messages in the shunt queue that would be lost and is what I mean by "State" mostly.
AFAIK API being served by different instances will affect what and how many held messages are reported.
I'm guessing it's for performance reasons but wanted to ask. Do you have any plans to add database storage for these at some point in the future?
And No, currently we don't have any plans to tinker with the queuing system in near future. It works very well right now and is quite fragile, one single bug in queuing/accounting of emails and you can bomb your subscribers with 1000s of emails or important emails being swallowed up.
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in
-- Abhilash Raj maxking@asynchronous.in