Re: [Declude.JunkMail] restricted mailing?

[paul]

>>This isn't something that I would generally try to promote because of the >>complexity of maintaining it in most cases, but for one's own daughter, it might >>make perfect sense. Something of course though would need to happen that >>caused her to get spam though, so it might not be necessary at all. True, at first, it wouldn't be much of an issue. >>You would need the Pro version to do this of course, and instead of weighting >>things to her address, what you would do is set up a weightrange test covering >>almost everything and then use actions (HOLD, ROUTETO or DELETE)  in a >>per-user JunkMail file according to the Manual.  Whitelisting will prevent an all >>inclusive weightrange test from taking action on an E-mail. Ok, I hadn't thought of the per-user configs, we are running pro here, so that's not an issue. I'm just wondering the pros to that as apposed to what I had mentioned before. Wouldn't having a list of recipients <those that were under parental control> be easier to manipulate? Sure, I have access to all Declude to make adjustments, but to make it as user-hands-off as possible, you wouldn't want to do it that way......   I guess what I'm asking is: Does Declude have a TO: key? like:   mailfrom 15 is [EMAIL PROTECTED]  is there a mailto 0 is [EMAIL PROTECTED] ? I don't see this on the manual site.   So a filter file would be defined as:   parentalcontrols    tofile    d:\mail\imail\declude\parentlist.txt    x    100    0   So message comes in, it's addressed to someone in the file, given a 100 weight, and deleted. UNLESS the address is on the users webmail contact list.   I'm not trying to repeat the same thing over and over, but I'm not sure I'm describing this the way I'm trying to make it sound........ Did that make sense? LOL! Basically, does Declude allow you to scan for matches on the TO field?????   Thanks Matt! I'll look into the per user configurations as well.   Paul