TMDA FAQ

### T M D A |  |
TMDA Homepage | TMDA @ SourceForge |  |
Overview
Introduction
History
Features
Results & Testimonials
TMDA In Use
Usage
Requirements
Download
Installation
Configuration
Support
FAQ
Mailing Lists
Bugs & Patches
External Resources
Author
Jason R. Mastaler
© 2001
- > |  | ### TMDA FREQUENTLY ASKED QUESTIONS Will TMDA run on non-unix clients such as Microsoft Windows? Not directly since the supported Mail Transfer Agents are only available for UNIX. However, you can configure a qmail relay to re-write the address of outgoing messages with tmda-inject, so that those running Microsoft Windows clients can take full advantage of TMDA. See `README.RELAY' in the contrib/ directory for the full details. Also, here is one user's configuration details for a site-wide TMDA install using smtpd-auth, vpopmail and qmailadmin. Can you clarify the syntax for the whitelist? I'd like any address in my domain (domain.dom) to be able to send me mail directly without worrying about confirmations. In addition to explicit e-mail addresses, TMDA supports matching patterns in the list files which use Unix shell-style wildcard characters. The special characters are:
  >     Characters(s)    Description
  >     -------------    -----------
  >     *                Matches everything.
  >     ?                Matches any single character.
  >     [seq]            Matches any character in seq.
  >     [!seq]           Matches any character not in seq.
  > In addition, ``@='` (a custom rule) will expand to match both `@` and `@*.` in one shot. Here are some common examples:
  >     # match only jdoe@domain.dom
  >     jdoe@domain.dom
  >     # match anyone@domain.dom, but not anyone@sub.domain.dom
  >     *@domain.dom
  >     # match anyone@sub.domain.dom, but not anyone@domain.dom
  >     *@*.domain.dom
  >     # match both anyone@domain.dom, and anyone@sub.domain.dom
  >     *@=domain.dom
NOTE: For incoming mail, tmda-filter compares the address in the Envelope-Sender, the "From:" header and the "Reply-To:" header when looking for a match. How can I delete old, unconfirmed messages from TMDA's pending queue? TMDA comes with a utility called `tmda-clean' which does this for you. You can run it by hand, or periodically from cron. Run `tmda-clean' without any arguments to get a listing of possible options. tmda-clean should be run from the user account that owns the pending queue, not from root (unless root is running TMDA). For example, to purge unconfirmed messages older than 14 days each morning at 2AM, add the following crontab entry: `0 02 * * * /path/to/tmda/bin/tmda-clean 14d` How do I allow my ezmlm mailing lists to pass through TMDA? Each list message is sent out with a different envelope sender address. You can whitelist the ezmlm list using wildcard characters. Here is an example whitelist entry for the qmail mailing list: `qmail-return-*@list.cr.yp.to` This will allow messages to get through when initially interacting with ezmlm to get subscribed, as well as after when list messages are delivered. I use BBDB, and every time it sees a new 'dated' address it asks me whether I want it added to so-and-so's BBDB record. How can I prevent this? You can either set bbdb-always-add-addresses to 'never, or use a BBDB hook to filter the addresses before adding them to the database.