Patches item #1210507, was opened at 2005-05-28 12:05 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1210507&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Option to not respond to successful confirm command Initial Comment: Some people feel that the e-mail response to a successful e-mail confirm command is unnecessary and confusing. This patch to the 2.1.6rc4 base adds a mm_cfg.py option to control the sending of the e-mail reply to a successful confirm. The patch adds RESPOND_TO_SUCCESSFUL_CONFIRM = Yes to Defaults.py.in, and code to cmd_confirm.py to test this and not send the response in the case when it is a successful confirm and RESPOND_TO_SUCCESSFUL_CONFIRM has been set to No in mm_cfg.py. Note that if you apply the patch to an already configured existing installation, you need to patch Defaults.py instead of Defaults.py.in, but presumably you would only apply the patch if you were going to put RESPOND_TO_SUCCESSFUL_CONFIRM = No in mm_cfg.py anyway, so patching Defaults.py would not be mandatory in this case. ----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro) Date: 2005-05-28 15:04

Message: Logged In: YES user_id=1123998 Updated patch - structurally different but functionally the same ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1210507&group_id=103