Geoff Shang wrote:
I will review your patch, and I used list-domain.tld instead of
list.domain.tld, but I basically came to the same conclusion and just
implemented same. I got the idea from
http://mail.python.org/pipermail/mailman-users/2008-September/063254.html
This really needs to be
On Thu, 8 Oct 2009, Terri Oda wrote:
Geoff Shang wrote:
I will review your patch, and I used list-domain.tld instead of
This really needs to be documented somewhere.
And by somewhere I recommend you put it into the Mailman Wiki, probably
just add it to the FAQs:
I'll do this. I probably
Hi Mark,
re multiple installs,
On Mon, 5 Oct 2009, Mark Sapiro wrote:
The post at
http://mail.python.org/pipermail/mailman-users/2004-June/037443.html
(linked from the FAQ at
http://wiki.list.org/pages/viewpage.action?pageId=4030604) has good
information. I don't thing there's anything better
Geoff Shang wrote:
This would appear to be the sticking point. The aliases file doesn't
generate fully-qualified Email addresses, only local parts. How do I
ensure that a message to annou...@foo.com doesn't go to
annou...@bar.org? This must be doable, because if it's not, then this
defeats
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
Geoff Shang wrote:
This would appear to be the sticking point. The aliases file doesn't
generate fully-qualified Email addresses, only local parts. How do I
ensure that a message to annou...@foo.com doesn't go to annou...@bar.org?
[snip]
I
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
I have a multi setup for mailman to host multiple domains. All my list
domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'.
My mailman installations all go under /home/mailman/lists.$domain
I don't
On Wed, 7 Oct 2009, Mark Sapiro wrote:
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
= /etc/mail/aliases/$domain-aliases
mailman-lists.$domain \
|/home/mailman/lists.$domain/mail/$domain-mailman post mailman
mailman-admin-lists.$domain:\
Geoff Shang wrote:
On Wed, 7 Oct 2009, Mark Sapiro wrote:
There is still a problem in that there is a potential list name
conflict, so to resolve that, you need to make a patch (see attached
ah...
I will review your patch, and I used list-domain.tld instead of
list.domain.tld, but I
On Mon, 5 Oct 2009, Mark Sapiro wrote:
You seem to have done your homework well, and to have a good
understanding of the issues.
You can learn a lot in 5 hours of reading. :)
I found http://ndim.fedorapeople.org/stuff/mailman-vhost/ which appears
to contain the same patches that were at
On Mon, 5 Oct 2009, Mark Sapiro wrote:
I just applied the mailman-2.1.7-20060114-to-vhost.patch to the 2.1.12
base and it applied with only two rejects, both of which are easy to
fix. Whether the patched code will actually work and meet your
requirements, I can't say.
I probably can't afford
Hello,
Apologies for jumping onto the list and posting right away, I realise
it's bad netiquette.
I admin two servers for a large non-profit organisation. On Thursday, one
of them died. At the time we were using a different mailing list manager,
but had plans to gently migrate the dozens
Hello,
Apologies for jumping onto the list and posting right away, I realise it's bad
netiquette.
I admin two servers for a large non-profit organisation. On Thursday, one of
them died. At the time we were using a different mailing list manager, but had
plans to gently migrate the dozens
Geoff Shang wrote:
This is about all I know though. There seems to be much posted on the
subject. It seems it'll be in version 3, and people have asked for it to
be in version 2.2. I've seen mentions of multiple patches and multiple
versions ranging over the last 6 years or so. And the
Geoff Shang wrote
This stuff looks a bit old. It's patches against Mailman 2.1.7 and files
seem to date back to 2006. The docs talk about what's going to happen in
2008.
Does this code patch against 2.1.12? Is there newer code than this or
should I get it from git? And is there any more
Geoff Shang wrote:
Ok...This is tarting to sound doable. It also means I can get the most
important domains up quickly. Is there any documentation for doing this?
I need to have 7 lots of everything, right?
The post at
http://mail.python.org/pipermail/mailman-users/2004-June/037443.html
I've been away from the list for a while, and am curious:
Will virtual domains support be included in Mailman 2.2...if they are not
already?
By virtual domain support I mean the ability to support email lists from
multiple domains via one GNUMailman installation on one server. I manage
Matt England wrote:
I've been away from the list for a while, and am curious:
Will virtual domains support be included in Mailman 2.2...if they are not
already?
By virtual domain support I mean the ability to support email lists from
multiple domains via one GNUMailman installation on
At 1/26/2006 07:47 PM, Jim Popovitch wrote:
I run multiple lists with Mailman, been doing so since v1.1 (or was it
1.2?). Anyway, virtual domains work for me. What virtual domain problem
do you have with recent MM versions?
[EMAIL PROTECTED] and [EMAIL PROTECTED] (ie, same list name,
Matt England wrote:
At 1/26/2006 07:47 PM, Jim Popovitch wrote:
I run multiple lists with Mailman, been doing so since v1.1 (or was it
1.2?). Anyway, virtual domains work for me. What virtual domain
problem do you have with recent MM versions?
[EMAIL PROTECTED] and [EMAIL PROTECTED]
At 1/26/2006 09:09 PM, Jim Popovitch wrote:
That depends on a few things. For starters, does your MTA support
[EMAIL PROTECTED] AND [EMAIL PROTECTED]
Yes.
If it does, then you will need to use the virtualization features of your
MTA to map each list to a unique local email account.
Already
Matt England wrote:
sendmail. ** shudder **
Hey, no shudder here. I fully understand Sendmail, it works well and I
sleep good at night. YMMV.
[... rest of stuff deleted, not sure why we are talking about an MTA
if it's a Mailman problem ...but yes, I know how to get my MTA to do
this...]
Matt England wrote:
[EMAIL PROTECTED] and [EMAIL PROTECTED] (ie, same list name, different
domains, different lists/reflectors) will not work for the same Mailman
server...or at least, so I'm told.
You are correct, at least as far as the standard 2.1.x distribution is
concerned. There are some
At 1/26/2006 09:43 PM, Mark Sapiro wrote:
There are some patches around. See
http://sourceforge.net/tracker/index.php?func=detailaid=943827group_id=103atid=300103.
There is also a link to cPanel's patches at
http://mail.python.org/pipermail/mailman-users/2005-January/041748.html.
But reports from
Matt England wrote:
So the question is: is there any move afoot to change Mailman to support
same list names across multiple domains?
Yes. See http://www.list.org/todo.html.
Why can't Mailman index it's list names such that the domain name is
associated with the internal list name...thus
At 1/26/2006 10:38 PM, Mark Sapiro wrote:
The followup question (assuming the above answer...which may or may not be
a fair assumption): will this architecture ever be changed to remove this
limitation?
Yes again. I think you'll see it in Mailman 3, but as I'm sure you well
know, I can't give
I've made various runs at this without much success. For some reason I have
trouble making some of the scripts work correctly with the symbolic links;
i.e., they just plain won't follow them. Since I'm using chroot for some
of my system services, I tried using that as well, but cron goes around
26 matches
Mail list logo
