Solution... The problem turned out to be with vpopmail. I reinstalled/upgraded vpopmail (5.4.2) and TMDA of coarse worked like a champ. What threw me was delivery only stopped working when I enabled tmda, but the root cause was a bad vpopmail installation.
Thanks for the time Tim. Keep up the good work TMDA! Cheers, -Jonas On Tue, 2004-02-24 at 22:36, Jonas Valkiunas wrote: > > I can set tmda on a per domain basis by setting: > > /vpopmail/domains/anydomain.com/.qmail-default > > to: > > | preline /usr/bin/tmda-filter -S /vpopmail/bin/vpopmail-vdir.sh > > | /vpopmail/bin/vdelivermail '' bounce-no-mailbox > > > > Not being able to do this for all domains, I would like to set in on a > > per-user basis. So I set > > /vpopmail/domains/anydomain.com/.qmail-default > > to: > > | /vpopmail/bin/vdelivermail '' bounce-no-mailbox > > > > and create .qmail files at the domain level: > > cat /vpopmail/domains/anydomain.com/.qmail-user > > |preline -f /usr/bin/tmda-filter -c \ > > /vpopmail/domains/anydomain.com/user/.tmda/config > > |/vpopmail/bin/vdelivermail '' /vpopmail/domains/anydomain.com/user > > This begs two questions: 1) Does the config file set appropriate paths > for the "user" (ex. FILTER_INCOMING, LOGFILE_INCOMING, DATADIR)? and > 2) Is there a user/.qmail file? If so, you might want to rename it to > something else and test this configuration again. > > the email gets delivered, and my qmail log spews out: > > 2004-02-23 18:46:57.285045500 delivery 833: success: > > vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/vdelivermail:_valiases_processed/did_0+0+2/ > > > > (looks like a loop to me) > > Me too, although tmda-filter doesn't ever run vdelivermail, so if > vdelivermail is looping, it may not be TMDA's fault. You might try > putting a simple command like "|env > env.out" into the > anydomain/.qmail-default file (that doesn't run TMDA), running a > single email through the system and checking to see if the env.out > file exists (meaning that the .qmail-default file was used instead of > .qmail-user or .qmail-user-default). > > > User was created using the vadduser-tmda script with a config set by the > > default /usr/share/doc/tmda-1.0.2/contrib/vtmdarc > > Hmmm. This should be ok. > > > Enabling logging in the user .tmda/config file does not produce any > > output. > > That's strange, suggesting that the user's .tmda/config file isn't > being used at all. It does, however, match the implication of the > above loop, where TMDA appears not to be involved at all. > > > Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
