TMDA Client Configuration

### T M D A |  |
TMDA Homepage | TMDA @ SourceForge |  |
Overview
Introduction
History
Features
Results & Testimonials
TMDA In Use
Usage
Requirements
Download
Installation
Configuration
Configuration
Overview
Pre-Configuration
Server Configuration
Client Configuration
Support
FAQ
Mailing Lists
Bugs & Patches
External Resources
Author
Jason R. Mastaler
© 2001
> |  | ### TMDA Client Configuration In addition to filtering your incoming e-mail, TMDA can also work with your mail client to modify your outgoing address with unique, cryptographically enhanced (tagged) e-mail addresses. This is done to compliment the filter's "whitelist" functionality. Dated Addresses TMDA can automatically tag your messages with a temporary e-mail address which only works for a defined time interval (e.g, 5 days). During this period, even those not on your whitelist will be able to contact you using the dated address. This also allows you to participate freely in open discussion forums such as Internet mailing lists without fear that your address will be "harvested" by spammers for later use against you, and without opening up your whitelist more than necessary. Here is an example dated address:
>     jason-dated-989108708.a17f80@mastaler.com
> This particular address expires on Sun, May 6 00:25:08 2001 UTC, which is exactly 5 days after it was generated. TMDA time intervals can be set in years, months, weeks, days, hours, minutes, and seconds. Once a dated address expires, messages sent there must go through the confirmation process. Use of strong cryptography insures that the timestamp can't be modified. Sender Addresses TMDA can also tag your messages with a sender address which is an e-mail address that only a certain sender can use. Here is an example sender address:
>     jason-sender-a751af@mastaler.com
> This particular sender address will only accept messages from president@whitehouse.gov. Other messages must go through the confirmation process. Sender addresses are often used to subscribe to mailing lists. This way, you don't have to worry that the subscription list might get harvested by spammers since only the mailing list software will be able to send messages there. The address to use can be found in the Return-Path header of a mailing list message (e.g, subscribe to the Python list with a sender address based upon python-list-admin@python.org). Keyword Addresses TMDA can also tag your messages with a keyword address which will work for any sender and indefinitely unless specifically revoked. Any string can be used as the keyword. Here is an example keyword address using the keyword `promos':
>     jason-promos.8d06eu@mastaler.com
- > Keyword addresses are appropriate when you need to hand-out a working address, but you don't want its use limited to a particular sender or time frame. They are particularily useful in cases where you are not be able to predict the sender address such as with automated mailings (your ISP, your Amazon.COM account, etc.). The caveat of course is that since keyword addresses are essentially keys to your inbox, you must manually intervene if the address starts getting spammed. An easy way to do this is to add the harvested keyword address to your ~/.tmda/lists/revoked file. The utilities tmda-dated-address, tmda-sender-address and tmda-keyword-address are included to generate the various types of addresses from the command line. Run the utility with the -h flag to get usage information (e.g, `tmda-dated-address -h`). list files: TMDA determines how to tag your outgoing mail by scanning though a set of text files in ~/.tmda/lists/. Here are the available list files:
  >     bare (don't tag)
  >     dated (tag with a dated address)
  >     sender (tag with a sender address)
  >     keyword (tag with a keyword address)
  >     exp (use an explicit address)
  >     ext (add an extension to the address)
- See the "User configurable settings" section in Defaults.py for more information on these files. Similar to the whitelist, the list files contain e-mail addresses and/or wildcard patterns, one per line. See the FAQ for details on matching syntax. A match in one of the list files determines the tag. For example, if you@domain.dom is listed in sender, mail sent there will be tagged with a sender address. If the destination address isn't listed in any of the files, or if the list files don't exist, the message will be tagged with a dated address. You can change this default by defining COOKIE_TYPE in your .tmdarc X-TMDA header: You can override any declarations you might have in your list files by adding this header when composing a message. TMDA will look for it first when determining how to tag the message. The header will be removed just before the message is sent. Here is how it can be used:
  `X-TMDA: bare` | Send the message to all recipients with your address untagged (no cookie added)
  `X-TMDA: dated` | Send the message to all recipients with a dated address (default timeout interval)
  `X-TMDA: dated 3M` | Send the message to all recipients with a dated address that expires in 3 months
  `X-TMDA: sender` | Send the message to all recipients with a sender cookie added to your address
  `X-TMDA: keyword promos` | Send the message to all recipients with a keyword (promos) cookie added to your address
  `X-TMDA: exp postmaster@xemacs.org` | Send the message to all recipients from postmaster@xemacs.org
  `X-TMDA: ext mlist-xemacs-beta` | Send the message to all recipients from jason-mlist-xemacs-beta@mastaler.com
- - > .tmdarc configuration: Make sure that your .tmdarc contains the same CRYPT_KEY on both your mail server and your mail client -- they must match. NOTE: The bare COOKIE_TYPE is especially useful when maintaining a "whitelist" of trusted contacts to filter your incoming mail against as described in the above sections. By default, addresses matching your WHITELIST will receive untagged (no cookie added) messages. This way your trusted contacts will not even be aware of TMDA. Set WHITELIST_TO_BARE = 0 in your .tmdarc to reverse this behavior. Mail User Agent (MUA) configuration: To have TMDA read your configuration each time you send outgoing mail and modify your sender address accordingly, you must arrange for your MUA to call the included sendmail compatibility wrapper (tmda-sendmail). Here is how to accomplish this for a few popular MUAs. Let me know if you are using TMDA with a MUA not listed here. For BSD Mail/mailx, add the following line to your .mailrc file:
    >     set sendmail="/path/to/tmda/bin/tmda-sendmail"
  - > For Pine, add the following line to your .pinerc file:
    >     sendmail-path="/path/to/tmda/bin/tmda-sendmail"
  - > For Mutt, add the following line to your .muttrc file:
    >     set sendmail="/path/to/tmda/bin/tmda-sendmail"
  - > For VM, add the following line to your .vm file:
    >     (setq sendmail-program "/path/to/tmda/bin/tmda-sendmail")
  - > For Gnus, add the following line to your .gnus file:
    >     (setq sendmail-program "/path/to/tmda/bin/tmda-sendmail")
- > For Sylpheed, Configuration --> Common Preferences --> Send --> External Program Check Use external program for sending In the Program path box, enter /path/to/tmda/bin/tmda-sendmail For Mahogany, Edit --> Preferences --> Network Check Use local mail transfer agent In the Local MTA command box, enter /path/to/tmda/bin/tmda-sendmail For XFMail, Misc --> Config Accounts+Misc --> Send Check Sendmail under Send method In the Sendmail Path box, enter /path/to/tmda/bin/tmda-sendmail For KMail (KDE Mail), Settings --> Configure KMail --> Network --> Sending Mail Check Sendmail In the Location box, enter /path/to/tmda/bin/tmda-sendmail USENET News Client configuration: If you still read USENET (a notorious source of SPAM), you might find it useful to post using a dated address. Simply have your newsreader call tmda-dated-address and use the result as your posting address. For Gnus, this could be accomplished with the following addition to your .gnus file:
  >     (defun tmda-dated-address ()
  >       (shell-command-to-string "/path/to/tmda/bin/tmda-dated-address"))

  >     (setq gnus-posting-styles
  >           (message-this-is-news
  >            (address tmda-dated-address)))