Topic: imp 3.0

[aaron]

Does anyone know of a how-to on upgrading imp from 2.2.7 to 3.0?

Thanks

[Rich Lafferty]

Sometime, sometime. Seriously, it's not an easy upgrade, as IMP 3.0 requires
PHP 4.1, so it's also a PHP upgrade. I *do* plan on figuring it out, though, I
just haven't had time.

Cheers,

-Rich

[Dan Brown]

Rich, I'm sure you'd know better than I, but it seems to be working with my PHP 4.0.6 installation (I did install the PEAR archive from horde.org, though).

[Rich Lafferty]

Yes, it'll work with PHP 4.0.6 and the PEAR from 4.1 (that's what's on horde.org).
That's a messy way to package it up, though, so (putting on my Horde hat) the
official line is that it requires PHP 4.1.

I've also got a system that's having unusual IMAP problems using Arvin's PHP
4.0.6 rpms that I haven't quite tracked down yet -- I'm not sure it's the
IMAP support that's causing the problem, but I'm not sure it *isn't*, either.

I'll see if I can either package it up or do a HOWTO this weekend.

-Rich

[Pierluigi Miranda]

Rich Lafferty wrote:

> I've also got a system that's having unusual IMAP problems
> using Arvin's PHP
> 4.0.6 rpms that I haven't quite tracked down yet -- I'm not
> sure it's the
> IMAP support that's causing the problem, but I'm not sure it
> *isn't*, either.

As far as I understand, it seems to be a PHP 4.0.6 bug. I looked through the bug list and found reference to this problem: the solution proposed was the download of the latest imap support from CVS and PHP recompilation.

To simplify my work, I downloaded and made 4.1.0 version instead...

It works, but issues some warnings using Horde 1.2.3 and IMP 2.2.3 on my old ESSG 4.0.1 - a deprecated mysql_query_db(), if I remember well. Editing the IMP mysql db include file replacing calls to mysql_query_db() with mysql_query() solved the problem.

--

Pierluigi Miranda

[Dan Brown]

You'd be seeing those same errors with 4.0.6; I think adjusting the error level in php.ini will solve them.

[Rich Lafferty]

The "unusual IMAP problems" involved three (!) users with a single-quote in their passwords, and a bug in IMP 3.0 that SQL-escaped passwords. It's fixed
in IMP's CVS, and will be fixed in 3.1. The PHP RPMs seem fine. So now it's just
the problem of finding tuits.

-Rich

[Trevor Wendt]

Has anyone been able to, or would be willing to, put a How-To together on upgrading IMP to v.3.0 on SME V5?