Under the spam control section, I suggest: 1) Moving the "Redlist serves 2 purposes..." bit from the GUI up to its own explanation section instead of having it in the RedRE section. That useful description applies to more than just RedRE
2) Adding some information to the redlist description. My changes in GREEN By default, Redlisted messages will not be stored in the SPAM/NOTSPAM-collection (see DoNotCollectRedList and DoNotCollectRedRe). 3) Change RedRe description to: If an email matches this Perl regular expression it will be considered redlisted. redRe detects tags to process a mail like the recipient were redlisted - nothing else (no redlist addition/removal). By default, RedRe matching messages will not contribute to the corpus (see DoNotCollectRedRe). As all fields marked by * this field accepts a list separated by | or a specified file 'file:files/redre.txt'. 4) Consider adding reference to DoNotCollectRedList to the list GUI screen? Yes, if someone changes the default of DoNotCollectRedList, they need to know the ramifications of that choice. However, if 2 years after making that change, they don't remember and then read what the redlist does, where it says redlisted mail won't be saved without mention of DoNotCollectRedList, they could be really confused. These additions to the GUI will make it more clear. I hope this is helpful. ken
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
