>Send it to the redlist. Ah. I had to look in close detail at the redRe description to see this. I had not seen that the red list serves two distinct purposes. The first paragraph appears to summarise the function of the red list. The second paragraph does not make it immediately obvious that there is a second, distinct function, given the description of the first. Here's what the description of 1.3.5(23.6) says:
"If an email matches this Perl regular expression it will be considered redlisted. The redlist is a list of addresses that cannot contribute to the whitelist, and who are not considered local, even if their mail is from a local computer. For example, if someone goes on a vacation and turns on their email's autoresponder, put them on the redlist until they return. Then as they reply to every spam they receive they won't corrupt your non-spam collection or whitelist: \[autoreply\] "Redlisted addresses will not be added to the whitelist. Redlisted messages will not be stored in the SPAM/NOTSPAM-collection. As all fields marked by * this field accepts a list separated by | or a specified file 'file:files/redre.txt' " To make it much clearer, I'd change this to: "If an email matches this Perl regular expression it will be considered redlisted. "The redlist serves two separate purposes: "1) the redlist is a list of addresses that cannot contribute to the whitelist, and which are not considered local, even if their mail is from a local computer. For example, if someone goes on a vacation and turns on their email's autoresponder, put them on the redlist until they return. Then as they reply to every spam they receive they won't corrupt your non-spam collection or whitelist: \[autoreply\] "2) Redlisted addresses will not be added to the whitelist when your local user sends mail to that address, thereby preventing accidental pollution of the white list by, say, inadvertent replies by your users to e-mails from the spammer. "Redlisted messages will not be stored in the SPAM/NOTSPAM-collection. As all fields marked by * this field accepts a list separated by | or a specified file 'file:files/redre.txt' " Note how reason 1 is not what I was looking for, since I want to prevent my user from accidentally adding a 'spammer' address to the white list when my user sends an e-mail to that one recipient. Clearly delineated, reason 2 shows that the redlist can be used to prevent addresses reaching the whitelist (which IS what I wanted but is not obvious, since reason 1 is about our own users not being able to add a To: address to the white list). >- and upgrade to 1.3.9.1 please I can't do that, since the boss won't yet let it happen on his server. (I DO use the latest 1.3 on my own server, and, for testing, 2.x on another of my own servers.) >I forgot to mention, there is even a setting, which will add >automatically this type of flip-flopper to the redlist: Thanks. I had not seen this. The reason Ihad not seen it was probably that EmailWhiteRemovalToRed is in the E-mail Interface section (even in 2.0.0(4.08), but it has little to do with e-mail. It's really about the red list and might be better in the Spam Control section under the redRe expression field. As an aside, perhaps half an em could be added to the bottom of paragraphs in the style.css for assp, so that sequential paragraphs are more easily distinguishable/readable. :-) HTH. T. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
