Bluehost.com Web Hosting $6.95

Re: [courier-users] sqwebmail: Transport endpoint is not connected

This is a discussion on Re: [courier-users] sqwebmail: Transport endpoint is not connected within the Courier-Imap forums, part of the Mail Servers and Related category; --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 08, ...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-09-2005
Kevin Coyner
 
Posts: n/a
Default Re: [courier-users] sqwebmail: Transport endpoint is not connected


--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



On Tue, Mar 08, 2005 at 06:30:09PM -0500, Sam Varshavchik wrote......

> Jacob Friis Larsen writes:
>=20
> >>> If I go to http://192.168.130.10/cgi-bin/sqwebmail/ I get "Internal=

=20
> >>Error
> >>>
> >>> The webmail system is temporarily unavailable. An error occured in
> >>> function write: Transport endpoint is not connected"
> >>>
> >>> Any idea what I have done wrong and where to look?
> >>
> >>You need to start sqwebmaild. See INSTALL.

> >
> >It is started. I see it in ps aux

>=20
> The above error is reported when the sqwebmail cgi-bin stub cannot
> connect to the socket that sqwebmaild is listening on.
>=20
> The most common reason is that sqwebmaild is not running, but you
> claim that it is.
>=20
> The second most common reason is that the permissions on the cgi-bin
> stub binary are wrong. The cgi-bin stub must be setuid root.



I just built a new email server using courier/sqwebmail and had the same
problem. My build was on a debian box so everything came in .deb
packages, but I believe upstream source downloads might have the same
problem. Anyway, the process ID's for all courier programs reside in
/var/run/courier. In my build of courier, the default permissions for
/var/run/courier were 770 with uid/gid of daemon.daemon. Getting
sqwebmail to run was solved by ...

chmod 755 /var/run/courier

Indeed, I checked an old email server that has been running
courier/sqwebmail for a long while now, and its permissions were 755,
not 770 as in the default build.

FYI there is a bug filed already in the Debian BTS for this.

Kevin



--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCLjlYqPceVIzhGUERApk/AKDRL+yyuhtY1jjj659LdyrPzqR3YQCgqBL7
mI8gErpGURDSEl6jscYkIR8=
=o6Pe
-----END PGP SIGNATURE-----

--gBBFr7Ir9EOA20Yy--


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 06:15 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0