MailAuth Options not appearing

[tyreking]

Hello - I am trying to implement a new install of EGW on a Debian Wheezy Install.
I’ve tried installing source, and also have now moved to the .deb packages provided through the website.

I can perform the installation fine, yet am unable to find out where to input the incoming mail server for authentication when choosing mailAuth. The Documentation States it should be in Step 2 of Setup, but the option doesn’t appear for me.

I’ve tried looking at the Database schema to find out where the option should be under the config table, yet no luck at all.
Can someone provide some insight into this on how to activate MailAuth?

[Ralf_Becker_Stylite]

Hi,

Hello - I am trying to implement a new install of EGW on a Debian Wheezy
Install.
I’ve tried installing source, and also have now moved to the .deb packages
provided through the website.

I can perform the installation fine, yet am unable to find out where to
input the incoming mail server for authentication when choosing mailAuth.
The Documentation States it should be in Step 2 of Setup, but the option
doesn’t appear for me.
Are you talking about 1.8 or 14.1 beta?

1.8: Setup >> Step 2: Configuration >> *Standard mailserver settings
(used for Mail authentication too)

14.1: was not there, re-added it now with r46972:

http://svn.stylite.de/viewvc/egroupware?revision=46972&view=revision

I’ve tried looking at the Database schema to find out where the option
should be under the config table, yet no luck at all.
Can someone provide some insight into this on how to activate MailAuth?

–
Ralf Becker
Director Software Development

Stylite AG

Morschheimer Strasse 15 | Tel. +49 6352 70629 0
D-67292 Kirchheimbolanden | Fax. +49 6352 70629 30

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 31158 Kaiserslautern Germany

[tyreking]

Version info from /setup/

eGroupWare Version 1.9.020 (installed from apt-get Suse Source).

Replaced the files and options appear just fine. Doesn’t seem to be authenticating at all regardless of the options setup:
Server being localhost or an external, with any of authentication options (username/emailaddress).
Reviewing the logs doesn’t show any connections reaching either the POP3 or IMAP server.
Finally, inside the EGW suite it shows an audit trail of the accounts I’ve tried to login, but as mentioned above it doesn’t seem to actually doing any authentication checks. FWIW its worth, LDAP / Active Directory hasn’t worked either. Have met all dependencies in installation check. Sorry is this is branching off to a new topic - this could be semi related.

[Ralf_Becker_Stylite]

Hi,

Version info from /setup/

eGroupWare Version 1.9.020 (installed from apt-get Suse Source).

Replaced the files and options appear just fine. Doesn’t seem to be
authenticating at all regardless of the options setup:
Server being localhost or an external, with any of authentication options
(username/emailaddress).
Reviewing the logs doesn’t show any connections reaching either the POP3 or
IMAP server.
Hmm, hard to believe. I reworked the code before replying to you and
tested with SSL and automatic STARTTLS on IMAP (143).

Maybe you misunderstood some of the options, just post what you filed in
in setup and what your username in EGroupware and on the mailserver are.

Finally, inside the EGW suite it shows an audit trail of the accounts I’ve
tried to login, but as mentioned above it doesn’t seem to actually doing any
authentication checks. FWIW its worth, LDAP / Active Directory hasn’t worked
You must have some other problem. LDAP as well as AD are used in many
installations. Thought both can be trick with certificates, when using
ldaps (ssl), as validating certificates is switched on in PHP/LDAP by
default, but there’s no certificate store by default. This causes all
ldaps connections to fail!

Most easy, but of cause not a good idea security wise, is to disable
certificate validation by adding the following to OpenLDAP’s
/etc/openldap/ldap.conf:

TLS_REQCERT never

Ralf

–
Ralf Becker
Director Software Development

Stylite AG

Morschheimer Strasse 15 | Tel. +49 6352 70629 0
D-67292 Kirchheimbolanden | Fax. +49 6352 70629 30

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 31158 Kaiserslautern Germany

[tyreking]

Hmm, hard to believe. I reworked the code before replying to you and

I just wiped the entire installation and reinstalled on this wheezy box
(apt-get install egroupware-epl) which installed a number of other
related egroupware packages. This time I let the package manager
configure header.inc.php - and I was able to login using SQL
authentication as expected.

I changed the 3 files as you posted a few days back, and the mail
configuration reappeared.

Maybe you misunderstood some of the options, just post what you
filed in

in setup and what your username in EGroupware and on the mailserver
are.
Server name: 127.0.01
IMAP (143)
Username is different from the SQL admin user.
IMAP server doesn’t register any connections whatsoever, but when I
login as admin and setup mail delivery it pulls the IMAP mailbox just
fine, and IMAP working fine on a few other apps on the server. Just for
fun I switched the IMAP server to another one we have in the org which
is in full time use, and noticed no connection attempts as well.

You must have some other problem. LDAP as well as AD are used in many
installations. Thought both can be trick with certificates, when using
ldaps (ssl), as validating certificates is switched on in PHP/LDAP by
default, but there’s no certificate store by default. This causes all
ldaps connections to fail!

You are right, I then tried LDAP and Active Directory using very
standard settings (local or remote servername) and a BaseDN ie
dc=domain,dc=com that should be able to search through the various OUs
in place on the different servers. Upon attempting to login using many
different accounts after clicking the submit button it returns
immediately with Bad User ID error message. I would think I have all
dependencies in place, pass the Installation test without issues. Just
seems to be that EGW isn’t communicating to any external sources on this
machine for some reason which is beyond me - I can’t seem to figure out
if I can throw the app into a debug mode to get more details at this
stage, so at a standstill.

Thanks so far,
Dave