mailman problem with local sender
![](https://secure.gravatar.com/avatar/dfa92b1d7153d7836dd983a48796d59d.jpg?s=120&d=mm&r=g)
I have a problem with my freshly-installed Mailman 1.1. When a mail is
sent to a list, it goes through properly. Everything works fine.
*Unless* the sender is on the list host. In that case, a duplicate
is also made and is held in sendmail (8.9.3)'s queue until mailman's "post"
script is killed. At that time the duplicate is sent out to all list
members and the zombie processes (one sh, one python) that were being
held open finally get cleaned up.
Python 1.5.2 (#2, Jun 10 1999, 15:33:16) [GCC 2.7.2.1] on freebsd3
List of processes being held open: 44829 ?? Is 0:00.01 sendmail -oem -oi -N failure -R full -- test@foo.org 44830 ?? Is 0:00.00 sh -c /usr/local/mailman/mail/wrapper post test 44831 ?? I 0:00.22 /usr/local/bin/python -S /usr/local/mailman/scripts/post test 44832 ?? Z 0:00.00 (python) 44833 ?? Z 0:00.00 (sh)
Sendmail logs from the message: Jan 27 00:31:17 <2.6> soivah sendmail[44827]: AAA44827: from=gsutter, size=456, class=0, pri=30456, nrcpts=1, msgid=<20000127003117.A42391@soivah.foo.org>, rel ay=gsutter@localhost Jan 27 00:31:17 <2.6> soivah sendmail[44827]: AAB44827: clone AAA44827, owner=te st-admin Jan 27 00:31:18 <2.6> soivah sendmail[44840]: AAA44840: from=<test-admin@foo.or g>, size=924, class=-60, pri=138924, nrcpts=1, msgid=<20000127003117.A42391@azaz el.foo.org>, proto=ESMTP, relay=localhost [127.0.0.1] Jan 27 00:31:20 <2.6> soivah sendmail[44841]: AAA44840: to="|IFS=' ' && exec /us r/local/bin/procmail -f- || exit 75 #gsutter", ctladdr=<gsutter@foo.org> (1001/ 20), delay=00:00:02, xdelay=00:00:02, mailer=prog, stat=Sent
This only happens when the sender is local, on the same box as the Mailman installation.
Are there known issues with this situation? Can I provide more information to aid in analysis?
Greg
Gregory S. Sutter I got a Pentium II for my girlfriend. mailto:gsutter@pobox.com Good trade, eh? http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052
![](https://secure.gravatar.com/avatar/efab32ced03577207a2966da965a9684.jpg?s=120&d=mm&r=g)
Hey, fancy meeting you here :-)
Gregory Sutter wrote:
The same basic setup here at work running on a FreeBSD 3.3 box, I
haven't seen this problem, let's see what may be different.
From this last log entry here it shows that you are running procmail
via a .forward, I wonder if procmail may be doing something strange. On the machine that I've got we're using procmail for local delivery, not via a .forward
Like I mentioned before, doing the same thing here, it looks like the
only difference is that you are using procmail via a .forward. One thing you might want to try is taking procmail out of your .forward and see if procmail is doing something strange.
Greg
--
Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento
![](https://secure.gravatar.com/avatar/dfa92b1d7153d7836dd983a48796d59d.jpg?s=120&d=mm&r=g)
On Thu, Jan 27, 2000 at 08:48:04AM -0800, Joseph Scott wrote:
This can't be it, because the problem occurs before procmail ever gets called. In the logs above, the message is cloned and queued before any type of delivery takes place. It's pretty puzzling.
Greg
Gregory S. Sutter Computing is a terminal addiction. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052
![](https://secure.gravatar.com/avatar/efab32ced03577207a2966da965a9684.jpg?s=120&d=mm&r=g)
Gregory Sutter wrote:
What version of sendmail are you using? 8.9.3 I would suppose? I've
got python :
Python 1.5.2 (#2, Nov 20 1999, 11:06:54) [GCC 2.7.2.3] on freebsd3
on my box. FreeBSD (uname -a) :
FreeBSD pebkac.owp.csus.edu 3.4-STABLE FreeBSD 3.4-STABLE #1: Thu Jan
27 14:23:22 PST 2000
scottj@pebkac.owp.csus.edu:/usr/src/sys/compile/PEBKAC i386
Except for some possible hardware problems it's been running fine. You also mentioned that this only happens if a user on that box sends email to the list, what's different about a user on the box sending to the list than a normal person sending to the list?
Strange.
--
Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento
![](https://secure.gravatar.com/avatar/efab32ced03577207a2966da965a9684.jpg?s=120&d=mm&r=g)
Hey, fancy meeting you here :-)
Gregory Sutter wrote:
The same basic setup here at work running on a FreeBSD 3.3 box, I
haven't seen this problem, let's see what may be different.
From this last log entry here it shows that you are running procmail
via a .forward, I wonder if procmail may be doing something strange. On the machine that I've got we're using procmail for local delivery, not via a .forward
Like I mentioned before, doing the same thing here, it looks like the
only difference is that you are using procmail via a .forward. One thing you might want to try is taking procmail out of your .forward and see if procmail is doing something strange.
Greg
--
Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento
![](https://secure.gravatar.com/avatar/dfa92b1d7153d7836dd983a48796d59d.jpg?s=120&d=mm&r=g)
On Thu, Jan 27, 2000 at 08:48:04AM -0800, Joseph Scott wrote:
This can't be it, because the problem occurs before procmail ever gets called. In the logs above, the message is cloned and queued before any type of delivery takes place. It's pretty puzzling.
Greg
Gregory S. Sutter Computing is a terminal addiction. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052
![](https://secure.gravatar.com/avatar/efab32ced03577207a2966da965a9684.jpg?s=120&d=mm&r=g)
Gregory Sutter wrote:
What version of sendmail are you using? 8.9.3 I would suppose? I've
got python :
Python 1.5.2 (#2, Nov 20 1999, 11:06:54) [GCC 2.7.2.3] on freebsd3
on my box. FreeBSD (uname -a) :
FreeBSD pebkac.owp.csus.edu 3.4-STABLE FreeBSD 3.4-STABLE #1: Thu Jan
27 14:23:22 PST 2000
scottj@pebkac.owp.csus.edu:/usr/src/sys/compile/PEBKAC i386
Except for some possible hardware problems it's been running fine. You also mentioned that this only happens if a user on that box sends email to the list, what's different about a user on the box sending to the list than a normal person sending to the list?
Strange.
--
Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento
participants (2)
-
Gregory Sutter
-
Joseph Scott