-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMAP email job not working in 5.1.2+ #553
Comments
Confirmed using default docker-compose.yml with IMAP_ENABLED set to true. Luckily reproducing this doesn't actually require a valid gmail account so its easy to test. Also verified running the app:rake does seem to work. I will dig into this
Not worried about credentials error since that's expected.
|
I pushed a commit to the master branch, could you test it and verify its working now. It looks like its working for me. |
This bug likely effects tags 5.1.1-4, 5.1.1-5, and 5.2.0, since the switch to the ruby:3.2-slim-bookworm image |
Documentation mentions Rake tasks with
|
Thanks for pointing this out, I think it's a lot cleaner to do this instead. As its shorter and will be backwards compatible
|
@jcormier I can confirm the issue is fixed. Many thanks! |
Running the cron job puts the following error in the cron_rake.log:
I can run it manually by executing the command via /sbin/entrypoint.sh eg:
/sbin/entrypoint.sh app:rake redmine:email:receive_imap host=imap.gmail.com port=993 ssl=true username=myusername password=mypassword unknown_user=accept no_permission_check=1 no_account_notice=true project=myproject project_from_subaddress=true
Looks like the environment is not initialised properly for the cron job?
The text was updated successfully, but these errors were encountered: