[Declude.JunkMail] restricted mailing?

2004-01-22 Thread paul
Title: Message



Hey guys, I asked this on Imail's list as well, but 
thought I'd see what Declude users do/think:

What I'd like to be able to do, is block all mail 
to a certain account, except from those addresses specified via AUTOWHITELIST. 
Kind of a 'parental control'. Let's say I give my daughter an email address, I 
only want to allow mail from family + friends, but those I specify in her 
contacts list within the webmail, so using Declude's AUTOWHITELIST ON, I can 
weight all mail coming in to her mailbox, say, 100 or so, waaay above delete 
range, but because of the address, it would be delivered. Does that make sense? 


Is anyone else doing this?

Paul





Re: [Declude.JunkMail] restricted mailing?

2004-01-22 Thread Matt




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.

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.

Matt


paul wrote:

  Message
  
  
  
  Hey guys, I asked this on Imail's
list as well, but thought I'd see what Declude users do/think:
  
  What I'd like to be able to do, is
block all mail to a certain account, except from those addresses
specified via AUTOWHITELIST. Kind of a 'parental control'. Let's say I
give my daughter an email address, I only want to allow mail from
family + friends, but those I specify in her contacts list within the
webmail, so using Declude's AUTOWHITELIST ON, I can weight all mail
coming in to her mailbox, say, 100 or so, waaay above delete range, but
because of the address, it would be delivered. Does that make sense? 
  
  Is anyone else doing this?
  
  Paul
  
  
  


-- 
=
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=




Re[2]: [Declude.JunkMail] restricted mailing?

2004-01-22 Thread Madscientist
Hello Paul, Matt

Thursday, January 22, 2004, 1:36:55 PM, you wrote:

M Paul,

M This isn't something that I would generally try to promote
M because ofthe complexity of maintaining it in most cases, but for
M one's owndaughter, it might make perfect sense. Something of course
M though wouldneed to happen that caused her to get spam though, so
M it might not benecessary at all.

M You would need the Pro version to do this of course, and
M instead ofweighting things to her address, what you would do is set
M up aweightrange test covering almost everything and then use
M actions (HOLD,ROUTETO or DELETE)  in a per-user JunkMail file
M according to theManual.  Whitelisting will prevent an all inclusive
M weightrange testfrom taking action on an E-mail.

snip

M   What I'd like to be able to do, isblock all mail to a certain
M account, except from those addressesspecified via AUTOWHITELIST.
M Kind of a 'parental control'. Let's say Igive my daughter an email
M address, I only want to allow mail fromfamily + friends, but those
M I specify in her contacts list within thewebmail, so using
M Declude's AUTOWHITELIST ON, I can weight all mailcoming in to her
M mailbox, say, 100 or so, waaay above delete range, butbecause of
M the address, it would be delivered. Does that make sense? 

We've been experimenting a PL (Private Listcode) methodology for these
scenarios. Specifically, all messages for a particular user (domain
usually) are blocked unless a PL code is present in the message. The
PL code is a random sequence of characters like a password. The group
that uses the code freely passes it around between them. Since no
spammer has the code it can't be abused. The code usually goes into a
signature. If the code becomes compromised then a new code is made up.

We usually create a PL code in Sniffer, but the methodology works
without it - In Declude you would use WHITELIST ANYWHERE plcode, and
block everything else.

Hope this helps,
_M

-- 
Best regards,
 Peter G McNeil (Madscientist, CodeDweller)
 President, MicroNeil Research Corporation.
 Chief SortMonster, www.SortMonster.com
 mailto:[EMAIL PROTECTED]

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.


Re: [Declude.JunkMail] restricted mailing?

2004-01-22 Thread 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





Re: [Declude.JunkMail] restricted mailing?

2004-01-22 Thread Matt




There's no "TO" filter, and no "FROM" filter either, only ALLRECIPS and
MAILFROM (the SMTP Sender). I would like to have access to these
things though because there are some patterns that can't be done by way
of a HEADERS filter.

Anyway, you could use a filter file, but personally, I would think the
Web mail address book would be easier to maintain. It would though
affect all of your users to have AUTOWHITELIST on, and that can be
especially problematic on very large domains since spammers will BCC
multiple recipients sometimes, and one might have an address to their
Web mail address book. Small domains are not that big of a deal, just
make sure that you don't list your own address in the address book
because spammers will spoof the address they send to in the MAILFROM.

The issue with all of this is that there's always the possibility of
something being sent to multiple addresses on a domain, and having a
whitelist setting or filter file affect that. Declude treats
whitelists globally, and filters can't be used with weights anymore
reliably in this case, you need to rely on per-user actions instead of
weights. Seems that NOT functionality would also benefit this scenario
(and many others).

If you are only looking to do this for one person, I would suggest
going the IMail rules route. That should be the most foolproof method,
but again, don't add her own address in there. If you want to offer
this widely as a configuration to customers, some others on this list
have done just this, but using the whitelist setting connected to the
address book.

Pete's idea wasn't bad, but you'll probably have a hard time telling
Grandma to insert a string with ==$FasdJyeW34df*== in every message :)
I'm sure Pete's counterparts can figure that out though. Seems most
appropriate to discussions relating to spam though.

Matt



paul wrote:

  
  
  
  
  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
  
  
  


-- 
=
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=




RE: [Declude.JunkMail] restricted mailing?

2004-01-22 Thread Bill
Title: Message



Hi 
Paul,

You 
may want to try my whitelist/blacklist program. It isa per user 
utility and has a strict mode where everything is blacklisted unless it is 
specifically whitelisted. I use it extensively and many other postmasters 
us it also. You can get more information and download it 
at:

www.wamusa.com/wamcheck

Thanks,
Bill

  
  -Original Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  On Behalf Of paulSent: Thursday, January 22, 2004 11:16 
  AMTo: [EMAIL PROTECTED]Subject: 
  [Declude.JunkMail] restricted mailing?
  Hey guys, I asked this on Imail's list as well, 
  but thought I'd see what Declude users do/think:
  
  What I'd like to be able to do, is block all mail 
  to a certain account, except from those addresses specified via AUTOWHITELIST. 
  Kind of a 'parental control'. Let's say I give my daughter an email address, I 
  only want to allow mail from family + friends, but those I specify in her 
  contacts list within the webmail, so using Declude's AUTOWHITELIST ON, I can 
  weight all mail coming in to her mailbox, say, 100 or so, waaay above delete 
  range, but because of the address, it would be delivered. Does that make 
  sense? 
  
  Is anyone else doing this?
  
  Paul