"Greg Saylor" <[EMAIL PROTECTED]> writes: > > 4) Delete .../gsaylor2/.qmail*.
[...] > Does this mean that everytime I want to protect a POP3 account I have to > go in and manually delete these?... I note that when I go to the > tdma.cgi URL and login that it is what makes these modifications.... Is > it making the wrong modifications for some reason?.... I want this to be > relatively easy to enable/disable on a per-user basis without me having > to login and modify .qmail files all the time... TMDA and tmda-cgi are sometimes a little out-of-sync. I suspect that the reason those dot-qmail files get added is because they're in the skel directory that tmda-cgi uses as a template when it adds a new user. Part of the problem is the issue I said I wouldn't bother explaining. Here's a condensed version. qmail looks for dot-qmail files in the home directory of the system user that controls the recipient address of a particular email. If you want to dive deep into qmail, you can make sense of this. For now, the simple explanation is that when vadddomain creates a new domain, it puts a line in /var/qmail/users/assign that tells qmail that the system user is 'vpopmail' and that the "home directory" of the particular domain (net-virtual.com) is /usr/local/vpopmail/domains/net-virtual.com. So qmail only looks for dot-qmail files in the .../net-virtual.com directory. In order to allow users to have their own dot-qmail files, the vdelivermail program, which gets run from .qmail-default, looks for a .qmail file in the user's directory, .../net-virtual.com/gsaylor2, and attempts to process that file like qmail would. It fails to do several important things that are a part of the normal dot-qmail processing, though. It only looks for a file named .qmail; never for any extension address files (.qmail-EXT). It does not change the directory to .../gsaylor2 and set $HOME correctly. So software that executes from .../gsaylor2/.qmail has a completely non-standard environment. This is the root cause of TMDA looking for crypt_key in .../net-virtual.com/.tmda rather than in .../gsaylor2/.tmda. As far as TMDA knows, the home directory is .../net-virtual.com. Ugh. Back to your question... As long as a .qmail file exists in a user's directory (.../gsaylor2/.qmail), the vdelivermail will attempt to parse it and perform the directives in it, in its own horribly wrong fashion. So, you're much better off without the .qmail file. The .../gsaylor2/.qmail-default file is never noticed by either qmail (it's not in the home directory) or vdelivermail, so it doesn't matter. It's just garbage lying around. I'd remove both of these from skel, so they don't get copied into individual users' directories when you enable TMDA for a user. For now, you'll still have to create the .../<domain/.qmail-<user> and .../<domain>/.qmail-<user>-default files by hand. Hopefully tmda-cgi will address this in an upcoming release. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
