[Mailman-Users] Email sent to list isn't delivered?

Mark Sapiro mark at msapiro.net
Wed May 12 21:02:36 CEST 2010


Martijn de Munnik wrote:
>
>I installed and configured Mailman on Solaris with Postfix. Everything
>seems to work except sending emails to the list :(
>
>I can subscribe to the list and get the confirmation email, also the lists
>admin gets an email about the subscription. But when I send an email to the
>list nobody on the list gets that email?
>
>After some postfix processing the mail is successfully delivered to
>mailman:
>
>---
>May 12 14:29:27 stevie.youngguns.nl postfix/local[12940]: [ID 197553
>mail.info] E95C020807: to=<test-youngguns.nl at stevie.youngguns.nl>, orig_to
>=<test at youngguns.nl>, relay=local, delay=3, delays=0.02/0/0/3, dsn=2.0.0,
>status=sent (delivered to command: /opt/youngguns/mailman/mail/mailma
>n post test)
>---


This says postfix successfully invoked the wrapper which presumably
invoked the 'post' script and which terminated normally which says the
message should be queued in qfiles/in/ as that's all this process does.


>Mailman is installed in /opt/youngguns/mailman:
>
>---
># pwd
>/opt/youngguns/mailman
># ls -la
>total 66
>drwxrwsr-x  20 root     mailman       20 Apr 28 09:30 .
>drwxr-xr-x  16 root     root          16 Apr 28 09:23 ..
>drwxrwsr-x  11 root     mailman       70 Apr 28 11:24 Mailman
>drwxrwsr-x   4 root     mailman        4 Apr 28 09:30 archives
>drwxrwsr-x   2 root     mailman       42 Apr 28 11:25 bin
>drwxrwsr-x   2 root     mailman       13 Apr 28 09:48 cgi-bin
>drwxrwsr-x   2 root     mailman       12 Apr 28 09:48 cron
>drwxrwsr-x   2 root     mailman        7 May 12 14:34 data
>drwxrwsr-x   2 root     mailman        7 Apr 28 09:48 icons
>drwxrwsr-x   6 root     mailman        6 May  7 16:05 lists
>drwxrwsr-x   2 root     mailman        4 May 12 14:44 locks
>drwxrwsr-x   2 root     mailman        8 May  7 16:06 logs
>drwxrwsr-x   2 root     mailman        3 Apr 28 09:48 mail
>drwxrwsr-x  38 root     mailman       38 Apr 28 09:31 messages
>drwxrwsr-x   2 root     mailman        2 Apr 28 09:30 pythonlib
>drwxrwsr-x  11 root     mailman       11 Apr 28 10:32 qfiles
>drwxrwsr-x   2 root     mailman       16 Apr 28 09:49 scripts
>drwxrwsr-x   2 root     mailman        2 Apr 28 09:30 spam
>drwxrwsr-x  39 root     mailman       39 Apr 28 09:31 templates
>drwxrwsr-x   4 root     mailman       19 Apr 28 09:48 tests
>--- 
>
>When I run as root I only get a warning, no errors:
>
>---
>Warning: Private archive directory is other-executable (o+x).
>         This could allow other users on your system to read private
>archives.
>         If you're on a shared multiuser system, you should consult the
>         installation manual on how to fix this.
>No problems found
>---


The above is all good.


>The logs directory isn't very helpful. Nothing about my message in here:
>
>---
>-rw-rw-r--   1 mailman  mailman      891 May 12 14:34 error
>-rw-rw-r--   1 mailman  mailman       86 May  7 15:48 mischief
>-rw-rw-r--   1 mailman  mailman     5978 May 12 14:34 qrunner
>-rw-rw-r--   1 mailman  mailman     2312 May 12 14:43 smtp
>-rw-rw-r--   1 root     mailman      497 May 12 14:43 subscribe
>-rw-rw-r--   1 mailman  mailman      324 May  7 16:07 vette
>---
>
>The qfiles directory only contains other directories but no files:
>
>---
># find .
>.
>./in
>./virgin
>./out
>./commands
>./bounces
>./archive
>./retry
>./shunt
>./news
>---


Which says the message either wasn't queued in qfiles/in/ at all or it
was completely processed.


>These processes are running for the user mailman:
>
>---
> mailman 14427 14424   0 14:34:29 ?           0:01 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=ArchRunner:0:1
> mailman 14424     1   0 14:34:29 ?           0:00 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/mailmanctl start
> mailman 14439 14424   0 14:34:30 ?           0:01 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=VirginRunner:0:
> mailman 14430 14424   0 14:34:29 ?           0:01 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=IncomingRunner:
> mailman 14429 14424   0 14:34:29 ?           0:00 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=CommandRunner:0
> mailman 14437 14424   0 14:34:30 ?           0:00 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=NewsRunner:0:1
> mailman 14440 14424   0 14:34:30 ?           0:00 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=RetryRunner:0:1
> mailman 14428 14424   0 14:34:29 ?           0:00 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=BounceRunner:0:
> mailman 14438 14424   0 14:34:30 ?           0:01 /opt/csw/bin/python
>/opt/youngguns/mailman/bin/qrunner --runner=OutgoingRunner:
>---
>
>I really don't have any clue where the messages are going to and why
>they're not delivered?


Does the test list have Archiving Options - archive set to Yes? If so,
is the message archived?

Does the test list have any eligible message recipients, i.e.
non-digest member with delivery enabled and not the poster if the
poster has "not metoo" set and not an addressee (To: or Cc:) with
"nodups" set?


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan



More information about the Mailman-Users mailing list