Joshua Alexander <[EMAIL PROTECTED]> writes: > New issue for you folks... I'm so close to getting this fully functional... > > TMDA is working fine for main accounts, but not for other email > accounts set up under these main accounts. To get TMDA to work with > these, it's going to have to be told to use a slightly different > DELIVERY and $home.
I don't know what this means.... Specifically, can you describe (or point me to docs) about what the difference is between a "main account" and an account "under" a "main account"? > I'm seeing this in my exim_mainlog: > > Child process of tmda_virtual_pipe transport returned 75 (could mean > temporary error) from command: /usr/bin/python2 I have no idea of the cause of this. Some MTAs capture the standard output of the program and write that to the log. Does Exim do this, or can it be configured to do this? > I tried to write my own vuserinfo script and use it via -S, but with > or without that this same error gets reported. My script logs its > usage, and I can tell it gets used when I test via the command line, > but when Exim calls TMDA, TMDA seems to be failing before getting to > that point. > > > In any case, TMDA is not writing to any log files I can find. In > /etc/tmdarc I have: > > > LOGFILE_DEBUG = "/var/log/tmda.debug" > LOGFILE_INCOMING = "/var/log/tmda.in" > LOGFILE_OUTGOING = "/var/log/tmda.out" /etc/tmdarc is read fairly early in the initialization sequence of tmda-filter, which is why I commented above that I'm at a loss as to what's going on. Could you post your transport definition as well as any other Exim configuration that might affect the tmda-filter invocation? Perhaps some of the Exim users here can spot something that might be causing a problem. > and the tmda.debug file was written to when I was fooling around on > the command line, but it doesn't get written to when Exim is calling > it... no TMDA_DELIVERY_FAILURE file is showing up anywhere I've > looked, nor are logs being written anywhere under /home/<mainuser>/ Have you done a "find / -name TMDA_DELIVERY_FAILURE" to search your entire system? tmda-filter writes to "~/TMDA_DELIVERY_FAILURE" so the setting of the HOME environment variable or possibly the home directory (from /etc/passwd) of the user that is actually running tmda-filter will be used. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
