TMDA Troubleshooting
If you encounter problems with running TMDA, please exhaust the following checklist first before reporting them or asking for assistance on the appropriate TMDA mailing list.
Please don't ask for free advice about TMDA if you haven't done this. Third-party commercial support is available for people who don't have time to read and follow instructions.
Make sure you have read the documentation, particularly those documents referenced under TmdaConfiguration.
Upgrade to the latest release if you aren't running it already and see if the problem disappears, which is likely given the rate at which TMDA is being developed.
Unless you are installing TMDA for the first time, make sure you have followed instructions in TmdaUpgrade.
Read TmdaFaq to make sure your question has not already been answered.
For delivery problems, check your LOGFILE_DEBUG file for errors, or if that isn't defined, look in ~/TMDA_DELIVERY_FAILURE.
For delivery problems/questions, also make sure LOGFILE_INCOMING is defined. Include the relevant snippets from this logfile when posting your question to the mailing lists.
Browse and/or search the mailing list archives for similar questions which have been asked in the past.
If, after all of this, your problem is still not resolved, you should inquire on tmda-users mailing list. Make sure to include at least the following information in your post:
Your TMDA version, your Python version, and your operating system (i.e, '''tmda-keygen -V''').
- Your type of TMDA installation (tarball, Linux RPM, FreeBSD port, etc.).
- Which MTA you are running (qmail, Postfix, etc.)
- If you are running TMDA from procmail or maildrop.
- Any other information you think might be relevant.
If you are interested in submitting a patch, please see TmdaPatchSubmissions.