[Mailman-Users] FW: FW: No One Can Post a Message but the Server

[Greg Sims]

OK Mark -- Will do.

The bash script generates the approve header line in the newsletter header
with the following command:

	echo 'Approved: password' >>newsletter

This seems pretty straightforward with respect to trailing spaces. The
password is 12 characters long and contains upper and lower case characters.
I have verified that I can enter admindb for the list via the web using this
password.

Greg
-----Original Message-----
From: Mark Sapiro [mailto:msapiro at value.net] 
Sent: Tuesday, July 18, 2006 7:39 PM
To: Greg Sims; 'Patrick Bogen'
Cc: mailman-users at python.org
Subject: RE: [Mailman-Users] FW: FW: No One Can Post a Message but the
Server

Greg Sims wrote:
>
>I found /var/log/vette and see an entry that matches the time the
newsletter
>cron was run.  Here is the log entry:
>
>Jul 18 04:23:01 2006 (8553) Message discarded, msgid:
><20060718112301.22011.qmail at raystedman.org>
>
>I hope this gives you more clues.  Is there some way for mailman to be
>verbose in the logs?


I suggest until you get this debugged that you set Privacy
options...->Sender filters->member_moderation_action and Privacy
options...->Sender filters->generic_nonmember_action to Hold. Then the
vette log, the held message notice and the admindb interface will all
give the specific reason for the hold.

Also, if Content filtering->filter_content is Yes, set Content
filtering->filter_action to "Forward to List Owner".

Then after you get this debugged, you can set these back to Discard.

My best guess at this point is that your "Approved: pw" header has
trailing spaces.

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