Martin N Brampton wrote:
>
>The simplest and immediately effective (I've done it!) solution is the
>hack to admindb.py.
I'm glad that's working for you. I'm not sure why this is an absolute
URL in the Mailman base. There are many things in Mailman that have
"always been that way", and since I do
Thanks very much for the various suggestions. Sorry I evidently didn't
make it immediately clear that the servers are not all on the same IP
address. Use of reverse proxy should work, although I'd prefer to avoid
loading mod_proxy if possible, to avoid having to think about ensuring
it is sec
Martin Brampton wrote:
>I'm running Mailman 2.1.13 from the Debian Squeeze repositories (on
>Debian Squeeze) to provide mailing lists across several domains. The
>domains that are not the primary mailing list domain have 301 redirects
>of URLs such as .../listinfo/ or .../admin/ to the
Martin Brampton wrote:
>I'm running Mailman 2.1.13 from the Debian Squeeze repositories (on Debian
>Squeeze) to provide mailing lists across several domains. The >domains that
>are not the primary mailing list domain have 301 redirects of URLs such as
>.../listinfo/ or .../admin/ to th
On Mon, Sep 05, 2011 at 04:41:18PM +0100, Martin Brampton wrote:
> I'm running Mailman 2.1.13 from the Debian Squeeze repositories (on
> Debian Squeeze) to provide mailing lists across several domains. The
> domains that are not the primary mailing list domain have 301 redirects
> of URLs su
I'm running Mailman 2.1.13 from the Debian Squeeze repositories (on
Debian Squeeze) to provide mailing lists across several domains. The
domains that are not the primary mailing list domain have 301 redirects
of URLs such as .../listinfo/ or .../admin/ to the primary domain.
In most c
Peter Russell wrote:
>Mailman wants to use [EMAIL PROTECTED] when it should be
>[EMAIL PROTECTED]
>
>Using the web interface, (http://www.my.domain/mailman), whichever option I
>select, it requests a page starting
>
>Http://server1.my.domain..
>
>If I manually change 'server1' to 'www' it wo
Peter Russell wrote:
> I just installed Mailman and it seemed to setup ok, until I tried to
> create a new list using the web interface.
>
> I'm running Fedora Core 3 with all the correct versions of Sendmail,
> Python,
>
> Apache and Mailman.
>
> My machine name is server1.my.domain
>
> My web
I just installed Mailman and it seemed to setup ok, until I tried to create
a new list using the web interface.
I'm running Fedora Core 3 with all the correct versions of Sendmail, Python,
Apache and Mailman.
My machine name is server1.my.domain
My web page is www.my.domain
All email addrs ar
J C Lawrence wrote:
> > Why unique names?
>
> They map to directories in ~/lists.
...under the assumption that's a singe install.
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+
Ashley M. Kirchner
On Wed, 16 Jan 2002 15:08:24 -0700
Ashley M Kirchner <[EMAIL PROTECTED]> wrote:
> Why unique names?
They map to directories in ~/lists.
--
J C Lawrence
-(*)Satan, oscillate my metallic sonatas.
[EMAIL PROTECTED] He lived as a devil, e
On 16 Jan 2002 22:48:08 +0100
Andreas Kotowicz <[EMAIL PROTECTED]> wrote:
> I tought (better said: read in old postings) that mailman v.2 was
> going to have virtual domain support. so what happend to that?
It does have virtual domain support -- with the limit that no two
domains may have ident
First of all when you reply to the list the mailman-user list is configured to
reply by default to sender. Therefore if one doesn't reply all this happens.
I have 14 mailman list using 2.08 and sendmail spanning 3 domains with one
mailman install. It is done using vitual users under sendmail. No
On Wed, 2002-01-16 at 23:09, alex wetmore wrote:
> First of all, please don't send my private email back to a public
> forum. That is incredibly rude.
I'm really sorry. I didn't think about that.
>
> No, I don't use sendmail. My incoming mail is handled by postfix. In
> your example above,
On 16 Jan 2002, Andreas Kotowicz wrote:
> On Wed, 2002-01-16 at 22:48, alex wetmore wrote:
> > Only for subdomains that have mailing lists with competing names. I
> > host lists on three subdomains using one copy of mailman.
>
> are you using sendmail? let's say you have a list that listens to th
Andreas Kotowicz wrote:
> I don't like that because that would mean I have to install mailman for
> every single subdomain (that wants to have a mailing list) as well.
> picking unique names isn't flexible.
Why unique names?
--
W | I haven't lost my mind; it's backed up on tape somewhere.
On Wed, 2002-01-16 at 22:48, alex wetmore wrote:
>
> Only for subdomains that have mailing lists with competing names. I
> host lists on three subdomains using one copy of mailman.
are you using sendmail? let's say you have a list that listens to the
name [EMAIL PROTECTED] what happens if you
On Wed, 2002-01-16 at 22:39, alex wetmore wrote:
> You can install mailman twice, in two different directories. Use one
> installation for one domain, and one for the other domain.
I don't like that because that would mean I have to install mailman for
every single subdomain (that wants to have
On 16 Jan 2002, Andreas Kotowicz wrote:
> i have a mailinglist [EMAIL PROTECTED] sending mails to this email
> address works great as does sending mails to [EMAIL PROTECTED] this is a
> sendmail problem i know, but i really don't see how to designate a list
> to a specific domain. if you want to m
hi,
i was looking in the archive for this problem and have just found some
postings from 1999 that didn't satisfy me. so here again:
i have a mailinglist [EMAIL PROTECTED] sending mails to this email
address works great as does sending mails to [EMAIL PROTECTED] this is a
sendmail problem i know
20 matches
Mail list logo
