Ticket #266 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 months ago

[PATCH] PEAR::Net_IMAP needs patching for use with PHP 5

Reported by: rjl Owned by: rjl
Priority: normal Milestone: 1.0.3
Component: PHP scripts Version: 1.0.0
Severity: normal Keywords: php 5 imap net_imap pear
Cc:

Description

While this isn't a Maia bug, it affects Maia users wishing to use PHP 5 and IMAP authentication. The bug and its solution are described here.

While this is likely to be fixed in future versions of PEAR::Net_IMAP, it plagues the current version (1.0.3), so a one-line patch for the IMAPProtocol.php file is all that's required to get it working with PHP 5. We should provide that patch with Maia until such time as a new release of PEAR::Net_IMAP is issued.

Furthermore, we can detect this condition within configtest.php--the combination of PHP version >= 5 and PEAR::Net_IMAP version == 1.0.3--and warn users to apply the supplied patch.

Attachments

IMAPProtocol.php.patch (404 bytes) - added by rjl 3 years ago.
Patch file for IMAPProtocol.php from PEAR::Net_IMAP 1.0.3

Change History

Changed 3 years ago by rjl

Patch file for IMAPProtocol.php from PEAR::Net_IMAP 1.0.3

Changed 3 years ago by dmorton

  • status changed from new to closed
  • resolution set to fixed

[952], [953] Pointing users to this page to get patch.

Changed 2 years ago by rjl

  • summary changed from PEAR::Net_IMAP needs patching for use with PHP 5 to [PATCH] PEAR::Net_IMAP needs patching for use with PHP 5

Changed 2 years ago by dmorton

  • patch set to 0

I also get an error when logging in, undefined variable $command on line 2707. By changing this to $token, the error goes away.

This can be a show stopper if debugging is turned on, as it causes a popup window and stops the redirect on xlogin.php.

Changed 7 months ago by dmorton

  • status changed from closed to reopened
  • resolution fixed deleted
  • milestone changed from 1.0.1 to 1.0.3

That last comment doesn't make sense?

Anyway, reopening this ticket because the url for the fix is wrong in the patches... it needs to go to www.maiamailguard.com now.

Changed 2 months ago by rjl

  • status changed from reopened to closed
  • resolution set to fixed

URLs corrected in [1236].

Note: See TracTickets for help on using tickets.