[lug] Horde/Imp

[Sexton, George]

Let's back up. Can you connect to localhost on port 143 using telnet?

telnet localhost 143

If not, check xinetd configuration to ensure that IMAP is allowed from
localhost.

Here is my entry:


$servers['imap'] = array(
    'name' => 'IMAP Server',
    'server' => 'mail.mhsoftware.com',
    'protocol' => 'imap',
    'port' => 143,
    'folders' => '.IMAP/',
    'namespace' => '',
    'maildomain' => 'mhsoftware.com.com',
    'smtphost' => 'mail.mhsoftware.com',
    'realm' => 'mhsoftware.com',
    'preferred' => ''
);

If this doesn't resolve it, take a look at your maillog, messages, and
secure files. There are usually tips in there.


-----Original Message-----
From: lug-admin at lug.boulder.co.us [mailto:lug-admin at lug.boulder.co.us]On
Behalf Of D. Stimits
Sent: 17 June, 2002 4:26 PM
To: lug at lug.boulder.co.us
Subject: Re: [lug] Horde/Imp


"Sexton, George" wrote:
>
> You might try taking SSL out of the protocol definition.
>
> I think that unless you are using real CA signed certs, there is some
extra
> configuration that has to be done.
...

One more additional note, from some debugging (including removing ssl or
not, but mozilla works with or without ssl on the imap itself). In the
imap_open calls of IMP.php, if I remove the @ symbol to get error
messages, I get this message if I have ssl off (and /ssl is added if ssl
is on, otherwise it is the same):

Warning: Couldn't open stream {localhost:143/imap} in
/var/www/html/horde/imp/lib/IMP.php on
line 319

[the variation would be instead {localhost:143/imap/ssl}, no difference]

If I could figure out how to debug php's imap_open based on the above
message, the problem would likely be solved (and I do know that
localhost port 143 imap is running and responds properly to mozilla
email client).

There is a second warning that is maybe related, but if I do not use
ssl, it shouldn't matter (the warning is still there):
Warning: Certificate failure for localhost: self signed certificate:
/C=--/ST=SomeState/L=SomeCity/O=SomeOrganization/OU=SomeOrganizationalUnit/C
N=localhost.localdomain/Email=root at localhost.localdomain
(errflg=2) in
Unknown on line 0

I'm wondering if maybe cert failure is a problem even when I tell it not
to use ssl, and if not, then where do I verify what and how it looks up
the user? Is there debug mode available?

D. Stimits, stimits at idcomm.com
_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug