Is it possible to change the "public" email address of a list (that reported in the rfc2369 headers, message footers, etc.) while maintaining a different name internally? Would there be any obvious problems I'm missing with such a feature?
For our virtually hosted lists, we need independent namespaces on a per-domain basis. This isn't really something that Mailman currently handles AFAICT. So we might have: [EMAIL PROTECTED] (or [EMAIL PROTECTED]) forwarding to [EMAIL PROTECTED] Obviously this looks ugly, and encourages people to send to the "wrong" address; it's a simple matter, of course, to alias [EMAIL PROTECTED] to [EMAIL PROTECTED] This "hack" (if it worked) wouldn't be perfect, but would at least improve the virtual hosting situation for our purposes. For various reasons, it's not practical to do a unique installation of Mailman for each account or domain, and requiring unique listnames globally will also not work for our purposes. If not, consider this an RFE (I can submit one on the site if requested). If someone wanted to provide a patch for this (against 2.1.3), I might even be able to give them some money if it worked properly. -- "Since when is skepticism un-American? Dissent's not treason but they talk like it's the same..." (Sleater-Kinney - "Combat Rock") ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
