Hey Matthieau Well, it took me a bit, but here's how I found out somethings went wrong:
I just cloned the mentioned branch, build it, set up the confings as I always do (only disable pop3, replace localhost with my domain and set database parameters), started it up, added a test-user via james-cli.sh and tried to drop a test-mail via telnet. I expected the usual behaviour that when connecting via IMAP I should see the mail I dropped via telnet in the inbox. Well, but I didn't. The logs only shown the usual message "mail <id> spooled for <address>" - but there was no mail in the inbox. So I dug through the database - nothing. Then I looked through the directories and found the dropped mail stuck in the <james-root>/var/store/activemq/blob-transfer/<some index number>/ sub-folder. No matter how often I re-started james, the stuck message didn't got spooled into the inbox. Also by dropping more incoming mails they built up in the mentioned directory but never got further to the user inbox. The logs didn't provide any help as they only show in the smtp log that the dropped message got received but no exception nor stacktrace.
I then cloned the mentioned older branch - did all the same - and it worked as expected. So I can only tell: There seems something worng in the master branch from April 3rd wich doesn't produce log output about the failure. Maybe it's a locked up thread so the queued mails didn't even got processed, maybe this thread is never created or started. Sorry I can't provide any more information.
Matt Am 19.04.2019 um 09:59 schrieb Matthieu Baechler:
Hi, Could you tell me a bit more about how you see that it fails ? Cheers,
--------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
