I am using paperless-ngx to import pdf's from a grommunio imap mailbox. It worked before I migrated from Suse 15.6 to Suse 16.0.
Now paperless-ngx fails to import pdf's with the following error:
[2026-06-05 16:20:00,114] [ERROR] [paperless_mail] Rule DMS mailbox.process inbox: Error while processing rule: Response status "OK" expected, but "NO" received. Data: [b'server internal error, midb: command parameter error']
Traceback (most recent call last):
File "/usr/src/paperless/src/paperless_mail/mail.py", line 574, in handle_mail_account
total_processed_files += self.handle_mail_rule(
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/paperless/src/paperless_mail/mail.py", line 652, in _handle_mail_rule
for message in messages:
^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/imap_tools/mailbox.py", line 194, in fetch
uids = tuple((reversed if reverse else iter)(self.uids(criteria, charset, sort)))[limit_range]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/imap_tools/mailbox.py", line 139, in uids
check_command_status(uid_result, MailboxUidsError)
File "/usr/local/lib/python3.12/site-packages/imap_tools/utils.py", line 48, in check_command_status
raise exception(command_result=command_result, expected=expected)
imap_tools.errors.MailboxUidsError: Response status "OK" expected, but "NO" received. Data: [b'server internal error, midb: command parameter error']
after doing some research with chatgpt I've tested grommunio imap:
a5 UID SEARCH (UNSEEN SINCE 01-Jun-2026)
a5 NO server internal error, midb: command parameter error
and
a5 UID SEARCH SINCE 1-june-2026
a5 NO server internal error, midb: command parameter error
Chatgpt suggestes that:
You now have a very clear, reproducible MIDB limitation/bug:
What works
UID SEARCH ALL ✔
UID SEARCH UNSEEN ✔
UID SEARCH SEEN ✔
What fails
UID SEARCH SINCE 1-june-2026 ❌
UID SEARCH (UNSEEN SINCE 01-Jun-2026) ❌ (already confirmed)
Root cause (now confirmed precisely)
This is not a Paperless problem anymore.
It is a Gromox MIDB date parser issue:
❗ MIDB in your build rejects SINCE date parsing depending on format/locale/keyword parsing path.
The key clue is:
midb: command parameter error
That is not IMAP syntax rejection from the IMAP layer — it is MIDB failing to interpret the date parameter.
Or should I not rely on chatgpt that much ;-)
the gromox-imap, gromox-midb and other services are running without errors...
