The old server had essentially the same bounce options as the new. It was mailman 2.1.5, and I see many probe messages in the bounce log. Maybe you are right about the VERPed probe.
On Jan 12, 2010, at 4:19 PM, Mark Sapiro wrote: > On 1/12/2010 4:07 PM, Andrew Watson wrote: >> >> Are the configuration data stored in a readable file? I could go back >> to the old server and find out what bounce options I used there. > > > If you still have the installation on the old server except for web > access, you can do > > bin/config_list -o - LISTNAME > > There are a couple of possibilities. If the old server was Mailman > 2.1.5, that release had bounce probes enabled by default. Thus, when an > address bounced, it wasn't disabled immediately, but a VERPed prob was > sent and the address wasn't disabled until the probe bounced. It the MTA > wasn't handling the VERPed return address properly, no-one would ever > get disabled. > > It's also possible that bounce_info_stale_after was too short. > > -- > Mark Sapiro <m...@msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ 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
