SupportSuite POP3 from Exchange 2007

[Ixian]

This is driving me insane.

Can someone please tell me what to do from here? I have the latest IMAP c-lient sources, I have build them, I have the latest PHP 5.2 sources, configured them with-imap pointing to the c-client build directory, ran make, yet it isn't bulding my imap.so extension and I am about to go mad.

Can someone please walk me through this? It's completely ridiculous this still exists but at this point I'll do whatever I need to do to get the imap extension without Kerberos built so I can actually use POP3 with my Exchange server

[miketree]

I'm having this issue too.

[plusbryan]

Still having same problem on HOSTED kayako. Perhaps they can upgrade their own PHP?

[supportskins]

Contact Kayako Support, they should be able to give you a definate answer. No "client" is in a position to answer that

[plusbryan]

Originally Posted by MikeMSD

To resolve this I recompiled IMAP C-Client and PHP IMAP without Kerberos support.

Mike, would you mind going into more detail about your solution? I sure would appreciate a step-by-step. Thanks!

[D0ubleStakked]

Hi Everyone,
To join into this discussion, we are evaluating v3.20.02 internal in our network, and we also have Exchange Server 2007.
We have tried several of the suggestions in this thread, and nothing has worked for us.
My email administrator is currently looking into the connector configurations.

As a tangent, I will note that we use spiceworks v2.0 internally and we use their HelpDesk feature that has POP3 SSL and SMTP connections into our Exchange 2007 mailserver, and that does work. We did find that we had to change the default SMTP outbound port to 587 instead of port 25, but that wouldn't impact the POP3 SSL settings.
Of course spiceworks is written in "Ruby on Rails", so we're talking a different programming language.

Our LAMP VM that is running Kayako is running PHP 5.1.6, and so we're about to attempt an upgrade to the latest version of PHP.
If that doesn't work, then we're going to attempt a custom compile of PHP.
-Brian

[D0ubleStakked]

just to post my latest status...

1.) I have begun looking into "kinit" for Unix, but its a world I don't know that well, so I'm slow to get myself muddy here.

2.) I'm compiling PHP 5.2.5 for Fedora Core 6 on my LAMP. It compiled, but it won't install b/c PHP 5.1.6 is already there and my LAMP won't accept the upgrade....going to do a fresh install of my LAMP without PHP, and then install only my custom build of PHP 5.2.5...will see if I can compile PHP 5.2.5 --without-kerberos to see if that helps at all.

3.) I am installing a second SupportSuite trial on a windows server to see if that gets me past this.

will keep you all posted,
-Brian

[John Haugeland]

The fundamental problem here is that Exchange 2007 has a bug wherein it incorrectly broadcasts malformed Kerberos auth tokens, even if Kerberos is completely disabled. PHP's IMAP driver is unable to understand what it sees, because it makes a good faith attempt to interpret the Kerberos tags, and shuts down the stream when it fails, fearing security breach.

Ruby on Rails' driver should do the same thing, but does not.

There are two ways to fix this, and there is one step that we believe should be taken by any customer undergoing these problems.

1) You can fix this by running a not-broken mail transfer agent. Other versions of Exchange do not have this defect, nor do MTAs like QMail, Postfix, Exim, et cetera. Unfortunately, Exchange has a lot of heavily used business logic, and so retreating even to a prior, correctly functioning version is frequently unrealistic for certain businesses.

2) You can fix this by recompiling PHP's IMAP driver without Kerberos support. When the IMAP driver doesn't know about Kerberos, it discards the auth tags, and begins to treat the stream as a normal stream (in the way that Ruby's driver does, but shouldn't.) This process is platform specific, and sometimes involves minor adjustments to your SSL configuration. Instructions on such a recompile can be found here:
PHP: IMAP - Manual

We strongly recommend that you call Microsoft's support phone number as paying customers and complain that they have allowed this bug to survive for in excess of a year. Microsoft tends to react once customers begin to complain.

Again, this is a defect in Exchange 2007. Switching to any correctly functioning mailserver, including other versions of Exchange, will resolve this problem. This is the fastest, and frequently the easiest, fix for the defect.

Thank you for your understanding.

- John Haugeland
Kayako Development Staff

[D0ubleStakked]

just to add some more details, I was able to get the Mail Parser to work immediately with the following configuration:

O/S: Windows XP Professional
WebServer: IIS 5.1
PHP 5.2.5 w/ php_imap.dll extension enabled

Fetch Type: POP3 SSL

My final install still needs to be on Linux, so I am going to follow John's advice about recompiling the Shared object(.so) for the IMAP driver.

-Brian