Ron Brogden wrote:

On Tuesday 17 January 2006 12:04, Zack Beatty wrote:

...

I've removed sevaral list members, using the Mailman Admin interface. However, they're still gettting my mailings, and are threatening to complain to the spam cops? I've double checked to confirm that these email addresses are NOT in my membership list.

Howdy. Have you asked this user to forward you one of the messages they have received with all headers intact so you can a) see if it even originated with your server and b) if so, compare it against your SMTP logs to see why it is being sent out?

In addition to Ron's suggestions, If you can personalize the list, you can include the recipients address in the list footer for non-digest subscribers. Also, the monthly password reminders (which you can manually send any time if you have command line access - see 'cron/mailpasswds --help') show the address they are sent to (Assuming of course that these users haven't opted out of reminders).

It is very likely that these users are receiving list posts via some other 'forwarding' address that they don't remember subscribing to the list. The Received: headers in the mesages can provide clues.

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

Bob Bales wrote:

We keep having an issue pop up. A non-member of our net tried to post. The moderator went in and disallowed his post. Now everyday we get the same message that there is a post made by this person that needs attention. When we go into the control panel it says that there are no actions that need to be taken.

Do you have more that one Mailman instance on your server? Did you upgrade at some point and change the locations of things?

You are getting this daily message because a cron/checkdbs job is running (presumably as it should) and is finding this request in a lists/<listname>/request.pck file, but when you go the the admindb interface (if that's what you mean), it doesn't find the request in lists/<listname>/request.pck.

Normally this means there is more than one lists/ directory and the cron/checkdbs job is looking at one and the admindb interface is looking at another.

Of course, if by "the control panel" you mean some cPanel or similar thing and not the Mailman admindb web interface, see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp.

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

Bob Bales wrote:

No, on this domain only 1 PHPlist is running. I have another list on a different domain, but it is not currently operating.

Are you sure that this reminder is not coming from the other list?

Is it the normal "... mailing list has N request(s) waiting" message?

Can you do 'bin/dumpdb lists/<listname>/request.pck'? If so, what does it show? What does it show for the other <listname> directories?

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

Bob Bales wrote:

...

Can you do 'bin/dumpdb lists/<listname>/request.pck'? If so, what does it show? What does it show for the other <listname> directories?

Please give me further inructions on how to do this?

If you can log in to a command shell or in some other way (via a control panel) execute commands on the Mailman server machine, you do the following commands assuming Mailman is installed in the default location:

cd /usr/local/mailman

ls lists/ (returns all the listnames, for example list1, list2)

bin/dumpdb lists/list1/request.pck (returns a somewhat readable list of requests)

similarly for list2.

note that the installation directory may be different from /usr/local/mailman and the bin/ and lists/ directories may not be sub-directories of the same directory either, all depending on how Mailman was installed.

If you don't understand this, then you probably can't do it anyway. If your lists are locally hosted, you might be able to enlist the help of a local sysadmin. If they are hosted elsewhere, you'll probably have to get people at the host to do it.

One other command you might try is

find / -name request.pck

which will return the full paths of all request.pck files on the system. This will tell you whether or not there are any you aren't aware of.

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