[ask]

# ~/.askrc
#
# This file contains the defaults to be used by ASK (Active Spam Killer)
# You can use this file as an example. For that purpose, just move it
# to ~/.askrc and edit the defaults to your needs.
#
# For more information, please consult http://www.paganini.net/ask
#
# $Id: sample_askrc,v 1.27 2003/04/07 21:29:22 paganini Exp $

# This should be your email addresses. The first address in the list will be
# used to send the confirmation messages.  In the example, all confirmation
# messages will come from myuser@mydomain.com)
rc_mymails    = myuser@mydomain.com , myotheruser@myothermail.com

# This should be your full name
rc_myfullname = John Doe

# The filename to be used as the delivery mailbox. Under unix, this is
# traditionally /var/spool/mail/yourusername. Make sure that you can 
# write to this file or ASK will fail. If you add a "/" to the end of
# this name, the program assumes this is a Maildir (qmail) mailbox
# (ex: /home/yourlogin/Maildir/)
rc_mymailbox = /var/spool/mail/yourlogin

# Your mailkey is some phrase that goes out on every email you send. Make
# SURE that you have this in your email. A good place for this would be
# in your signature. YOU MUST CHANGE THIS TO SOMETHING ELSE. Also, DO NOT
# change it to anything that appears in your headers, like your name or 
# else ASK will deliver every single email without confirmation.
#
# IMPORTANT: DO NOT USE YOUR FIRST AND/OR LAST NAME AS THE MAILKEY. This
# is too obvious and many spammers know this information. 
#
# Note: The mailkey is treated as a regular expression. If you intend to use
# special signs like "+", "$", "^", and others, escape them with a backslash
# (like \. \$ etc). If you don't know whether a given character has special a
# special meaning or not in a regular expression, just escape it.

rc_mailkey   = My Cow Ate My Homework

# This is used as a 'key' to generate an MD5 signature for the incoming message
# It can be anything, as long it's unique.
# WARNING: CHANGE IT BEFORE YOU USE THE PROGRAM. DO NOT CHANGE IT AFTER you
# install ASK.
rc_md5_key = Big brother is watching you
 
# ASK now accepts "remote commands", meaning that you can delete messages
# from your queue, add users to your whitelist, etc, all remotely. This
# feature can be enable or disable by changing rc_remote_cmd below
rc_remote_cmd_enabled = on

# There are two ways to use the "remote command" feature: One of them is to
# have ASK send you a piece of HTML Mail with clickable links what will send
# the correct emails to yourself in order to perform certain tasks. This may
# be appropriate for people with HTML capable mailers. On the other hand, if
# you cannot digest HTML mail, you will use the "text" version of the remote
# commands
rc_remote_cmd_htmlmail = off

# The default action for textmode commands is "N" (do nothing), unless the
# queued message is older than 'rc_remote_cmd_max_age (in days). The default
# will be OK for most people. If you want all queued messages to default to
# "Delete", set this to 0.
#rc_remote_cmd_max_age = 10

# This option controls which headers will be included in the message that goes
# attached in the confirmation mail and in the nastygram. Some people get 
# confused when they see the full set of RFC-822 headers. Comment the following
# line if you want to send the full headers
rc_basic_headers = From:,To:,Cc:,Bcc:,Date:,Subject:

# If you're having problems with fnctl locking, just uncomment the line below
# and point the file to a *LOCAL* filesystem. This will cause ASK to use locking
# on this file, instead of the main mailbox. Most people should leave this alone.
# rc_lockfile = %(rc_askdir)s/tmp/ask.lock

## Use for ASK programs et al
rc_askdir = ${HOME}/.ask

## Message queue (default: ~/ask/queue)
## If this ends in "/", the queue will be in "Maildir" format.
## This allows easy browsing of the pending queue using IMAP for instance.
## Example of Maildir queue: ${HOME}/Maildir/.Queue/
rc_msgdir = %(rc_askdir)s/queue

## You guess...
rc_tmpdir = %(rc_askdir)s/tmp

# These directories contain the confirmation and blacklist message files
# They're normally copied from a global location by asksetup.py. You
# normally don't need to change them.
rc_confirm_dirs = %(rc_askdir)s/templates
rc_blacklist_dirs = %(rc_askdir)s/templates

# Emails with your mailkey will be automatically delivered. Setting this
# variable to one will also cause those senders to be automatically
# added to your whitelist. It works like that: You send someone an email
# and that email contains your mailkey. Most people these days reply and
# keep the entire original email. Ask will "see" the mailkey there and
# add the sender to the whitelist right away. This seems to be a good
# idea in most cases.
rc_whitelist_on_mailkey = true

# These languages will be used to send email. Take a look at the 'templates'
# subdirectory to have an idea of available languages.  Currently, we have
# en (English), es (Spanish), ptbr (Brazilian Portuguese), de (German), fr
# (French), it (Italian) and nl (Dutch).  It is recommended to always include
# english. The order defined here will be the order in which they appear in
# the confirmation/blacklist emails.

rc_confirm_langs = en, ptbr
rc_blacklist_langs = en, ptbr

# Instead of using the scheme above, you can also force a specific
# file to be used for the confirmation and blacklist messages.
# Note that this is DEPRECATED and may not be supported in future
# versions of ASK. (Default is COMMENTED OUT and it should remain so)
#rc_confirm_mailbody   = %(rc_askdir)s/templates/confirm_mailbody.txt
#rc_blacklist_mailbody  = %(rc_askdir)s/templates/confirm_mailbody.txt

# From ASK 2.3_beta2 on, each list is now split into multiple files:  The
# whitelist, for example, is now contained in two files: whitelist.txt and
# whitelist-local.txt. ASK will only use the FIRST file of each list to
# add content to the list, even though all files on a list will be used to
# match addresses. The other files (*-local.txt) should be used for local
# edits. This setup prevents the possibility of conflict between ASK and the
# avid vi user. :) Also note that if you install ASK globally, you can set a
# "master" white/ignore/black list by adding an entry to /etc/ask/listname.
#
# If it seems confusing to you, just remember: When editing files locally
# (vi, emacs, etc) always use whitelist-local.txt, ignorelist-local.txt or
# blacklist-local.txt.

rc_whitelist  = %(rc_askdir)s/whitelist.txt, %(rc_askdir)s/whitelist-local.txt
rc_blacklist  = %(rc_askdir)s/blacklist.txt, %(rc_askdir)s/blacklist-local.txt
rc_ignorelist = %(rc_askdir)s/ignorelist.txt, %(rc_askdir)s/ignorelist-local.txt

# This is the command used to send confirmation messages. Please note that
# most MTAs have a 'stub' called sendmail, since they know that most programs
# call sendmail directly. This default should be OK for most people (you
# should verify your installation, though).
#
# TIP: If you're "trusted" to the mail system (your sysadmin knows what this
# means) you can use the following line when sending out the confirmations:
#
# rc_mta_command = /usr/sbin/sendmail -f '<>' -t < MAILFILE
#
# This will cause confirmation messages to be sent with a null return-path.
# Bounces from invalid addresses will be ignored completely, saving bandwidth
# and promoting world peace.

rc_mta_command = /usr/sbin/sendmail -t < MAILFILE

# This is the maximum numbers of lines of an attachment to include
# in the confirmation message. -1 for no limitation.
rc_max_attach_lines = 50
