Just upgraded to ASK 2.3beta, following the upgrade
instructions, I received no errors.
However, mail being received gets bounced with an error:
Below is an excerpt from my maillog file...
Apr 2 09:44:02 spxgate sm-mta[49252]:
h32Fi2xj049252: from=<bill@servplex.com>,
size=0, class=0, nrcpts=1, proto=ESMTP,
daemon=MTA, relay=[192.168.0.9]
Apr 2 09:44:02 spxgate sm-mta[49252]:
h32Fi2xk049252: from=<bill@servplex.com>,
size=889, class=0, nrcpts=1,
msgid=<5.2.0.9.0.20030402093406.02279f48@mail.serv
plex.com>, proto=ESMTP, daemon=MTA, relay=
[192.168.0.9]
Apr 2 09:44:03 spxgate sm-mta[49253]:
h32Fi2xk049252: to="|/home/peter/ask_inst
all/ask-2.3.beta3/ask.py --loglevel=5 --
logfile=/home/peter/ask.log --home=/home
/peter", ctladdr=<peter@servplex.com> (1001/1001),
delay=00:00:01, xdelay=00:00:
00, mailer=prog, pri=31140, dsn=5.3.0, stat=unknown
mailer error 127
Apr 2 09:44:03 spxgate sm-mta[49253]:
h32Fi2xk049252: h32Fi3xi049253: DSN: unkn
own mailer error 127
Apr 2 09:44:03 spxgate sm-mta[49253]:
h32Fi3xi049253: to="|/usr/local/ask2_2/as
k.py --loglevel=5 --logfile=/home/bill/ask.log --
home=/home/bill", ctladdr=<bill
@servplex.com> (1002/1001), delay=00:00:00,
xdelay=00:00:00, mailer=prog, pri=32
164, dsn=2.0.0, stat=Sent
I had to go back to my 2.2 backup in order to receive
email...
Peter
Logged In: YES
user_id=52555
Hello Peter,
That's a very important report. A few questions:
1) Does it *always* happens or only once in a while?
2) What does the sender get as a response?
3) Can you reproduce it easily?
4) Do you use procmail? If so, would it be possible to turn
VERBOSE=on inside your .procmailrc and send me the resulting
logfile?
Regards,
Paga
Logged In: YES
user_id=381130
Hello Pagi,
1) Always happens...
2) Sender gets a response that says the following email
address had permanent failure errors... Unknown Mailer Error
127.
3) Nope, no procmail... Just Sendmail.
Logged In: YES
user_id=381130
Here is a copy of what a user sees... Just noticed
something... env: python: No such file or directory
Wonder if that has something to do with it?
----- The following addresses had permanent fatal errors -----
"|/home/testuser/ask-2.3.beta3/ask.py --loglevel=5 --
logfile=/home/testuser/ask.log --home=/home/testuser"
(reason: 127)
(expanded from: <testuser@servplex.com>)
----- Transcript of session follows -----
env: python: No such file or directory
554 5.3.0 unknown mailer error 127
Reporting-MTA: dns; spxgate.servplex.com
Received-From-MTA: DNS; [192.168.0.10]
Arrival-Date: Wed, 2 Apr 2003 12:28:34 -0600 (CST)
Logged In: YES
user_id=381130
Here is a copy of what a user sees... Just noticed
something... env: python: No such file or directory
Wonder if that has something to do with it?
----- The following addresses had permanent fatal errors -----
"|/home/testuser/ask-2.3.beta3/ask.py --loglevel=5 --
logfile=/home/testuser/ask.log --home=/home/testuser"
(reason: 127)
(expanded from: <testuser@servplex.com>)
----- Transcript of session follows -----
env: python: No such file or directory
554 5.3.0 unknown mailer error 127
Reporting-MTA: dns; spxgate.servplex.com
Received-From-MTA: DNS; [192.168.0.10]
Arrival-Date: Wed, 2 Apr 2003 12:28:34 -0600 (CST)
Logged In: YES
user_id=52555
Hello Peter...
Hmmm...
That means python is not being found on your system using
the default PATH.
Please, send me the results of:
1) echo $PATH
2) type python
Regards,
Paga
Logged In: YES
user_id=381130
Path variable:
spxgate:peter# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/loc
al/bin:/usr/X11
R6/bin:/home/peter/bin
spxgate:peter#
spxgate:peter# python
Python 2.2.2 (#1, Nov 20 2002, 09:30:23)
[GCC 2.95.4 20020320 [FreeBSD]] on freebsd4
Type "help", "copyright", "credits" or "license" for more
information.
>>>
Python is found...
Logged In: YES
user_id=381130
Any more ideas on this?
Logged In: YES
user_id=381130
Found the problem...
in ask.py at the top you had: #!/usr/bin/env python
Python is installed (on FreeBSD anyway) in /usr/local/bin
Once I changed that, ask worked fine...
Logged In: YES
user_id=116253
This will be moved to the bug section, because the
documentation should state this somehow.