[Mailman-Users] Virtual Hosts in mm-cfg.py
Richard Barrett
r.barrett at openinfo.co.uk
Sun May 23 21:50:26 CEST 2004
On 23 May 2004, at 17:52, Bob Escher wrote:
> I don't want to change anything
> All I want to do is set it up
> and learn it properly and then maybe down the line
> start tweaking it.
> I have 4 or 5 domains that will be using mailman
> and I just need to add them.
>
> The insrtuctions I recieved are from
>
> here.
> Info for integrating it with xmail can be found at:
> http://xmailforum.homelinux.net/index.php?
> showtopic=1179&st=0&#entry5823
>
> and I followed that specifically
>
> Thanks
>
>
>
>
> Subject: Re: [Mailman-Users] Virtual Hosts in mm-cfg.py
>
>
>> On 23 May 2004, at 16:50, bescher wrote:
>>
>>>
>>> Hello again
>>> I apologize for not putting a subject line in my last post.
>>> I am having several issues one of which are below
>>>
>>> I asked the question earlier (thank you Richard for helping me)
>>> about having more then 1 domain to have mailing lists in)
>>> he showed me where in defaults.py is the reference
>>> for it and also in a FAQ
>>>
>>> Now I am presuming you DON'T edit defaults.py
>>> at all and do everything in mm-cfg.py?
>>>
>>
>> Correct. If you make changes to Defaults.py it will work BUT they will
>> be lost when you install a Mailman update. You site specific changes
>> to
>> mm_cfg.py are not lost on updates.
>>
>>> I have the below in my mm-cfg.py
>>> and would like to know if this is correct
>>>
>>> Thank you for everything
>>>
>>>
>>>
>>> # Put YOUR site-specific settings below this line.
>>> IMAGE_LOGOS ='/icons/'
>>> DEFAULT_EMAIL_HOST = 'mail.test.com'
>>> DEFAULT_URL_HOST = 'list.tester.org'
>>>
>>> VIRTUAL_HOSTS.clear()
>>> add_virtualhost(listserv.test.com, mail.test.com)
>>> add_virtualhost(list.test1.com, mail.test.com)
>>>
>>>
>>> PUBLIC_ARCHIVE_URL = '/pipermail'
>>
>> The default for this is:
>>
>> PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s'
>>
>> why do you want to change it? But you need to ensure that an Alias
>> directive(s) in in your Apache web server httpd.conf (or whatever)
>> associates the /pipermail/ location with the correct file path, for
>> instance:
>
> Alias /pipermail/ /usr/local/mailman/archives/public/
>
> PRIVATE_ARCHIVE_URL = '/usr/local/mailman/archives/private'
>
> THIS I HAVE (ABOVE IN MY HTTP.CONF FILE)
>
>
>> The standard default for this is:
>>
>> DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>>
>> again, why do you want to change it?
>>
>> But you need to ensure that the ScriptAlias directive(s) in in your
>> Apache web server httpd.conf (or whatever) associates the /mailman/
>> location with the correct file path, for instance:
>>
>> ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
> THIS I HAVE AS WELL
>
>
> I do have those two things in my http.conf file
> (or will have very shortly will double check'
> but what about the domain aliases that I am looking for
>
Declaring virtual hosts in the mm_cfg implies that:
1. your DNS has entries for the hosts concerned
2. your Apache httpd.conf contains a VirtualHost directive for a named
or numbered virtual host for each of the virtual hosts you are telling
Mailman about.
btw: do remember that standard Mailman is a bit challenged in its
virtual host handling and that the listname name space is shared by all
virtual host it knows about. If you need to be able to support the same
listname on several virtual hosts with different lists then the normal,
simple, standard Mailman install will not meet your needs.
> Thank You
>
>
>
> Now I am getting bounce messages
> (at least I am getting those) I haven't gotten anything for 4 days
> and now I am
>
> Here is this new problem\
>
> smtp.rsegroup.com is (the name of the computer and is the mail server
> name
> as well
A mail loop is being reported to you and correctly so, from looking at
the headers of the looping message. I'll preface what I say with the
comment that I think this problem is nothing to do with Mailman per se.
Looking at the first three Received: headers of the message in temporal
order we have:
1st - the message is passed my mailman to smtp.rsegroup.com
---
Received: (from mailman at localhost)
by smtp.rsegroup.com (8.12.8/8.12.8/Submit) id i4NGK0rL004562
for mailman; Sun, 23 May 2004 11:20:00 -0500
From what you say this has happened on the same machine as mailman is
running on, smtp.rsegroup.com
2nd - the message is passed from smtp.rsegroup.com to 62ndmpco.org.
---
Received: from smtp.rsegroup.com (127.0.0.1:36716)
by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
id <S2B6> for <mailman at smtp.rsegroup.com> from
<mailman at smtp.rsegroup.com>;
Sun, 23 May 2004 11:20:00 -0500
Now in this Received: header it might be saying that smtp.rsegroup.com
passed the message via the 127.0.0.1 interface. Looking up the DNS
entries for smtp.rsegroup.com and 62ndmpco.org yields the IP numbers
69.33.193.71 and 69.33.193.73 respectively. Which is a bit of a puzzle,
which may indicate I do not know what I am talking about.
smtp.rsegroup.com. 43200 IN A 69.33.193.71
62ndmpco.org. 3095 IN A 69.33.193.73
3rd - the message is passed from 62ndmpco.org to 62ndmpco.org
---
Received: from 62ndmpco.org (127.0.0.1:36740)
by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
id <S2BB> for <mailman at smtp.rsegroup.com> from
<mailman at smtp.rsegroup.com>;
Sun, 23 May 2004 11:21:38 -0500
This occurs repeatedly as 62ndmpco.org appears to be relaying the
message back to itself; which is the mail loop complained of.
One thought I had was that 69.33.193.71 and 69.33.193.73 were both
interface on the same machine and this might explain things but when I
talked to the two IP numbers, the SMTP servers (MTAs) listening on them
report different operating systems and types of SMTP server - see
terminal transcripts below.
This is even more confusing because talking from outside your network
to 62ndmpco.org I get "eWall v2.0 at rsegroup.com ArGoSoft Mail Server
Pro for WinNT/2000/XP, Version 1.8" claiming to be the responder but
when 62ndmpco.org delivers to itself "XMail 1.18 (Linux/Ix86) ESMTP
Server" is reported in the Received: header.
I am also a little confused by the fact that an SMTP MTA is running on
62ndmpco.org but the MX record for that domain specifies
smtp.rsegroup.com exclusively, with no fallback.
62ndmpco.org. 3116 IN MX 3 smtp.rsegroup.com.
My last thoughts are that the mail loop is the result of a single
instance of XMail, maybe running on a machine supporting both
69.33.193.71 and 69.33.193.73 IP numbers, and that something is wrong
in the configuration of the mail relaying on that machine. The
difference I see from outside your network when connecting to
62ndmpco.org's SMTP port may be due to your firewall arrangements which
are routing my connection to a Windows box rather than the "real"
62ndmpco.org running Linux.
At this point I am bowing out as I know not wot about either type of
MTA in use on your site nor their configuration. Nor do I have any idea
about the DNS, firewall and routing arrangements on your site. You may
need to talk to your local sys admin guru.
Or maybe some other mailman-users list reader can advise.
Best of luck resolving this.
terminal transcripts
--------------------
myComputer: richard$ telnet smtp.rsegroup.com 25
Trying 69.33.193.71...
Connected to smtp.rsegroup.com.
Escape character is '^]'.
220 <1085338342.1301596976 at 62ndmpco.org> [XMail 1.18 (Linux/Ix86) ESMTP
Server] service ready; Sun, 23 May 2004 13:52:22 -0500
quit
221 [XMail 1.18 (Linux/Ix86) ESMTP Server] service closing transmission
channel
Connection closed by foreign host.
myComputer: richard$ telnet 62ndmpco.org 25
Trying 69.33.193.73...
Connected to 62ndmpco.org.
Escape character is '^]'.
220 eWall v2.0 at rsegroup.com ArGoSoft Mail Server Pro for
WinNT/2000/XP, Version 1.8 (1.8.5.2)
quit
221 Aba he
Connection closed by foreign host.
myComputer: richard$
> Received: from 62ndmpco.org (127.0.0.1:36740)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2BB> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:21:38 -0500
> X-AV-Scanned: yes e53522151522fc20a7ff0efbd73e72b8
> Received: from smtp.rsegroup.com (127.0.0.1:36716)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2B6> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:20:00 -0500
> Received: (from mailman at localhost)
> by smtp.rsegroup.com (8.12.8/8.12.8/Submit) id i4NGK0rL004562
> for mailman; Sun, 23 May 2004 11:20:00 -0500
>
> [<00>] XMail bounce: Rcpt=[mailman at smtp.rsegroup.com];Error=[Mail loop
> detected]
>
>
> [<01>] Error sending message
> [1085330668898.1301596976.smtp.rsegroup.com]
> from [62ndmpco.org].
>
> ID: <S2F3>
> Mail From: <mailman at smtp.rsegroup.com>
> Rcpt To: <mailman at smtp.rsegroup.com>
>
>
> [<02>] The reason of the delivery failure was:
>
> Mail loop detected
>
>
> [<04>] Here is listed the message log file:
>
> [PeekTime] 1085330668 : Sun, 23 May 2004 11:44:28 -0500
> <<
> ErrCode = -173
> ErrString = Mail loop detected
> Message <S2F3> blocked by mail loop check !
> SMTP-Error = "554 Message blocked by mail loop check"
>>>
>
>
> [<05>] Here is listed the initial part of the message:
>
> Received: from 62ndmpco.org (127.0.0.1:37084)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2F3> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:44:28 -0500
> X-AV-Scanned: yes 1f5fb7131c9c2fe1108bdb809a86df59
> Received: from 62ndmpco.org (127.0.0.1:37062)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2F1> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:42:50 -0500
> X-AV-Scanned: yes 48e2471613aaa83746cef57c5c2a821c
> Received: from 62ndmpco.org (127.0.0.1:37040)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2EF> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:41:13 -0500
> X-AV-Scanned: yes 3529343cbc4888ac62b0d994c7747e7e
> Received: from 62ndmpco.org (127.0.0.1:37017)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2ED> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:39:35 -0500
> X-AV-Scanned: yes 46fc98f6c7d9de1f73bd7d0d42e02e62
> Received: from 62ndmpco.org (127.0.0.1:36993)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2E9> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:37:57 -0500
> X-AV-Scanned: yes 94ae06347b6fbc657d7f196fa4d1399a
> Received: from 62ndmpco.org (127.0.0.1:36968)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2E6> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:36:19 -0500
> X-AV-Scanned: yes d178bc49c178a1f1f13661fc6fd85180
> Received: from 62ndmpco.org (127.0.0.1:36944)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2E3> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:34:41 -0500
> X-AV-Scanned: yes 65e3bc3e4d9fe05dc02abebcd94a3a09
> Received: from 62ndmpco.org (127.0.0.1:36919)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2DE> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:33:03 -0500
> X-AV-Scanned: yes fcbff4808ff4d302ba84a7e674b8ae74
> Received: from 62ndmpco.org (127.0.0.1:36895)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2DA> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:31:25 -0500
> X-AV-Scanned: yes 99a6d488c83f73405b0234d58e351bd8
> Received: from 62ndmpco.org (127.0.0.1:36871)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2D6> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:29:47 -0500
> X-AV-Scanned: yes 82004a1d48c9131f0c79f79d63858388
> Received: from 62ndmpco.org (127.0.0.1:36843)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2D0> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:28:09 -0500
> X-AV-Scanned: yes e80405809a200270a72ba8b32960b30c
> Received: from 62ndmpco.org (127.0.0.1:36819)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2CB> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:26:32 -0500
> X-AV-Scanned: yes df8ed30e2234e95fc0d22f14a5c1a49c
> Received: from 62ndmpco.org (127.0.0.1:36791)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2C6> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:24:53 -0500
> X-AV-Scanned: yes 4e960a6c4be7cde63d8c9de4262fd34c
> Received: from 62ndmpco.org (127.0.0.1:36765)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2C0> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:23:15 -0500
> X-AV-Scanned: yes 2a062620600c836c557212f1a57f493f
> Received: from 62ndmpco.org (127.0.0.1:36740)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2BB> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:21:38 -0500
> X-AV-Scanned: yes e53522151522fc20a7ff0efbd73e72b8
> Received: from smtp.rsegroup.com (127.0.0.1:36716)
> by 62ndmpco.org with [XMail 1.18 (Linux/Ix86) ESMTP Server]
> id <S2B6> for <mailman at smtp.rsegroup.com> from
> <mailman at smtp.rsegroup.com>;
> Sun, 23 May 2004 11:20:00 -0500
> Received: (from mailman at localhost)
> by smtp.rsegroup.com (8.12.8/8.12.8/Submit) id i4NGK0rL004562
> for mailman; Sun, 23 May 2004 11:20:00 -0500
> Date: Sun, 23 May 2004 11:20:00 -0500
> Message-Id: <200405231620.i4NGK0rL004562 at smtp.rsegroup.com>
> From: root at smtp.rsegroup.com (Cron Daemon)
> To: mailman at smtp.rsegroup.com
> Subject: Cron <mailman at smtp> /usr/bin/python -S
> /usr/local/mailman/cron/gate_news
> X-Cron-Env: <SHELL=/bin/sh>
> X-Cron-Env: <HOME=/home/mailman>
> X-Cron-Env: <PATH=/usr/bin:/bin>
> X-Cron-Env: <LOGNAME=mailman>
>
>
>
>
>
More information about the Mailman-Users
mailing list