it does indeed sounf like the problem is with cron. Everything else sounds
like it's working properly, but cron is never calling qrunner to proccess
it. Can you look in your ~mailman/qfiles dir and see if there's anything in
there? If it's full of unprocessed .msg, and .db files, then the cron, or
qrunner to be more precise is your problem.


  -Richard

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, January 17, 2002 10:51 AM
To: [EMAIL PROTECTED]
Subject: [Mailman-Users] Mailman wrapper program not working properly ??



Sorry if this has been answered before...

I'm using Mailman 2.0.8 w/ postfix on freebsd 4.5 PRE-.

I have set up a test list. All functions appear to work via the web
interface. The problem is that none of the email subscriptions, posts,
confirmations, etc. via email are working.

They are getting to the server as verified by /var/log/maillog:
Jan 16 13:05:22 lists postfix/local[37774]: D945789D7B:
to=<[EMAIL PROTECTED]>, relay=local, delay=2, status=sent
("|/usr/local/mailman/mail/wrapper post test2")

This should verify that I have properly configured w/ "postalias".
I have also verified that confirmations/subscriptions get to the system
(piped through postfix to Mailman) w/ a similar log entry. The problem is
that it doesn't appear to be handled by mailman from there.

In /usr/local/mailman/logs/, I get nothing in 'error' and only get a new
user logged in 'subscription' when I add them via the web interface. If I
do anything via email, nothing is logged.

/usr/local/mailman/mail/wrapper is suid and owned by root.

Is this a problem perhaps with cron not working?

Grateful for any assistance.

TIA,

mike


------------------------------------------------------
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users


------------------------------------------------------
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Reply via email to