Vanilla pine-4.63 (and pine as patched by gentoo curently) only handles ldap v2. This is a patch that applies to pine-4.63-r3.ebuild extending it with an ldapv3 use flag and the code that applies a patch to pine source code in order to enable LDAPv3 handling. I will also attach the patch that modifies the crucial line in pine4.632 sources. This patch produces a working ebuild for me that installs pine which works for me on x86 with openLDAP. AFAIK ldapv3 supports unicode, and pine4.63 does not quie support unicode and this is the reason, why ldapv3 is not on by default in vanilla pine. Everything should work fine thoug as long as extended characters are not used. I am not an expierenced ebuild submitter, so bear with me, do not be too harsh, and say what else do you need, or why you don't like it,... but nicely ;)
Created attachment 66015 [details, diff] ebuild extension to support ldapv3 patch
Created attachment 66016 [details, diff] a patch enabling ldap-v3 in pine4.63
I think the support is disabled exactly because of missing unicode support in Pine, and for good reason. It is not safe to assume users are not going to encounter multibyte characters, thus it would be a very bad idea to have it enabled in Gentoo ebuild, even if only optionally, controlled by an USE flag. I will however ask Mr Eduardo Chappa, who is directly involved in Pine, for an opinion.
(In reply to comment #3) Actually I have googled out some opinions on mailing lists that the only harm that can happen is that you see gibberish instead of extended characters. And that often happens anyway, if you get unicode mail in pine. Having said that, I admit that I am not at all a pine developer, and have no clue about its internals, It is always wise to ask someone more knowledgeable. I find it useful to be able to share addressbooks with thunderbird, etc., but of course if this is introducing some criminal bugs, I am not willing to use it (nor propose others to use it).
As pine-4.64 has experimental LDAPv3 support, I'm closing this bug.
