I've published some scripts that I used to get my own virtual Mailman
setup running - the whole concept and my experiences with this are in my
blog today:
http://danielpocock.com/effectively-supporting-virtual-domains-with-mailman
Any feedback (or corrections) are welcome of course.
Regards,
I've just been looking at the wiki about the vhost patch
https://wiki.koumbit.net/VirtualMailman
It writes the aliases file in much the same way as Sympa, except the
domain comes before the list name, e.g.
Sympa: example.org-list1
Mailman+vhost patch: list1-example.org
O
Mark Sapiro wrote:
>On 07/29/2013 09:55 AM, Barry S. Finkel wrote:
>>
>> Also, as discussed previously on this list, the
>>
>> postfix-to-mailman.py
>>
>> script is NOT part of the SourceForge Mailman, and its use is
>> discouraged. There is a Mailman FAQ that describes this
>> script
On 29/07/13 17:53, Mark Sapiro wrote:
> On 07/29/2013 08:35 AM, Daniel Pocock wrote:
>> Migrating to Mailman, I'd like to do something like this:
>>
>> lists.example.org-list1:
>> "|/var/lib/mailmen/lists.example.org/mail/mailman post list1"
>>
&
I currently run virtual domains with Sympa
To get around the aliases file bottleneck and allow pure virtual
hosting, Sympa uses the virtual aliases file to map the recipients like
this:
li...@lists.example.org lists.example.org-list1@myhostname
and each of those entries is then matched
Hi,
I've been looking at whether it is possible to do pure virtual hosting
with Mailman. When I say "pure", I mean that there will be no shared
domain for the site list (that is the most important requirement for me)
and that the globally-unique list name issue will be eliminated (maybe
importan
