Imap mailbox not work with new groupware grommunio-imap / rubby 2.7 problem?

Used Zammad version: 5.1.1
Used Zammad installation type: (source, package, docker-compose, …)
package over ubuntu 20.04 LTS
Operating system: ubuntu 20.04 LTS
*Browser + version: alle actual browser, chrom, edge, firefox

Expected behavior:
on inserting e-mail box imap or pop in zammad!

Actual behavior:

when i will change my mail server in e-mail settings to the new grommunio server. it doesnt work.
the problem, when i will save the imap settings i get an error:


Unexpected token LPAR (expected QUOTED or LITERAL)

on testing und searching i will see there is an rubby 2.7 probleme, that have a bugfix. but i cannot update rubby to version 3.x
happend only on new grommunio-imap mail server. old server and other work.

i have make an ticket on grommunio, that also use zammad as ticketsystem, but the have not the problem.
i have make a ticket nand community entry there. but no solution.

we only find this:

next i have test an change settings in imap.rb but nothing helped.

the log in mailserver only show this:

Jun 09 07:19:34 m1 imap[1420]: < LOGIN ****: ret=6a9h code=1705
Jun 09 07:19:34 m1 imap[1420]: < RUBY0002 SELECT INBOX: ret=0h code=0
Jun 09 07:19:34 m1 imap[1420]: < RUBY0003 SORT (DATE) US-ASCII ALL: ret=0h code=0
Jun 09 07:19:34 m1 imap[1420]: < RUBY0004 SEARCH ALL: ret=2000000h code=0
Jun 09 07:19:34 m1 imap[1420]: < RUBY0005 FETCH 1 (RFC822.HEADER: ret=2000000h code=0

so i need support here…
ist the problem on mailserver or on zammads used version ruby?
or ist the problem on ruby package at the grommunio server.

zammad ruby:
Ubuntu 20.04
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]

grommunio ruby:
Suse grommunio appliance
ruby 2.5.9p229 (2021-04-05 revision 67939) [x86_64-linux-gnu]

Steps to reproduce the behavior:
reproducing this isue only be possible when you use grommunio-imap.
grommunio says that the use zammad to but i should check the side of zammad, there are work with compatibility rfc headers.

grommunio hase fix this bug in RFC822 headers!

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.