If python is not really specified in the enironment of the user then it would not be found.
I found that I have to use different versions of python for older/newer versions of things.
When you compile maybe you do it as root with a different shell than what is truly specified with your mail user.
The env would mean different things to root and another user (like vpopmail) when searching for a specific path of something.
I am not sure what user you are running mail as or what os but you could just su to the mail user and verify the env statement to see what path it comes up with for python and what version.
Sam
[EMAIL PROTECTED] wrote:
--> Friday, January 30, 2004, 3:05:24 PM, [EMAIL PROTECTED] wrote:Can I be helped in finding the location of this problem?Here's the big problem. I changed the first line in tmda-filter. >From "#!/usr/bin/env python" to "#!/usr/local/bin/python" However, "/usr/bin/env python" works from my shell. [EMAIL PROTECTED]:~$ /usr/bin/env python Python 2.3.2 (#1, Nov 2 2003, 16:06:48) [GCC 2.95.4 20020320 [FreeBSD]] on freebsd4 Type "help", "copyright", "credits" or "license" for more information. >>> (As a side note, ./compileall worked and still works) I can now change between these two and watch tmda work and not work. About 16 hours ago the former worked (unless tmda changed it...). Can anyone say why this changes absolutely everything? Perhaps the exit code is a problem with /usr/bin/env? If I may be so bold, why is /usr/bin/env used?
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
