You're right, there is a missing file. I think WebKitEmail should look
like WebKit.cgi, only calling EmailAdapter.main instead of
On Wed, 2003-04-09 at 20:35, Alex King wrote:
> trying to setup email kit and having problems.
> when I unpack it, I get:
> $ ls -lR
> total 24
> drwxr-sr-x 2 alex alex 4096 Apr 10 13:17 Docs
> -rwxr-xr-x 1 alex alex 2756 Mar 21 2002 EmailAdapter.py
> -rw-r--r-- 1 alex alex 1199 Mar 21 2002 EmailServlet.py
> drwxr-sr-x 2 alex alex 4096 Apr 10 13:17 Examples
> -rw-r--r-- 1 alex alex 298 Mar 21 2002 Properties.py
> -rw-r--r-- 1 alex alex 52 Mar 21 2002 __init__.py
> total 8
> -rw-r--r-- 1 alex alex 4268 Mar 21 2002 QuickStart.html
> total 8
> -rw-r--r-- 1 alex alex 1118 Mar 21 2002 EmailForward.py
> -rw-r--r-- 1 alex alex 1 Mar 21 2002 __init__.py
> It seems to integrate into webware OK, but following the instructions:
> You must create a pipe handler for the email you wish to redirect. This
> is usually done as |/path/to/Webware/EmailKit/WebKitEmail
> /Path/To/Servlet ....
> But as you see in the listting there is no WebKitEmail executable in the
> listing above. Perhaps something has been left out of the tarball?
> Assuming that Adaptor.py should be used as the executable to pipe
> through (makes sense) I started hacking it to get it to run on my
> system. but is seems to be a set of functions only, no code in the top
> level to run anything.
> Just thought I'd fire this email to you before I go further, I will
> probably make it work because it seems the guts are there, but you might
> be able to offer helpful suggestions to me. Ie, is somthing missing
> from the tarball, it it not designed to work with webware 0.8, or am I
> just completely on the wrong track?
> Alex King