"tmda" <[EMAIL PROTECTED]> writes: > I'm a bit confused about where to put the /.tmda directory. Her'es how > qmil is set up on this box: The dot-qmail file is as follows: > > /hsphere/local/var/vpopmail/domains/domain.com/.qmail-someusername > and it contains: > /hsphere/local/var/vpopmail/domains/domain.com/someusername/Maildir/ > So do I put that user's /.tmda directory here: > > /hsphere/local/var/vpopmail/domains/domain.com/someusername/.tmda > or somewhere else? Thanks for helping...
Well, some disclaimers first: 1) I do not use VPopMail. I do understand how it works, but not its intricate details. 2) Until I read your mail, I had never heard of HSphere. I googled and I'm assuming it is the Help Desk software to which you're referring. It appears that HSphere is using the VPopMail add-on to qmail and has set it up slightly non-standard. That's OK, though. Let me give you a few pointers and let you determine how to make TMDA work best in your situation. First, many settings for TMDA will be the same for each of your users. Take advantage of the /etc/tmdarc file for those settings. That file is read before any user-specific configuration file. The same settings (from Defaults.py -- http://tmda.net/config-vars.html) can be used in /etc/tmdarc. Second, given that this is in a help-desk environment, you may find that all of your users can share company-wide whitelist and blacklist files. They may even be able to share a company-wide incoming filter file. Let me try to give a brief example of what I mean. I'll use 'example.com' as the domain. - /etc/tmdarc: (global TMDA configuration file) FILTER_INCOMING = '/hsphere/local/var/vpopmail/domains/example.com/incoming' - /hsphere/.../example.com/incoming: (the TMDA filter file) from-file -autodbm /hsphere/local/var/vpopmail/domains/example.com/blacklist drop from-file -autodbm /hsphere/local/var/vpopmail/domains/example.com/whitelist ok - /hsphere/.../example.com/.qmail-someusername: /usr/local/bin/tmda-filter /hsphere/local/var/vpopmail/domains/example.com/someusername/Maildir/ In a nutshell, this configuration does *not* require a .tmda directory per user, all users share the (very minimal) incoming filter *and* the black/whitelist files and qmail, not TMDA, is responsible for the delivery into the individual's Maildir. Let's say you wish each user to have his or her own black/whitelist files. You can modify the above configuration as follows. - /etc/tmdarc: *** no changes *** - /hsphere/.../example.com/incoming: from-file -autodbm /hsphere/local/var/vpopmail/domains/example.com/${EXT1}/blacklist drop from-file -autodbm /hsphere/local/var/vpopmail/domains/example.com/${EXT1}/whitelist ok - /hsphere/.../example.com/.qmail-someusername: *** no changes *** Place the black/whitelist files in /hsphere/.../example.com/someusername/. The way this works is that qmail sets a number of environment variables when making a delivery. The EXT1 variable is set to the part of the recipient's email address after the first '-' and before the second '-'. Thus, since mail to a virtual user comes in to <[EMAIL PROTECTED]>, EXT1 is the same thing as 'someusername'. This is exactly why you name your .qmail* files the way you do (.qmail-EXT1-EXT2, etc.). The TMDA filter parser is capable of picking variables out of the environment and substituting them into your rules, which means the the first rule above will end up looking like this. from-file -autodbm /hsphere/local/var/vpopmail/domains/example.com/someusername/blacklist drop Now, you still have no need for a .tmda directory (all configuration remains global), but individuals can have their own black/whitelists. There are variations on these themes, of course. I suggest you sit down and plan on paper how you want the system to work and if you can't see how to make it work, come back with a specific question. All the best, Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
