In my setup all I have is the .qmail file in the users directory and the user-something is followed because vpopmail now has that feature.
Sam
You need either a test/.qmail-default or a nesys.it/.qmail-test-default when using TMDA, since replies to confirmation requests come back to an extension address (test-confirm-xxx). Without the -default file they will never get delivered and thus mail will never get confirmed.
Tim Legant wrote:
"Andrea Riela" <[EMAIL PROTECTED]> writes:And the TMDA_DELIVERY_FAILURE: Uncaught Python 2.2.1 Exception (Tue Jan 20 17:08:28 2004): ----------------------------------------------------------- Traceback (most recent call last): File "/usr/local/tmda-1.0/bin/tmda-filter", line 53, in ? execfile(os.path.join(execdir, 'tmda-rfilter')) File "/usr/local/tmda-1.0/bin/tmda-rfilter", line 175, in ? from TMDA import Defaults File "./TMDA/Defaults.py", line 1534, in ? ConfigError: Can't find key file: /home/vpopmail/domains/nesys.it/.tmda/crypt_key Traceback (most recent call last): File "/usr/local/tmda-1.0/bin/tmda-filter", line 69, in ? raise NameError, 'LOGFILE_DEBUG is not defined' NameError: LOGFILE_DEBUG is not definedProbably there's a problem with $HOME, isn't it? I need vpopmail-vdir.sh?Yes, there is a problem with $HOME and you can handle it in one of several ways. 1) You can leave the user's .qmail and .qmail-default in his/her home directory, the way you have it now. The only reason that the .qmail file is processed, however, is that vdelivermail, which gets run from .../nesys.it/.qmail-default, runs the user's .qmail. It doesn't do a very good job of it, though, so I don't recommend this option. 2) You can put the user's dot-qmail files in .../domains/nesys.it/: .../nesys.it/.qmail-test .../nesys.it/.qmail-test-default If you do this, be sure all paths in the config file point to the test user's .tmda/ directory. You'll need to make sure to set DATADIR, among other things. This is close to the configuration you have now, except that the dot-qmail files are in the domain directory rather than in the user's directory. This is the way the contrib/vadduser-tmda script sets things up. 3) You can do the same as 2 (the user's dot-qmail files are in the domain directory) but avoid changing any paths in the config file; it will look much cleaner, nearly empty. You do this by using the vpopmail-vdir.sh script on the tmda-filter command line (see the -S option) in the dot-qmail files. The vpopmail-vdir.sh script will properly set the $HOME environment variable so that the '~' shortcut actually refers to the test/ directory rather than the nesys.it/ directory, as it does in the preceding two options. This means that the defaults for TMDA's paths will work "out of the box".My .qmail is: |preline -f /usr/local/tmda-1.0/bin/tmda-filter -c /var/qmail/vpopmail/domains/nesys.it/test/.tmda/config | maildrop /etc/mailfilter <-- a script to do some checks about spam.Your mailfilter script won't get called for spam anymore because TMDA won't let the spam get that far. Only valid messages will ever be processed by the second line in your .qmail.I don't use qmail-default, because I'll use TMDA only for specific accounts.You need either a test/.qmail-default or a nesys.it/.qmail-test-default when using TMDA, since replies to confirmation requests come back to an extension address (test-confirm-xxx). Without the -default file they will never get delivered and thus mail will never get confirmed. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
