J C Lawrence wrote:
> Now we're making progress.
>
> Please repeat the same experiments using your address instead of
> -owner. They should all succeed this time, but we need to check to
> make absolutely sure where the fences are.
Yeh, works fine. =)
> If I read this right the message some into QMail and is delivered
> successfully. The question is delivered to what/where. I'm a
> little curious that it doesn't note that its actually being handed
> to a Mailman wrapper pipe. Please check very carefully to ensure
> that your aliases are set up to accomplish the following (paths may
> vary):
>
> testlist: "|/var/lib/mailman/mail/wrapper post testlist"
> testlist-admin: "|/var/lib/mailman/mail/wrapper mailowner testlist"
> testlist-request: "|/var/lib/mailman/mail/wrapper mailcmd testlist"
> testlist-owner: testlist-admin
qmail aliases are set up differently from sendmail aliases. Each alias is a separate
file in the /var/qmail/alias
directory. Here they are:
/var/qmail/alias/.qmail-testlist |preline /home/mailman/mail/wrapper post
testlist
/var/qmail/alias/.qmail-testlist-admin |preline /home/mailman/mail/wrapper
mailowner testlist
/var/qmail/alias/.qmail-testlist-owner testlist-admin
/var/qmail/alias/.qmail-testlist-request |preline /home/mailman/mail/wrapper mailcmd
testlist
The |preline you see is apparently (what the heck do I know?) necessary for qmail to
understand what's being piped, or
where it's being piped, or something.... That came from the readme.qmail in the docs.
I can try it without the
preline, but something's floating around in the back of my memory about that not
working... or at least, being "more
broken."
> Create a text file which contains a standard RFC 2822 message.
> it really doesn't matter what it is other than the fact that you
> can recognise it when you see it.
>
> Run the following as the appropriate user:
>
> $ cat message_file | /var/lib/mailman/mail/wrapper mailowner testlist
>
> What happens? Logs?
Sent it from user "alias" (who belongs to the qmail group "nofiles") and got no errors
from the terminal.
Syslog has nothing relevant to report.
Servicelog shows:
01/7/12@14:10:54: START: telnet pid=5519 from=[my.workstation.ip.address]
01/7/12@14:20:04: START: smtp pid=5709 from=127.0.0.1
mailman/logs/bounce shows:
14:20:04 2001 (5707) Testlist: [EMAIL PROTECTED] - exceeds limits (This was the
From: in the message)
14:20:04 2001 (5707) Testlist: already disabled [EMAIL PROTECTED]
mailman/logs/error shows something finally, though it's not directly related to the
current test (it's been empty till
now):
Jul 11 12:50:04 2001 (10163) testlist: Bounce recipient loop encountered!
(Ie, bounce notification addr, itself, bounces.)
Bad admin recipient: [EMAIL PROTECTED]
mailman/logs/post shows:
Jul 12 14:20:04 2001 (5707) post to testlist from [EMAIL PROTECTED], size=20, 1
failures
mailman/logs/smtp shows:
Jul 12 14:20:04 2001 (5707) smtp for 1 recips, completed in 0.331 secs
> While you're at it, also check correct operation of the -request
> address.
I did cat temp.txt | /home/mailman/mail/wrapper mailcmd testlist ; the message was
from amanda@tux.[foo.bar] this time,
and to testlist-request@tux.[foo.bar].
mailman/logs/smtp:
Jul 12 14:44:02 2001 (5773) smtp for 1 recips, completed in 0.312 seconds.
None of the other mailman logs show anything for this time frame at all.
amanda@tux.[foo.bar] got mail on this, however:
==============================
Message 1: automated response.
>From testlist-admin@tux.[foo.bar] Thu Jul 12 21:44:03 2001
Delivered-To: amanda@tux.[foo.bar]
Subject: Mailman results for Testlist
From: testlist-request@tux.[foo.bar]
To: amanda@tux.[foo.bar]
X-Ack: no
Sender: testlist-admin@tux.[foo.bar]
Errors-To: testlist-admin@tux.[foo.bar]
X-BeenThere: testlist@tux.[foo.bar]
X-Mailman-Version: 2.0.5
Precedence: bulk
List-Help: <mailto:testlist-request@tux.[foo.bar]?subject=help>
List-Post: <mailto:testlist@tux.[foo.bar]>
List-Subscribe: <http://tux.[foo.bar]/mailman/listinfo/testlist>,
<mailto:testlist-request@tux.[foo.bar]?subject=subscribe>
List-Id: Tux's test list <testlist.tux.[foo.bar]>
List-Unsubscribe: <http://tux.[foo.bar]/mailman/listinfo/testlist>,
<mailto:testlist-request@tux.[foo.bar]?subject=unsubscribe>
List-Archive: <http://tux.[foo.bar]/mailman/private/testlist/>
This is an automated response.
There were problems with the email commands you sent to Mailman via
the administrative address <testlist-request@tux.[foo.bar]>.
To obtain instructions on valid Mailman email commands, send email to
<testlist-request@tux.[foo.bar]> with the word "help" in the
subject line or in the body of the message.
If you want to reach the human being that manages this mailing list,
please send your message to <testlist-admin@tux.[foo.bar]>.
The following is a detailed description of the problems.
>>>>> Subject line ignored:
>>>>> Test
Command? Testing, 1, 2, 3.
Command? .
===================
What I find odd about this is that, except for the addresses of to and from, this is
the same test email I use for a
variety of other purposes and it seems to work okay there...
And of course qmail shows the message being sent to amanda@tux :
Jul 12 14:44:02 tux qmail: 994974242.810176 new msg 114919
Jul 12 14:44:02 tux qmail: 994974242.837965 info msg 114919: bytes 1643 from
<testlist-admin@tux.[foo.bar]> qp 5775 uid
507
Jul 12 14:44:02 tux qmail: 994974242.854154 starting delivery 1: msg 114919 to local
amanda@tux.[foo.bar]
Jul 12 14:44:02 tux qmail: 994974242.854351 status: local 1/10 remote 0/20
Jul 12 14:44:02 tux qmail: 994974243.017196 delivery 1: success:did_1+0+0
Jul 12 14:44:02 tux qmail: 994974243.017511 status: local 0/10 remote 0/20
Jul 12 14:44:02 tux qmail: 994974243.059128 end msg 114919
In response to other, newer questions:
(JC)>Got any results from that last business of checking your alias setups?
The aliases are as identical to the docs as I know how to make them.
I did find out when I ran the test - piping the text message right into wrapper - that
the GID it's expecting is 450,
which is "nofiles", which belongs to qmail. (Helps if you remember to switch to the
RIGHT user. What can I say, I've
had no caffeine yet today. :-) )
(JB)> Then I'd go ahead and install mailman from scratch, I don't think you can
> really trust an RPM install of it with qmail.
I did not use an RPM install of either mailman or qmail. (I don't know where JB got
the idea that I had.)
Whee... I just love having everything go crazy at once. I don't get it. The moon isn't
full ... is Mercury retrograde?
On top of all else, I just had a techinician show up to fix a CSU that isn't broken.
[He was looking for the downstairs
office network, not ours.] (And of course he said, "Oh pardon me, ma'am, I'm so-and-so
from such-and-such-company, and
I'm here to replace a piece of equipment that's malfunctioning." I said, which piece
of equipment would that be? and he
said, "it's part of your computer and phone system." and I said, WHICH part? to which
he said, very slowly, in that
bright tone of voice reserved for very small children and the mentally incapacitated,
"It's called a CSU/DSU. Do you
know where the phone room is, or maybe the computer server room?" I let the guy
live... but I may reevaluate that
decision ...)
=)
Amanda
------------------------------------------------------
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
