[imp] why does Horde/IMP re-define mime types, and Dovecot issue(s)

[Chris H.]

Hello Michael, and thank you for your response.

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting "Chris H." <fbsd at 1command.com>:
>
>> Hello Michael, and thank you for your response.
>>
>> Quoting Michael M Slusarz <slusarz at horde.org>:
>>
>>> Quoting "Chris H." <fbsd at 1command.com>:
>>>
>>>> Hello Chuck, thank you for your response.
>>>>
>>>> Quoting Chuck Hagenbuch <chuck at horde.org>:
>>>>
>>>>> Horde, and all Horde apps, do not "redefine" any mime types, for  
>>>>>    PHP or otherwise.
>>>>
>>>> Good to hear.
>>>>
>>>>> It may be that your server is segfaulting.
>>>>
>>>> That does not appear to be the case; there are no indications that Apache
>>>> or Dovecot are stopping, or dying. There are no indications in any of the
>>>> logs, nor any cores on the system. I just wiped the disks and performed a
>>>> fresh install of everything (OS too). The results are still the same.
>>>> There are no errors in the Apache logs while using the imp/test.php to try
>>>> to find a problem. But attempting to connect to the IMAP(s) server 
>>>>   (Dovecot),
>>>> on the test.php page, the Dovecot reveals this in it's log:
>>>>
>>>> ####
>>>> dovecot: Aug 06 05:47:32 Info: Dovecot v1.0.rc2 starting up
>>>> dovecot: Aug 06 05:56:06 Info: imap-login: Disconnected:   
>>>> Inactivity:   rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 05:58:06 Warning: imap-login: SSL_accept() syscall 
>>>>     failed: EOF [127.0.0.1]
>>>> dovecot: Aug 06 06:00:06 Info: imap-login: Disconnected:   
>>>> Inactivity:   rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 06:02:06 Warning: imap-login: SSL_accept() syscall 
>>>>     failed: EOF [127.0.0.1]
>>>> dovecot: Aug 06 06:10:41 Warning: Killed with signal 15
>>>> ####
>>>>
>>>> NOTE: Killed with signal 15 is always whats emmited when shutting Dovecot
>>>> down. It's a normal response.
>>>>
>>>> ####
>>>> dovecot: Aug 06 16:08:46 Info: Dovecot v1.0.rc2 starting up
>>>> dovecot: Aug 06 16:12:16 Info: imap-login: Disconnected:   
>>>> Inactivity:   rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 16:14:16 Warning: imap-login: SSL_accept() syscall 
>>>>     failed: EOF [127.0.0.1]
>>>> dovecot: Aug 06 16:16:16 Info: imap-login: Disconnected:   
>>>> Inactivity:   rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 16:18:16 Warning: imap-login: SSL_accept() syscall 
>>>>     failed: EOF [127.0.0.1]
>>>> dovecot: Aug 06 16:54:32 Info: imap-login: Disconnected:     
>>>> rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 16:54:33 Info: imap-login: Login: user=<joetest>,  
>>>>    method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> dovecot: Aug 06 16:54:34 Info: IMAP(joetest): Disconnected: Logged out
>>>> dovecot: Aug 06 16:55:34 Info: imap-login: Disconnected:   
>>>> Inactivity:   rip=127.0.0.1, lip=127.0.0.1, TLS
>>>> ########
>>>
>>> You shouldn't be using TLS to login w/PHP 4.
>>
>> I'm not sure I understand. I'm using TLS on 9 other mail servers,
>> all of which use php4.4, and Horde/IMP. They all run flawlessly.
>> Are you suggesting there is a security issue? These are all running
>> IMP/Horde via https and Apache and PHP both have SSL compiled into
>> them.
>
> From config/servers.php:
>
>  *           NOTE: Due to limitations within PHP, IMP can only support auto-
>  *                 detection of namespace parameters with IMAP TLS 
> connections
>  *                 (e.g 'imap/tls') if using PHP version 5.1.0 or greater.
>  *                 If using a version of PHP less than 5.1.0, the following
>  *                 options are available:
>  *                 1. RECOMMENDED - If a secure IMAP connection is 
> needed, use
>  *                    a direct connection to a SSL enabled IMAP port
>  *                    (e.g. 'imap/ssl').
>  *                 2. If you absolutely must use TLS, then it is REQUIRED to
>  *                    define the 'namespace' parameter (see below).
>
> Maybe you have 'namespace' defined and, thus, are working around this 
>  issue.  If not, there is no reason IMP should work since TLS 
> requires  stream_socket_enable_crypto(), which only appeared in PHP 
> 5.1.
>
> michael

Thanks for the clarification. Appreciated.

--Chris

>
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
> -- 
> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>



-- 
panic: kernel trap (ignored)



-----------------------------------------------------------------
FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006
/////////////////////////////////////////////////////////////////