Looks like plesk is self healing... :-/ when you shut off and turn on mailman it rebuilds the list aliases. Also appears that I am running 2.1.9 and the plesk update for mailman doesn't actually update mailman!?
I guess I need to figure out how to get 2.1.12 running. Currently ...12 update dies because it wants the python development package. Will the current python break plesk?? 8-0 So remind me again how plesk makes my life easier? :-P John I wrote: > Thanks, I think I've got it set correct. My server has multiple domains, plesk > and qmail... in case anybody with a similar setup is interested, I found the > alias at /var/qmail/mailnames/<domain>/.qmail-<listname>-bounces > > John > > Mark Sapiro wrote: >> John wrote: >> >>> I am having problems with my service provider handling outgoing list >>> email... I >>> would like to temporarily disable bounce handling for debug so I can see the >>> complete bounces immediately. >> >> If you have access to the mailman installation, change the list-bounces >> alias to go to you. >> >> Otherwise, all you can do is make sure that >> bounce_notify_owner_on_disable is Yes so that when a member's delivery >> is disabled by bounce you receive the notice which contains the full >> bounce message. You can also reduce the threshold to cause delivery to >> be disabled and a notice sent on the first bounce, but if you do that >> in Mailman prior to 2.1.10, a bug in cron/disabled will possibly >> disable delivery for users with stale bounce info. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org