Eino Tuominen writes: > You are missing the point. Of course you can inform of a delivery > problem, but only when you really need to do it. Every organisation > should know of every recipient within their authority. You should know > the recipient if you accept a message for delivery from outside your domain.
Says who? There is nothing in the standards that says so. And if you take that seriously, you have to disable .forward and procmail for individual users, as well as refuse to allow open subscription mailing lists and the like. This may make sense in the U.S. Army and in corporations with a military authority structure, but it does not in most universities, research, or open communities. That is *not* the way Internet mail is designed to work. Mail, like every other application on the Internet, is intended to be decentralized. It is designed to allow load-sharing by use of intermediate and/or secondary MXes to handle primary crashes or overloads. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
