Mark Sapiro wrote:
(...)
> To elaborate a bit, as Brad says, you need to have a web server and MTA
> running. Other than that, there is no constant, even when idle, memory
> usage by Mailman to support the web interface or incoming mail.
> Incoming mail causes the MTA to invoke the mail wrapper w
Brad Knowles wrote:
>Tomasz Chmielewski wrote:
>
>> Is it possible to minimize the memory usage by only running some parts
>> of mailman (i.e., I only want the archive be viewable via the web
>> interface).
>
>I don't think you're going to cut down those memory requirements by much,
>at least not
Tomasz Chmielewski wrote:
> I'm trying to run mailman 2.1.8 on a system with only 32 MB RAM (and
> ~100 MB swap).
I think that's unlikely to work well.
> However, it fails to start - the system swaps very heavily, and then
> mailman gets killed by the kernel.
I'm not surprised.
> Without mailm
> >From your description, I am guessing that you are doing some time
> consuming validation on SMTP transactions in your outgoing MTA and
> OutgoingRunner is hopelessly backlogged. If this is the case, it
> should be obvious from a detailed look at Mailman's 'smtp' log. If
> you're seeing SMTP for
I'm trying to run mailman 2.1.8 on a system with only 32 MB RAM (and
~100 MB swap).
However, it fails to start - the system swaps very heavily, and then
mailman gets killed by the kernel.
Without mailman started, the system uses about 12 MB RAM.
What are the minimal memory requirements for ma
