We recently moved our mail server from a 32-bit SuSE SLES 9 system to a 64-bit SuSE SLES 9 system.

The versions of courier-authlib-0.57, courier-imap-4.0.4 and maildrop-1.8.1 are working fine, but sqwebmail-5.0.6 is not working properly.

The configure line I used for sqwebmail is:

env \ COURIERAUTHCONFIG=/opt/courier-authlib/bin/courierauthconfig \ CPPFLAGS=-I/opt/courier-authlib/include \ LDFLAGS=-L/opt/courier-authlib/lib/courier-authlib \ ./configure --prefix=/opt/sqwebmail \ --enable-cgibindir=/srv/www/cgi-bin \ --enable-imagedir=/usr/share/apache2/icons \ --enable-imageurl=/icons/ \ --enable-hardtimeout=7200 \ --enable-softtimeout=1200 \ --enable-maxpurge=90 \ --with-ispell=/opt/ispell/bin/ispell \ --disable-autorenamesent

I've configured apache2 on the web server for sqwebmail and generated both the secret key and self signed certificate using openssl.

The server name of the apache2 server is foobar.dkp.com, which is redirected to https://foobar.dkp.com/cgi-bin/sqwebmail.

When Firefox performs the redirect, it indicates an Internal error in the write function due to "transport agent not connected", a string corresponding to a value of errno.

I've inspected the code and found the code which produces the error. It's in the force_write function which is called from the send_environ function at line 127 in sqwebmail/sqwebmaild.c.

I think this is a 32-bit vs 64-bit problem because I can successfully install and use sqwebmail on the old 32-bit SuSE SLES 9 system using the configure line shown above.

Has anyone run into this kind of problem and devised a fix or work around?

Any assistance would be greatly appreciated.

Mark