Andrew Stuart writes: > Image a mailing list myl...@example.org > > Is there any reason why the users could not be told to use > adifferentl...@adifferentdomain.org which simply forwards mail to > myl...@example.org > > Would this raise any potential problems?
Depends on what you are trying to do. The main issues relate to users being subscribed to mylist but post to adifferentlist. Also MTA configuration may be tricky (SPF, DKIM, DMARC) depending on whether you have full control of both domains. Problems with lists: - This may be quite confusing to users, as they post to adifferentlist but set nomail, notmetoo, digest settings etc on mylist. - This will confuse smart software, because the List-* headers will point to mylist. (Some MUAs are smart enough to reply to List-Post by default or when a "list-reply" command is invoked.) - If the lists are served by different MLM instances, ban settings etc on one cannot be referenced by the other. - There are some settings to alleviate user confusion (sibling lists, umbrella lists) which you will not be able to use across instances. Mailman 3 will help to alleviate some of these issues by making it easier to serve multiple domains from one instance, but if your domains are actually different hosts, you're not going to be able to use those features without substantial extension to current Mailman 3 (as we've discussed on mailman-developers, access to many Mailman 3 databases requires running on the same host). ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
