Hi, one of users enter today SOGO and have mails list as plain green boxes w/o any information.
I found in SOGO logs followinf Entry: “NGImap4ParserException: unsupported fetch key: nil”.
It seems its a bug which had been solved long time ago.
Is there a fix for this?? I have newest SOGO 1.84
English
Empty message list. NGImap4ParserException: unsupported fetch key: nil
Hi,
Please post dovecot-mailcow logs.
Have something to say?
Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!
diekuh Dear Diekuh,
In dovecot logs nothing special:
24.09.2020, 13:27:23 info imap(zozwigor@wigor.org)<29638><nhLoew2wMpmsFgH4>: Logged out in=40 out=1133 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
24.09.2020, 13:27:23 info imap-login: Login: user=zozwigor@wigor.org, method=PLAIN, rip=172.22.1.248, lip=172.22.1.250, mpid=29638
24.09.2020, 13:27:23 info imap(zozwigor@wigor.org)<29635><xhDmew2wLpmsFgH4>: Connection closed: Connection reset by peer (UID fetch running for 0.010 + waiting input for 0.001 secs, 584 B in + 85100+2419 B out, state=wait-input) in=699 out=86819 deleted=0 expunged=0 trashed=0 hdr_count=83 hdr_bytes=311 body_count=0 body_bytes=0
24.09.2020, 13:27:23 info imap-login: Login: user=zozwigor@wigor.org, method=PLAIN, rip=172.22.1.248, lip=172.22.1.250, mpid=29635
24.09.2020, 13:27:23 info imap(zozwigor@wigor.org)<29632><GCfiew2wKJmsFgH4>: Logged out in=99 out=1352 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
24.09.2020, 13:27:23 info imap-login: Login: user=zozwigor@wigor.org, method=PLAIN, rip=172.22.1.248, lip=172.22.1.250, mpid=29632
24.09.2020, 13:27:23 info imap(zozwigor@wigor.org)<29629><nNreew2wIpmsFgH4>: Connection closed: read(size=7448) failed: Connection reset by peer (UID fetch finished 0.013 secs ago) in=744 out=137781 deleted=0 expunged=0 trashed=0 hdr_count=100 hdr_bytes=370 body_count=0 body_bytes=0
24.09.2020, 13:27:22 info imap(zozwigor@wigor.org)<29627><zbTeew2wIJmsFgH4>: Logged out in=355 out=10331 deleted=0 expunged=0 trashed=0 hdr_count=6 hdr_bytes=37 body_count=0 body_bytes=0
24.09.2020, 13:27:22 info imap-login: Login: user=zozwigor@wigor.org, method=PLAIN, rip=172.22.1.248, lip=172.22.1.250, mpid=29629
Sogo Logs with error:
24.09.2020, 13:27:38 notice [1216]: <0×0×55994cbab000[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
24.09.2020, 13:27:38 notice [1247]: <0×0×55994cb14e50[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
24.09.2020, 13:27:23 notice [1216]: <0×0×55994cb3fcd0[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
24.09.2020, 13:27:23 notice [1216]: <0×0×55994cb8e6d0[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
24.09.2020, 13:24:06 notice [1247]: <0×0×55994cca7150[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
24.09.2020, 13:24:04 notice [1247]: <0×0×55994cc18940[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unsupported fetch key: nil
I have exactly the same problem, interestingly only on one mailbox (at least for now)..
Few Users start to complains about this issue so its not unique and so rare.
I found email which cause this. If You put this email is in specific folder - SOGO stop parse correctly email list in that folder and shows clear list of emails. There are more in other email accounts - I’ll try to destille them aswell.
I am attaching .eml as zip
Found another email which cause error in SOGO. In this email I had to remove attachments from it but still placing it on folder block SOGO .
Ah, I also reported it internally a few days back.
Yes, same problem here. I hope they will sort that soon.
I post error screenshot also on Mantis bug report.
- Edited
@petar_kozic @PiotrE
Seems to be fixed in inverse-inc/sopec5c23fd
Can you try to update mailcow and see if it got fixed?
Did anyone expect this to be in the packages within 3 hours after it was pushed to git?
Wait for the renewed packages.
@MAGIC
I updated mailcow, same problem. Not solved.
Packages were updated yesterday evening.
Thank you very much @diekuh
I tested, seems to work well.
- Best Answerset by MAGIC
Fixed in mailcow/mailcow-dockerizedda6f510
then