One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments.
Thanks!!!
--Warren
On Thu, 2003-10-23 at 23:10, Warren Hoffman wrote:
One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments.
Thanks!!!
--Warren
for i in find /var/mailman/ -type f
do; grep -H "fragment" $i; done
This will search through every file in every subdirectory of /var/mailman and look for the word "fragment". If it finds a match, it prints out the files name.
Good Luck - Jon Carnes
- Jon Carnes wbap@ap.ee.pbz [2003-10-24 00:10:39 -0400]:
On Thu, 2003-10-23 at 23:10, Warren Hoffman wrote:
One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments.
for i in
find /var/mailman/ -type f
do; grep -H "fragment" $i; doneThis will search through every file in every subdirectory of /var/mailman and look for the word "fragment". If it finds a match, it prints out the files name.
"grep -r .... /usr/lib/mailman/" finds Mailman/Handlers/Hold.py which appear to hard-code the rejection messages.
Feature request:
for "class SuspiciousHeaders": optionally add the name and the value of the suspicious header to the rejection message. the moderator then can remove it if he wants to, but it gives him valuable fedback on which rules trigger.
for all rejection messages, allow a common custom explanation. e.g., I find it very inconvenient to have to insert "See http://clisp.cons.org/faq.html#rejected for details." after each rejection message.
Thanks!
At 9:24 AM -0500 2005-01-24, Sam Steingold wrote:
- for all rejection messages, allow a common custom explanation. e.g., I find it very inconvenient to have to insert "See http://clisp.cons.org/faq.html#rejected for details." after each rejection message.
I've uploaded a patch which allows you to re-use the
member_moderation_notice as a result of a generic_nonmember_action which results in a rejection. See http://sourceforge.net/tracker/index.php?func=detail&aid=1107169&group_id=103&atid=300103. This may not solve all your problems, but might still be useful to you.