For anyone searching in the future: The eventual cause turns out to be, as
far as I can tell, something screwy in uw-imap or the base64 decode
function it uses on this old Solaris server. It seems to be something odd
with the number of characters in the hash.
tl;dr I'm going to do my migra
On Wed, 8 Feb 2023, Aki Tuomi wrote:
> Can you try setting imapc_sasl_mechanisms to login, maybe it works better?
And Stephan Bosch wrote:
> Can you make a protocol log (tcp dump of commands sent by client and
> replies sent by server) for one of these sessions? e.g. using ngrep if
> connec
Can you make a protocol log (tcp dump of commands sent by client and replies
sent by server) for one of these sessions? e.g. using ngrep if connections
aren't secured.
On 8-2-2023 05:24, Chris Candreva wrote:
I'm migrating a legacy uw-imap system to Dovecot, on a Rocky (RHEL) 8
server running
Can you try setting imapc_sasl_mechanisms to login, maybe it works better?
Aki
> On 08/02/2023 06:24 EET Chris Candreva wrote:
>
>
> I'm migrating a legacy uw-imap system to Dovecot, on a Rocky (RHEL) 8
> server running Dovecot 2.3.16-3 from their repos. I am using a master user
> to import
I'm migrating a legacy uw-imap system to Dovecot, on a Rocky (RHEL) 8
server running Dovecot 2.3.16-3 from their repos. I am using a master user
to import all users for an imaps connection from the old server to the
new. On a trial run however, it worked for about half the users. Half are
gi
