> Heh, I think this is a general problem when you get two > email robots talking to each other! In MM2.1cvs the robot > will refuse to respond to a message marked Precedence: > bulk|junk|list -- but it looks like that wouldn't have even > helped in this case (since the Majordomo server isnt' > setting that header ;/ )
Rate limiting can do a lot to prevent things from getting out of hand. For example, respond at most ten times to essentially the same request from the same email address. On any given day, when Mailman gets the tenth message from the same email address without valid commands, it could reply "This is the tenth message of this type today from you. It order to avoid problems like mail loops between email robots, any further messages of this type will be ignored today. Please try again tomorrow." And then any further messages from that address with no valid commands will be just discarded. Similarly, Mailman would reply only to ten subscription requests for the same list from the same user on any given day. And only to ten unsubscription requests for the same list from the same user on any given day. And only to ten requests to change the subscription options in the same way. Etc. Since most loops (with the exception of some bounce loops) iterate more quickly than ten times per day, this will kill most loops between robots before they create serious problems. Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman-21/listinfo/mailman-developers
