Thanks for the reply. OK, to be clear the problem is one of mailbox name length. Another list member replied privately and questioned that so I will repost that information here.
The number characters in my list name plus the '-request' is 6 characters too many. I could change the list names but that would be too much effort for list members most of which are computer illiterate. These lists have been around for several years. The need for confirmations simply has not come up until now. It probably never worked from the beginning. It has been so long since I set these up I'm not sure I remember how (IIRC, that can be set on a list-by-list basis from the web interface) but obviously this is different. Perhaps I should have pointed that out in the original question but I didn't think it was really relevant. That being said, using list-confirm is still that same length. As for what needs to be munged, I think only the confirmation message. My list members don't use anything else and probably wouldn't know how anyway. In all the years these lists have been active, this is the first time someone had to change their email address so it is the first time a confirmation was needed. I was not aware this was going to be a major effort. Be aware that, although I am experienced with many various languages (scripting and otherwise), python is not among them. Mark Sapiro wrote: > Dennis Putnam wrote; > >> I am having a problem getting the reply-to header configured for >> confirmations. Due to some email restrictions from my ISP I cannot use >> the default (i.e. [EMAIL PROTECTED]). Thus when a user >> tries to reply to a confirmation, it bounces (it needs to be >> [EMAIL PROTECTED]).I can't find this in the documentation (probably >> because my reply-to search key word keeps yielding user reply >> information not mailman generated reply-to forms). How to I configure >> the reply-to header for confirmations. Do I need to customize the form >> itself? Thanks. >> > > > Can you use [EMAIL PROTECTED] or does that have to be munged too? If you > can use it, set > > VERP_CONFIRMATIONS = Yes > > in mm_cfg.py and restart Mailman. > > If the list-confirm address is munged too, you will have to modify the > definitions of the getListAddress() and GetConfirmEmail() methods in > Mailman/MailList.py to return the addresses you use. > > Also, if you are concerned about the site (mailman) list, you need to > modify the get_site_email() function in Mailman/Utils.py. > > If you need help with these mods, post again and indicate which of the > nine list-... addresses need to be munged and to what. > >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
