On 01/15/2015 03:05 PM, Andrew Stuart wrote: > 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?
Assuming the myl...@example.org list is Mailman 2.1.x, you need to ensure that either Privacy options... -> Recipient filters -> require_explicit_destination is No or that adifferentl...@adifferentdomain.org is listed in Privacy options... -> Recipient filters -> acceptable_aliases. There may be other issues depending on what adifferentl...@adifferentdomain.org actually is and how it delivers to myl...@example.org and whether it delivers to other addresses as well. Also, things like the List-* headers added by myl...@example.org may cause issues, the most obvious being that reply-list will go to myl...@example.org, not adifferentl...@adifferentdomain.org. -- 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 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