"Greg Saylor" <[EMAIL PROTECTED]> writes: > > 3) Edit /usr/local/vpopmail/domains/net-virtual.com/.qmail-default. > > It should look like this: > > > > | preline /usr/local/bin/tmda-filter -S > >/usr/local/vpopmail/bin/vpopmail-vdir.sh > > | /usr/local/vpopmail/bin/vdelivermail '' bounce-no-mailbox > > Secondly, when I do item #3 above, all of a sudden it is protecting *ALL* > of my email accounts and I don't want that...
Ah. The .qmail-default file in a vpopmail domain directory is used for all users in that domain. Fortunately, qmail provides a way around this. > Is there something in your later instructions which prevent this from > happening?... I undid it because my test confirmed that it wasn't doing > what I needed and did not go any further.. To protect individual accounts, put the above lines in user-specific dot-qmail files. For your gsaylor2 example, you would want to have the two lines from step 3 in .../net-virtual.com/.qmail-gsaylor2 and you need to make .../net-virtual.com/.qmail-gsaylor2-default a symbolic link to .qmail-gsaylor2. The .qmail-default file should then only contain the vdelivermail line and not the tmda-filter line. More specific dot-qmail files override less specific ones, so when mail comes in for gsaylor2, qmail first looks for .qmail-gsaylor2 and if it doesn't find it, it looks for .qmail-default. The dot-qmail man page explains how this works in the section called EXTENSION ADDRESSES. This may not work exactly as I've outlined it because you have a hyphen in the name of your domain. I'm not sure what the vadddomain program does in that case. If the mail for gsaylor2 does not appear to be handled by TMDA, post the lines from your /var/qmail/control/virtualdomains file that reference net-virtual.com. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
