Interestingly, the vette log has nothing in it for those rejects. Perhaps that is a clue to the problem. It appears to be none of the above. I have not implemented SSL yet so that is out. It must be saving my changes because when I revisit the admin page, the radio button is correct and no redirects are involved. Admittedly the only suspect is the ineffective mm_cfg.py variables. As you might recall that was an issue earlier but using the config script solved the problem so I haven't worried about it since. Here is my refuse.txt which looks correct:
Your request to the %(listname)s mailing list
%(request)shas been rejected by the list moderator. The moderator gave the following reason for rejecting your request:
"%(reason)s"
Any questions or comments should be directed to the list administrator at:
%(adminaddr)sI don't have any idea where to start on this. Can I somehow trace this if I have the offending message resent?
On 9/24/2012 8:16 PM, Mark Sapiro wrote:
Dennis Putnam wrote:
I didn't send a reason explicitly. Since the reason was given as part of the admin display, I thought that reason would go to the member as part of the rejection message. Is that not the case? If not, I would consider that a bug.
It is the case that the default reason shown in the admindb page or whatever you put there if you change it is included as part of the rejection message.
What is in Mailman's vette log for these rejects? If it doesn't show the reason that was in the admindb page, it may be a manifestion of the issue of the FAQ at <http://wiki.list.org/x/ioA9>.
If the reason is in the rejection message in the vette log but was not in the rejection message sent to the user, you may have an edited version of the refuse.txt template that applies to the list(s) and is missing the %(reason)s replacement.