On Mon, Jun 09, 2008 at 12:59:56PM +0200, Marco wrote:

No problem. Actually I find it quite amusing to see the levels of ego in certain software projects, and it's tempting to get drawn in sometimes.

I was originally replying to a message which screamed "BUG!!!" in the Subject line, and so I admit I was rather brusque in my response (*).

I find it strange that when an application like sqwebmail works happily with a bunch of different webservers, but not with a newcomer that no-one has heard of before, that automatically it's sqwebmail which is assumed to be at fault.

Essentially, this isn't anything to do with sqwebmail, as it just runs inside a CGI environment. It's a difference of interpretation of the CGI spec between Apache (and a bunch of others) in the blue corner, and Hiawatha in the red corner.

Like it or not, Apache is the de-facto standard. If a CGI app works in Apache but doesn't work in Fooserver, then you should be asking why Fooserver doesn't run the CGI, not why the CGI doesn't work under Fooserver.

Anyway, sqwebmail is just a CGI stub, which sends messages down a socket to sqwebmaild. Since you say it works for the login page, then I suggest you look at resource limits and the process environment. Sqwebmail does rely on a number of environment variables being set, and the CGI sends them down the socket (up to a hardcoded size limit).

You could try running a simple CGI under both Apache and Hiawatha:

#!/bin/sh echo "Content-Type: text/plain" echo "" printenv

and compare the outputs. Maybe Hiawatha doesn't set some variable which Apache does.

Regards,

Brian.

(*) http://www.catb.org/~esr/faqs/smart-questions.html#id306810 http://www.nabble.com/BUG%21%21%21-td14395843.html