Re: [Asrg] 4. Consent Framework - General

["John Fenley" <pontifier@hotmail.com>]

It seems to me that no matter what language the consent famework is writen 
in, the limiting factor is still the tests that can be performed. It does no 
good to have even a perfect consent defenition if the tests that must be 
perfomed are not possible.

I have created a consent framework that i feel is simple, complete, and 
relies on tests that i know would be possible with the choicelist system I 
have been working on.

The attached file would be read as is by a Choicelist MUA.

John Fenley
www.Choicelist.com

_________________________________________________________________
Get MSN 8 and help protect your children with advanced parental controls.  
http://join.msn.com/?page=features/parental
#   Choicelist sample consent policy v8/21/2003
#
#
#   This is a sample consent policy
#   This FiLe Is NoT CaSe sEnSiTiVe and
#   extra    spaces  (outside of [data blocks]) are    ignored
#   each line consists of a "COMMAND=DATA" string
#   A comma is treated as if it was a "[carriage return]LAST_COMMAND="
#   Conflicting commands: The last command is used
#
#   Commands available: key, Id, feedback, bulk, intro_a, intro_b, adv, 
content
#   whitelist, blacklist, list, filter, other
#
#   various coded/authorised values are(will be) looked up at 
www.choicelist.com
#   Gibberish strings represent Choicelist ids, and do not mean anything by 
themselves.
#



# key:
# allows the user to specify a key type and key to sign all outgoing mail 
with.
# keys may only be of aproved types, but anyone can define a type and submit 
it.
# this ensures that everyone will be able check the signature type 
specified.
# this also allows automatic ecryption/decryption at the sending and 
recieving ends
# Make sure your public key is included in your choicelist Id


# key=[key type][key]






# id:
# this allows the user to give their address, and Id to their MUA to allow 
extra checks


# id=me@example.com,97sd863j89






# Feedback allows a sender to see how you handle their mail. It tells bulk
# mailers that you do or don't want what they are sending, by telling them 
if
# you are ignoring them, or requesting that you receive their mailing if you
# aren't currently. This lowers costs to everyone over the long run.
# Selective mode asks you before sending a message.
#
# Give feedback:
# Yes, No, Selective.
# Default: Yes


 feedback=yes
# feedback=selective






# Receive bulk email:
# List valid Choicelist bulk email Ids.
# Default: No entries
# Default: each entry in a different folder


# bulk=a12t34s5[directory A]






# Receive bulk introductions:
# Two types of bulk introductions exist.
# Solitary and recomended
# A bulk introduction is a short blurb giving the name of the id responsible
# for the message, and asking if you would like to add them to your list, or
# ignore them forever.
# The timed option allows only Ids that were created before a certain date, 
or
# a number of days/months/years ago to be introduced. This proves a  measure
# of  stability on the part of the sender.
# intro_a is for any unknown sender and intro_b is for recomended senders
# Yes, No, Timed. time format "mm/dd/yyyy" or [number](m,d,or y)
# Default: Yes to both


intro_a=1m
intro_b=yes
# intro_a=6m






# Receive "ADV:" labeled mail:
# Yes, no.
# Default: Yes
# Default: placed in ADV folder and deleted after 30 days.


adv=yes[junk mail]
# adv=no






# Whitelist / blacklist:
# List addresses, ids, IPs or external lists to block/allow.
# Default: No entries


# whitelist=your_friend@example.com,192.0.34.166,34h2nn2b3,friend_list.txt
# blacklist=your_enemy@example.com,12.254.227.235,643ud52,foe_list.txt






# Receive personal email:
# this option affects only Choicelist personal mail
# The timed option makes Personal mail wait an amount of time before it is
# delivered. This raises the chance that a spamming personal Id will be
# terminated before the spam is delivered.
# Yes, No, Timed. time format x(sec,min,hr,d,m,y)
# Default: Yes


personal=yes
# personal=5min






# Receive/block mail from third party lists:
# List all valid Choicelist third party lists, and select block, or allow,
# plus handling options.
# Default: No entries
#
# Lists are evaluated first to last, as a party may be on more than one 
list.
# The last entry that mentions a party gives the final destination of mail
# from them.
# Eg:
# City Highschool: (allow): [school]
# City Highschool bullies: (block)
# Tim's friends: (allow): [Tim's friends]
#
# Everyone from city highschool will go in the school folder unless they're 
a
# bully or Tim's friend, while all of Tim's friends go in the Tim's friends
# folder even if they go to city high or are a bully.
# Bullies who are not Tim's friend go to the trash.
#
# These groups must be created and registered before being used.
# IP based lists may be added as well, though these only affect 
non-Choicelist
# registered mail.
# Anyone not on these lists is unaffected by these options.
# Anyone can create a list, and put anyone on it. This list is then made
# public, though it will be encrypted.
# These lists can be updated by the list controler.


# list=324bn28v[a][school],3jbnj8bc[a][chemistry class],






# Third party filters:
# List Choicelist compatible filters here.
# Default: No entries
# These are filters that have been interfaced with Choicelist.
# These filters are run according to the makers specifications, but user
# options may be set up if available.
# When a filter is put here it should just work.


# filter=528s9u78f






# Miscellaneous filters:
# Run other filters here.
# Default: No filters
#
# filters run on a virtual machine to prevent unauthorized actions unrelated
# to email.
# Filters that need to be messed with go here.


# filter=[command line][folders accessed][other resources required]






# Where unknown, unfiltered mail goes:
# Specify folder.
# Default: Inbox 2


other=[inbox2]
#other=delete