phpgroupware-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-users] Email authentication problem 0.9.16RC3


From: Miguel Koren OBrien de Lacy
Subject: [Phpgroupware-users] Email authentication problem 0.9.16RC3
Date: Fri, 27 Feb 2004 01:50:37 -0200

I'm trying to set up email authentication using 0.9.16RC3 of phpGroupware (On 
Fedora 1
with phpGroupware on MySql). I got the system set up correctly for SQL 
authentication,
created groups, users and set up the administration email parameters using IMAP 
(and
POP3) with ip instead of server names for the imap and smpt server. I then 
tested that
I can access the email application (site configuration) without setting special
preferences for the admin user. I sent out a test email without any problems. I 
did
not configure email further because my objective is not to use email inside
phpGrpupware but to authenticate users so they have just one password for 
email, samba
and groupware. I access phpGroupware using SSL.

I get a warning at the top of the page when I access the email app, like this:

Warning: imap_open(): Couldn't open stream {10.2.252.2:143}INBOX in
/opt/phpgroupware/email/inc/class.mail_dcom_imap.inc.php on line 214

but it seems to work. This happens with IMAP/Courier/Standard login (and any 
IMAP
combination). If I change it to POP-3/Courier/Standard the warning goes away 
the first
time I access the email app, but makes no difference to my main problem of
authenticating users. If I log in again with POP-3 configured and use the email 
app, I
get this error and it does not work at all:

Warning: imap_open(): Couldn't open stream {10.2.252.2:110/pop3}INBOX in
/opt/phpgroupware/email/inc/class.mail_dcom_pop3.inc.php on line 184

 source: email class.mail_msg_base.inc.php

called from: /phpgroupware/index.php, mail_msg: ensure_stream_and_folder(),
called_from: from mail_msg_base: loginerr_tryagain_buggy_cert FOR
/phpgroupware/index.php, msg_bootstrap: ensure_mail_msg_exists(), called_by:
email.boindex.index_data LINE 353

 imap_last_error: [Certificate failure for 10.2.252.2: self signed certificate:
/C=--/ST=SomeState/L=SomeCity/O=SomeOrganization/OU=SomeOrganizationalUnit/CN=localhost.localdomain/address@hidden
tried RH bug recovery?: [1] 

When I switch the preferences to authenticate with Mail (having IMAP defined) I 
can't
log in. By looking at the logs I get the feeling that phpGroupware is not 
sending the
mail server (the same physical server) the user name. This is what the
/var/log/maillog shows (having IMAP in the email administration setup):

Feb 26 23:32:44 TBNET imapd[24585]: imap service init from 10.2.252.2
Feb 26 23:32:44 TBNET imapd[24585]: Authenticated user=admin host=tbnet 
[10.2.252.2]
Feb 26 23:32:53 TBNET imapd[24585]: Logout user=admin host=tbnet [10.2.252.2]
Feb 26 23:34:21 TBNET imapd[24586]: imap service init from 10.2.252.2
Feb 26 23:34:21 TBNET imapd[24586]: Command stream end of file, while reading 
line
user=??? host=UNKNOWN
Feb 26 23:34:31 TBNET imapd[24587]: imap service init from 10.2.252.2
Feb 26 23:34:32 TBNET imapd[24587]: Command stream end of file, while reading 
line
user=??? host=UNKNOWN

The first lines show access from within the email application. The last lines 
show
where I tried to log in twice (in case I made a mistake with the password). 

This happens when I have POP-3 set up:

Feb 27 00:27:40 TBNET ipop3d[24991]: pop3 service init from 10.2.252.2
Feb 27 00:27:40 TBNET ipop3d[24991]: Command stream end of file while reading 
line
user=??? host=UNKNOWN
Feb 27 00:27:51 TBNET ipop3d[24992]: pop3 service init from 10.2.252.2
Feb 27 00:27:51 TBNET ipop3d[24992]: Command stream end of file while reading 
line
user=??? host=UNKNOWN

I checked with telnet to port 110 that the user is able to log in.

I'm curious about the user=??? message.

Any ideas of what could be wrong? Are the IMAP errors (when having POP-3 
defined)
somehow related to the fact that I use SSL?

Miguel

--
Konsultex Informatica (http://www.konsultex.com.br)


-- 
Esta mensagem foi verificada pelo sistema de antivĂ­rus e
 acredita-se estar livre de perigo.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]