Hi all,

I am trying to set mail forwarding with sogo-tool:

sogo-tool user-preferences set defaults test2 -p /etc/sogo/sieve.creds Forward -f /tmp/fwd <0x0x5638face3ec0[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
<0x0x5638face3ec0[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
S[0x5638fafb21a0]: "IMPLEMENTATION" "Dovecot"
S[0x5638fafb21a0]: "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vacation-seconds spamtest imapflags notify imapsieve vnd.dovecot.imapsieve"
S[0x5638fafb21a0]: "NOTIFY" "mailto"
S[0x5638fafb21a0]: "SASL" "GSSAPI GSS-SPNEGO PLAIN"
S[0x5638fafb21a0]: "STARTTLS"
S[0x5638fafb21a0]: "VERSION" "1.0"
S[0x5638fafb21a0]: OK "Dovecot ready."
C: AUTHENTICATE "PLAIN" {%d+}
LOGIN:PASSWORD

S[0x5638fafb21a0]: OK "Logged in."
C: LISTSCRIPTS
sogo-tool: Uncaught exception NSInvalidArgumentException, reason: NGImap4Client(instance) does not recognize authenticate:authname:password:

The login seems to succeed (a manual test with telnet confirms that) but then Sogo suddenly crashes.

When I set mail forwarding from the browser it works fine.

I am using Sogo 5.7.0 on Debian Bullseye.

How can I fix this issue?
Or what would be a good approach to debug it?

- Kees

--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to