On 12/15/2010 1:40 AM, Florian Effenberger wrote: > > interestingly, a withlist -l -r fix_url -a seems to have cured the > problem. Of course, copy-pasting it out of my documentation without > thinking led to the hostnames for 50% of the lists being wrong, which > I manually corrected in the list interface, but now things seem to > work. Maybe it also has something to do with the nightly cronjobs, > resetting the bounce counter? > > Strange...
The only thing fix_url would "fix" is the domain of the sender of the mail and the domain of the list-ow...@domain recipient (much but not all mail to owners/moderators is sent first to the list-ow...@... address and only then resent to the actual owner/moderator addresses. Possibly this domain was not valid or didn't have a -owner alias. > Anyone knows an easier solution when migration another host to our > mailing list server while adding another hostname? The procedure for adding a host name is 1) Put the appropriate add_virtualhost() in mm_cfg.py. 2) If Postfix is to generate virtual alias maps for this domain, add it to POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py. 3) To move any lists to that domain, run fix_url with the -u option on the list(s) I don't think there's any 'easier' solution. Note, if you don't care about the web domain, you can set the host_name on the list's General Options page instead of step 3. -- 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
