John Lockwood wrote:
The server is running Mac OS X 10.3.5 (Server), with SquirrelMail 1.4.3a. I have specifically configured my server NOT to use SSL. The bug is that SquirrelMail is using SSL (i.e. HTTPS) when it should not only if if it configured to open a new read or compose window (rather than reusing the same window). It is therefore nothing to do with any SSL faults (if there are any) in Mac OS X Server.
Once again, please read the archives. This has been an issue with people using OS X even when not using SM thru SSL. OS X's SSL stuff still needs to be upgraded to the latest and greatest.
If I turn on the preference to compose a message in a new window or read a message in a new window I get an error. For example if I compose a message in a new window and send the message I get the following error displayed by my web-browser
Safari couldn't open the page https://mail.example.com:80/webmail/src/right_main.php?sort=6&startMessage=1&mailbox=INBOX because it couldn't establish a secure connection to the server mail.example.com
The same happens if I read a message in a new window and try to delete or go to next message.
My web/mail server is not configured to use SSL. Normal Squirrelmail access works via http and no error is produced if I turn of compose/read in a new window. Squirrelmail is therefore incorrectly using https instead of http (but only if using a new window).
I can reproduce the bug by: Turning on compose message in a new window and/or read message in a new window.
----------------------------------------------
My browser information: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-gb) AppleWebKit/125.5 (KHTML, like Gecko) Safari/125.9
Please include server info too. If Mac OS X, make sure it is fully up to date. There are SSL related bugs in OS X environment that cause similar problems that ultimately have nothing to do with SM. Please search mailing list for the solution if you don't already know how to approach the job.
My web server information: PHP Version 4.3.2 PHP Extensions (List) * 0 = xml * 1 = tokenizer * 2 = standard * 3 = sockets * 4 = session * 5 = posix * 6 = pcre * 7 = overload * 8 = odbc * 9 = mysql * 10 = mbstring * 11 = ldap * 12 = ftp * 13 = exif * 14 = dbx * 15 = curl * 16 = ctype * 17 = zlib * 18 = apache
SquirrelMail-specific information: Version: 1.4.3a Plugins (List) * 0 = compatibility * 1 = vlogin * 2 = attachment_tnef * 3 = autocomplete * 4 = view_as_html * 5 = forced_prefs * 6 = newuser_wiz * 7 = unsafe_image_rules * 8 = bug_report * 9 = message_details * 10 = windows * 11 = ldifimport * 12 = ldapquery * 13 = abook_take * 14 = username
My IMAP server information: Server type: other Server info: * OK [HIDDEN] server ready Capabilities: IMAP4rev1 AUTH=CRAM-MD5
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
--
squirrelmail-users mailing list
Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: squirrelmail-users@lists.sourceforge.net
List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
