| Response | |
|
********** This is an automated reply to your message to Email Abuse. ********** Your message has been delivered to our email abuse department. This department handles complaints from users that are receiving unwanted email. We try our best to investigate all reports of abuse. If we determine that the email you reported was in fact sent from an email address at one of our domains, or by way of computers operated by us, we will take the appropriate action. If you did not include the original "message headers" along with your message, please do so by replying to this message, leaving the subject line intact (which contains our tracking identification), and including all email headers. Email headers show specific details regarding the source provider, path, originating program, and destination of the message which is not shown within the TO: and FROM: address fields of the email. Unfortunately, "spammers" use a variety of techniques to mask an email's actual point of origin, such as by forging information to make it appear as though the email originated from a domain that is well recognized across the Internet. Accordingly, the information in the header is very helpful in assisting us in our investigation. We regret any inconvenience this may have caused and appreciate you bringing this matter to our attention. Regards, The Email Abuse Department | |
| Discussion Thread | |
| Customer ( php) | 06/12/2006 10:56 AM |
| Thank you Peter for your reply. I had no config.cache file and --with-imap-ssl option is the same as --with-imap-ssl=yes. To solve this problem (but I still don't know the origin of it) I gave up with the libc-client Suse package. I used the last source of libc-client (2004g) compile this in a specific directory to avoid conflict and then compile and linked PHP5.1.4 with this brand new libc-client. Every thing is ok now. I hope this can help despite the lake of real explanation. Xavier "Peter Hodge" <[EMAIL PROTECTED]> a crit dans le message de news: [EMAIL PROTECTED] > Hi Xavier, > > I don't know if this will fix your problem, but these two jump out at me: > > 1) According to 'configure --help', the --with-imap-ssl option should not > be > 'yes', it should be the path to the includes (e.g., /usr or /usr/local). > Try > --with-imap-ssl by itself, or --with-imap-ssl=/usr/local, etc. > > 2) The configure command caches the include paths in config.cache, make > sure > you delete this file before you try configure/make clean/make/make install > again. > > regards, > Peter > > > > --- Xavier Boully <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> >> >> I have so far PHP 5.0.5 on a Suse 9.2 and apache 2.2.2 box. >> >> PHP is compiled with imap extension (--with-imap-ssl=yes >> and --with-imap), >> using a libc-client library in version 2004c. >> >> >> >> I tried to update to PHP 5.1.x (in fact 5.1.4 and then 5.1.0). Configure, >> make and make install are ok but the linphp5.so cannot be load with this >> error message: >> >> cannot load /.../.../libphp5.so into server: /usr/lib/libc-client.so: >> undefined symbol: mm_dlog >> >> >> >> Then I tried in the PHP 5.1.4 source to substitute the imap source code >> with >> the one found in the php 5.0.5. The result is the same. I suppose the >> problem >> doesn't come from the source code but from the configure script. >> >> Any idea of what have been changed in the configure script of the PHP >> 5.1.x? >> >> >> >> Thanks to read this >> >> Xavier >> > > > Send instant messages to your online friends http://au.messenger.yahoo.com | |
Title: Re: [PHP-INSTALL] Cannot update to PHP 5.1.x with imap extension
