Surprises & Gotcha's
This section of the documentation is reserved for functionality and quirks
that, although not erroneous, may not be what you expect. Check this list for
help if you experience problems with tmda-cgi.
Whitelist Woes
Python Problems
Authentication Ailments
Attachment Anxiety
Whitelist, Blacklist... where are the options?
Bad Base
Install Again?
Can't Install!
Bad Install
International Intrigue
Whitelist Woes
tmda-cgi's whitelist feature does not update the list pointed to by
configuration variable
CONFIRM_APPEND.
tmda-cgi uses configuration variable
PENDING_WHITELIST_APPEND
instead of
CONFIRM_APPEND.
To use the whitelist feature, you must set
PENDING_WHITELIST_APPEND
to a list that is handled by your incoming filter.
Python Problems
TMDA requires Python version 2.1 but some flavors of Linux (such as RedHat) come with two different versions of
Python installed, one older and one newer.
If tmda-cgi tries to run using the wrong version of Python, then you
must specify the correct version at compile time. Instead of typing:
# ./configure <options>
Type:
# /usr/bin/python2 configure <options>
(Assuming that your Python 2.1+ can be found at
/usr/bin/python2.) The compiler will save the correct version of
the Python interpreter and use it when tmda-cgi is run.
Authentication Ailments
If no username/password combination lets you log in, your problem may be due
to a misconfigured authentication method. To aid in finding out precisely
what is misconfigured, we have added a variety of debugging messages to
various parts of the authentication code.
The debugging messages are embedded in comments in the login page. Try
logging in and when you get the "Wrong password." message, do a "View/Source"
of the HTML page. At the top of the page, you should see something like:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!--
Having difficulties logging in?
Here's some details of why you couldn't:
Capturing the debug stream...
Setting up remote authentication with pop3://localhost
Trying pop3 authentication for gre7g@lazarus.wolfhome.com@localhost:110
pop3 authentication for gre7g@lazarus.wolfhome.com@localhost
failed: -ERR authorization failed
Authentication returned: 0
-->
<html>
... |
If you do not wish for these messages to be embedded, modify the template
file login.html and remove the %(ErrMsg)s string.
If the messages do not help you get to the root of the problem, refer to the
instructions on the Contact page to get some
assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.
Attachment Anxiety
tmda-cgi does not let you view the attachments on a pending e-mail.
If you need one of the attachments in an e-mail, simply release the e-mail
by clicking on the checkmark button. You can then download the e-mail as if
the sender had confirmed the message, and view the attachment. Remember,
tmda-cgi lets you manage your pending messages. It is not a web-based mail
client.
Whitelist, Blacklist... where are the options?
The screenshots show whitelist and blacklist options, but I don't see
these!
The whitelist and blacklist options are only available if you have
configured them in your config file. Try setting PENDING_WHITELIST_APPEND
and PENDING_BLACKLIST_APPEND.
The radio buttons and option buttons should appear on the pending list and
pending e-mail viewer once you do.
Bad Base
My skel files use %(Base)s/bin/ to refer to TMDA's
bin/ directory, but when my users install, the files created point
to the wrong directory.
The variable %(Base)s asssumes you have installed TMDA from source.
If you installed TMDA from RPM or FreeBSD port, then the assumed relationship
between library files and executables is no longer valid.
Simply modify the skel files, remove %(Base)s/bin/ and
replace it with the correct path to TMDA's executables.
Install Again?
I've already installed TMDA on this e-mail account, but when I login to
tmda-cgi, it gives me the welcome screen and asks if I want to install.
If tmda-cgi cannot detect a valid TMDA install on a given e-mail account, it
will ask if you wish to install. The reason why it can't detect a valid
install are hidden in the comments at the top of HTML for this page. Do a
"View/Source" and at the top of the page, you should see something like:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!--
Why did I end up here?
Here's some details:
Can't find key file:
/home/vpopmail/domains/lazarus.wolfhome.com/gre7g/.tmda/crypt_key
-->
<html>
... |
If you do not wish for these messages to be embedded, modify the template
file welcome.html and remove the %(ErrMsg)s string.
If the messages do not help you get to the root of the problem, refer to the
instructions on the Contact page to get some
assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.
Can't Install!
I've run configure and make, but make install
won't work because the user I'm compiling as doesn't have the needed
permissions to put a file in the web tree. Can I do make install as
root?
Yes, you may do make install as root.
Bad Install
I used tmda-cgi's auto-install feature to add TMDA to my e-mail account, but
it didn't work. I am still receiving spam and no confirmations are being
sent.
Did you read the auto-install page?
tmda-cgi comes with a default installation that it will apply to all new TMDA
users, but this installation may not match your system. You may
need to customize the skel files
to match your system setup.
International Intrigue
Instead of Chinese characters in the pending list, the subject lines are
showing up as random English characters!
Did you remember to install the Chinese
codec? tmda-cgi can't translate Chinese without it.
|
