Re: [gentoo-server] Mailing List Manager that does not need to integrate tightly with the mail server?

[Brian Kroth <bpkroth@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

Pandu Poluan <pandu@poluan.info> 2011-05-25 21:31:
> On Wed, May 25, 2011 at 13:22, Pandu Poluan <pandu@poluan.info> wrote:
>> Okay, the CEO of the company had just asked me to set up a 'proper
>> mailing' list.
>>
>> For reasons too long to describe here, we've been running with
>> hMailServer on Windows Server 2003. Unfortunately the 'distribution
>> list' facility on hMailServer is, to put it mildly, lacking.
>>
>> hMailServer is scriptable, but rather than reinventing the wheel, I
>> guess I'll just create another GentooServer VM to handle this.
>>
>> Now, for this purpose, I'm looking for a Mailing List Manager that
>> fulfills the following requirements:
>>
>>  * Does not need access to the email spool directory
>>  * Does not need to integrate with the mail server, but can act as a
>> POP3 / IMAP client -- or --
>>  * Can act as an SMTP server (so that I can employ fetchmail to
>> actually perform the mail-pulling)
>>  * Support basic mailing list management commands (subscribe + unsubscribe)
>>  * Performs mail header mangling (e.g., prefixing Subject: with [ListName])
>>  * Allows for one-way (e.g., announcement-only) mailing list
>>
>> *Not* required are:
>>
>>  * Web-based management
>>  * Mail archival system
>>  * Integration with Active Directory and/or LDAP
>>
>> Can anyone recommend something that fits my need?
>>
>
>> From: Ramon van Alteren <ramon@vanalteren.nl>
>> Date: 2011-05-25 19:16
>
>> mailman ?
>
> Doesn't mailman require access to the mail spool dir?
>
> Or am I reading the docs wrong... @_@
>
> Rgds,

No, it has its own spooling system.  You just have to setup aliases in 
sendmail (or your mda of choice) to deliver to the mailman delivery 
program with the appropriate arguments.  Mailman should then turn around 
and submit new message back out to the list members again using your 
local msa mechanisms.

Brian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]