cclient, panda-cclient, and php71-imap (and others?)

[Adam Bernstein]

Thierry et al. -

Thanks for the reply and for adding to my understanding here. I haven't 
seen any reply from the php71-imap maintainer; have I missed it? It does 
seem like the most immediate solution here would be to change the 
default build option for that port, and perhaps others that use cclient.

Of course getting cclient (and panda-cclient if it's in need too) back 
to fully maintained status would be even better, but that would need 
someone new to step up. I'm willing, but I've started reading up on what 
it would take to be a port maintainer, and concluded it's far beyond me 
at present. :(

    adam

On 4/24/2019 12:43 PM, Thierry Thomas wrote:
> Le lun. 22 avr. 19 à 20:05:07 +0200, Adam Bernstein <adam at electricembers.coop>
>   écrivait :
> 
>> It seems to me that 'mail/cclient' should be marked as broken with
>> current OpenSSL
>> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226621), and possibly
>> as unmaintained, and that all other ports that use it (the one that
>> concerns us currently is 'php71-imap') should switch to using the fork
>> 'panda-cclient' instead. That fork has this bug fixed already, and
>> php71-imap offers panda-cclient as a build option but not as the default.
> 
> Indeed, I've been using Panda for a long time, and it is a safer
> replacement for cclient and uw-imap, and we could set it by default.
> (adding PHP maintainer to Cc:)
> 
>> Or am I missing something? If not, is there anything we can do to
>> facilitate?
> 
> However, note that Panda is not bulletproof, and mostly unmaintained
> too. Someone tries to revive this project and help is wanted: see
> https://github.com/nkhorman/panda-imap/issues
> 
> Regards,
> 

-- 
Electric Embers Cooperative
Handcrafted hosting, powering the fires of change
electricembers.coop
(800) 843-6197 / (415) 992-6916