|
From: Brian P. <br...@un...> - 2005-06-29 05:35:43
|
On Wednesday 29 June 2005 14:59, Paul Lesneiwski wrote: > Brian Parish wrote: > > On Wednesday 29 June 2005 13:35, p dont think wrote: > >>Brian Parish wrote: > >>>This is a RHEL3 machine with all updates. Installed the latest stable > >>>version using the RPM. Ran the config script but made minimal changes. > >>> > >>>When I attempt to browse I get: > >>> > >>>The connection was refused when attempting to contact > >>> my.server.name:2096 > >> > >>2096? That's very non-standard; you should tell us more about your > >>setup if that's normal for you. > >> > >>>There's no firewall running. I can telnet to my imap server. Just > >>> can't get as far as a login prompt for SM. > >> > >>Read this: > >> > >>Posting Guidelines: > >> > >>http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines > >> > >>Then post what you find from your mail log. > > > > Apache/1.3.33 > > dovecot-0.99.14-1.1.el3.rf > > RHEL3 updated to be current > > > > Nothing related shows in the mail log. In the httpd access log I get: > > > > "GET /webmail/src/configtest.php HTTP/1.1" 302 304 > > > > as a result of attempting to browse to the configtest, but nothing in the > > httpd error log. Nothing in the system log. > > What is the output of that script? None - connection refused > > > I have no idea why the connection is being attempted on 2096. Where is > > this determined? > > You're joking, right? ;) Please review your SquirrelMail configuration > file by hand or by using the config/conf.pl script. Server settings > including port number are contained therein. > > > Not much help I guess. Any idea where to look next? > > After reviewing your server setup in SM config, check configcheck and/or > login and watch mail log. > > > - paul Well it may well be an apache issue, but I have a couple of difficulties with your comments: The port settings in the config file are to do with imap and smtp - these are set at the standard 143 and 25. Nowhere do I see 2096. An earlier response stated that 2096 is very non-standard, so it seemed reasonable to wonder where that number was coming from. Presumably it's something to do with the way apache is configured. This is probably not a SM issue as you suggest, but given that I can get to html pages OK and it's supposedly a bog standard apache install, I had to wonder. And again - there are no messages to look at in the mail log - presumably because I don't get far enough to even attempt a login. Anyway - I'll go back to my apache config and try to work out what the issue is there. thanks Brian |