@girish said in Due date email notifications: @MarchinBunny This feature should work out of the box if Wekan supports it. Does it not work? What is the setting that you mention in docker-compose.yml? Cloudron does not use docker compose, we have our own packaging. Nope, I don't think it works out of the box from what I can tell. I certainly have never received an email for due dates. If you scroll through the file I mentioned, there is a section called "==== EMAIL DUE DATE NOTIFICATION =====" Below that you will see the settings are commented out with hashtags. Here is a copy and paste of the specific section I am talking about. # ==== EMAIL DUE DATE NOTIFICATION ===== # https://github.com/wekan/wekan/pull/2536 # System timelines will be showing any user modification for # dueat startat endat receivedat, also notification to # the watchers and if any card is due, about due or past due. # # Notify due days, default is None, 2 days before and on the event day #- NOTIFY_DUE_DAYS_BEFORE_AND_AFTER=2,0 # # Notify due at hour of day. Default every morning at 8am. Can be 0-23. # If env variable has parsing error, use default. Notification sent to watchers. #- NOTIFY_DUE_AT_HOUR_OF_DAY=8

@jdaviescoates Thanks! Fixed - https://git.cloudron.io/cloudron/box/-/commit/122ec75cb667197a550e8488c94062524b0713db

#heretoo #thanksforthefix

@JOduMonT Currently, the 'email is not configured properly' notification is updated every 30 minutes. So, it's very much possible that those email settings are fine now and that notification will go away after 30 minutes. If you click on the notification, it should expand to give information on what exactly is not setup properly. Can you tell me what you see if you click the notification ? Also, zen.spamhaus.org being disabled is not good! Do you have a custom DNS setup by any chance? Under system -> services, is unbound running OK?

@girish As far as I know, it's correct - unless DKIM has the IP included, since that did change during the migration. Unfortunately, the Email section of Cloudron wasn't properly giving the needed information - previously it was saying DKIM was incorrect, but the display just said something like "expected null to equal null". DKIM isn't showing in the Email status page at all with the workaround I added here. I'll put that in as a separate issue, though, once the update comes out and I see the proper message.

I have created https://git.cloudron.io/cloudron/box/issues/649

Until there are better or more fine granular ones, there is always the option to create email filters in your email account to get a better overview, while still being informed.

Fixed it for next release.