Thanks, Terri Oda and Mark Sapiro for the responses. The pointer to CommandRunner.py allowed me to quash the copied input for now.
(I had to do something, as the issue was getting our server into CBL and so largely hobbling all our lists.) But I agree with Terri that the result is not ideal -- and probably confusing -- for legitimate users of the request address. We are lucky (I guess) in that we have an otherwise tightly controlled, custom front end for subscriber management and that the only time *most* legitimate users interact with the 'request' address is when Replying to a subscription confirmation. (And that may be the step where a cc: of the original message is least informative.) Regards, Steven At 06:56 PM 6/11/2009, Mark Sapiro wrote: >In Mailman 2.1.x, only by modifying the the Results.send_response() >method in Mailman/Queue/CommandRunner.py. If you want to do this, post >that fact, and I can suggest a patch. At 05:52 PM 6/11/2009, Terri Oda wrote: >Are you sure you want to just disable the quoting? I know the spams are >obnoxious, but at least right now your users can tell that the spammer is the >culprit. If you take that part out, then they may assume your installation of >mailman is at fault, or that they somehow sent something out, which could be >even more confusing than just receiving the spam copy is. -- Steve Bonisteel The Web Paving Company Ltd. / Kingston, Ontario Phone: 613-531-0479 / Cell: 613-484-3196 ICQ: 321181636 MSN/AIM/YAHOO: "webpaving" ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
