E-Mail Notification twice

wusa88 · 20 2024 13:53

Hello,

I have a small problem.
Every comment that is created is sent twice by e-mail.

Here is an example:

version: '3'

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_JWTSECRET: password
      VIKUNJA_SERVICE_PUBLICURL: http://home.local/
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
      VIKUNJA_SERVICE_ENABLETASKATTACHMENTS: 1
      VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: 1
      VIKUNJA_MAILER_ENABLED: 1
      VIKUNJA_MAILER_AUTHTYPE: login
      VIKUNJA_MAILER_SKIPTLSVERIFY: 1
      VIKUNJA_MAILER_HOST: mail.home.local
      VIKUNJA_MAILER_PORT: 25
      VIKUNJA_MAILER_USERNAME: user
      VIKUNJA_MAILER_PASSWORD: password

    ports:
     - 3456:3456
    volumes:
     - /home/ubuntu/docker/vikunja/files:/app/vikunja/files
     - /home/ubuntu/docker/vikunja/db:/db
    restart: unless-stopped

Is this just a setting or is it a bug?

However, I would like to thank you very much for the project!

wusa88 · 20 2024 13:54

Here the comment inside vikunja. I’m not allowed to add 2 pictures in one post.
grafik

Thank you

Wasabi · 21 2024 09:39

How do you even get these mails in the first place? I’ve been searching for an option to get those, but our Vikunja is only sending reminders if the task is overdue

wusa88 · 21 2024 10:40

I have subscribed to the project.

But i only get mails from my teammate.

wusa88 · 21 2024 12:28

Mail Debug log.

|2024-08-21T12:11:14.540697639Z: DEBUG|▶ [MAIL] 123 250 2.0.0 OK|
|---|---|
|2024-08-21T12:11:14.540790176Z: DEBUG|▶ [MAIL] 124 AUTH LOGIN|
|2024-08-21T12:11:14.54143637Z: DEBUG|▶ [MAIL] 125 334 VXMlcm5hbWU6|
|2024-08-21T12:11:14.541486052Z: DEBUG|▶ [MAIL] 126 YmFja2VwYWRt|
|2024-08-21T12:11:14.541988968Z: DEBUG|▶ [MAIL] 127 334 UGJzc3dvcmQ6|
|2024-08-21T12:11:14.542033301Z: DEBUG|▶ [MAIL] 128 YXdjNLIwMUM3|
|2024-08-21T12:11:14.605644044Z: DEBUG|▶ [MAIL] 129 235 2.7.0 Authentication successful|
|2024-08-21T12:11:14.605718375Z: DEBUG|▶ [MAIL] 12a NOOP|
|2024-08-21T12:11:14.606310249Z: DEBUG|▶ [MAIL] 12b 250 2.0.0 OK|
|2024-08-21T12:11:14.606363769Z: DEBUG|▶ [MAIL] 12c MAIL FROM:<mail@vikunja> BODY=8BITMIME|
|2024-08-21T12:11:14.607226961Z: DEBUG|▶ [MAIL] 12d 250 2.1.0 Sender OK|
|2024-08-21T12:11:14.607272073Z: DEBUG|▶ [MAIL] 12e RCPT TO:<thomas@domain.local>|
|2024-08-21T12:11:14.607993488Z: DEBUG|▶ [MAIL] 12f 250 2.1.5 Recipient OK|
|2024-08-21T12:11:14.60803436Z: DEBUG|▶ [MAIL] 130 DATA|
|2024-08-21T12:11:14.608614039Z: DEBUG|▶ [MAIL] 131 354 Start mail input; end with <CRLF>.<CRLF>|
|2024-08-21T12:11:14.715150965Z: DEBUG|▶ [MAIL] 132 NOOP|
|2024-08-21T12:11:14.71587348Z: DEBUG|▶ [MAIL] 133 250 2.0.0 OK|
|2024-08-21T12:11:14.715921769Z: DEBUG|▶ [MAIL] 134 RSET|
|2024-08-21T12:11:14.716585313Z: DEBUG|▶ [MAIL] 135 250 2.0.0 Resetting|
|2024-08-21T12:11:14.716626326Z: DEBUG|▶ [MAIL] 136 NOOP|
|2024-08-21T12:11:14.717168847Z: DEBUG|▶ [MAIL] 137 250 2.0.0 OK|
|2024-08-21T12:11:14.717250672Z: DEBUG|▶ [MAIL] 138 NOOP|
|2024-08-21T12:11:14.718114748Z: DEBUG|▶ [MAIL] 139 250 2.0.0 OK|
|2024-08-21T12:11:14.718170404Z: DEBUG|▶ [MAIL] 13a MAIL FROM:<mail@vikunja> BODY=8BITMIME|
|2024-08-21T12:11:14.719128308Z: DEBUG|▶ [MAIL] 13b 250 2.1.0 Sender OK|
|2024-08-21T12:11:14.719185525Z: DEBUG|▶ [MAIL] 13c RCPT TO:<thomas@domain.local>|
|2024-08-21T12:11:14.72008003Z: DEBUG|▶ [MAIL] 13d 250 2.1.5 Recipient OK|
|2024-08-21T12:11:14.720134123Z: DEBUG|▶ [MAIL] 13e DATA|
|2024-08-21T12:11:14.720841227Z: DEBUG|▶ [MAIL] 13f 354 Start mail input; end with <CRLF>.<CRLF>|
|2024-08-21T12:11:14.826050721Z: DEBUG|▶ [MAIL] 140 NOOP|
|2024-08-21T12:11:14.82676359Z: DEBUG|▶ [MAIL] 141 250 2.0.0 OK|
|2024-08-21T12:11:14.826810947Z: DEBUG|▶ [MAIL] 142 RSET|
|2024-08-21T12:11:14.82739771Z: DEBUG|▶ [MAIL] 143 250 2.0.0 Resetting|
|2024-08-21T12:11:14.827438089Z: DEBUG|▶ [MAIL] 144 NOOP|
|2024-08-21T12:11:14.828092016Z: DEBUG|▶ [MAIL] 145 250 2.0.0 OK|

Wasabi · 21 2024 13:11

Learned something new myself now however cannot reproduce it in our environment (v0.24.2), mails are only ent once. Which version are you running exactly?

wusa88 · 21 2024 13:23

I am running Docker Version: v0.24.2

Notifications inside Vikunja are also twice.
grafik

Could you show me your docker compose?

How do you share the projects?
By user or by team?

Wasabi · 21 2024 13:53

Hi, for sure, here you go (however we’re using a config.yml, as OIDC settings are not yet exposed via environment variables):

services:

  vikunja:
    image: vikunja/vikunja:{{vikunja_version}}
    volumes: 
      - vikunja-data:/app/vikunja/files
      - ./config/vikunja/config.yml:/app/vikunja/config.yml:ro
    restart: unless-stopped
    environment:
      - VIKUNJA_SERVICE_PUBLICURL=https://{{vikunja_external_url}}
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.vikunja.rule=Host(`{{ vikunja_external_url }}`)"
      - "traefik.http.routers.vikunja.entrypoints=websecure"
      - "traefik.http.routers.vikunja.tls.certresolver=letsencrypt"
      - "traefik.http.services.vikunja.loadbalancer.server.port=3456"
  
  vikunja-redis:
    image: redis

volumes:
  vikunja-data:

And the config files:

service:
  JWTSecret: "{{vault_vikunja_jwt_secret}}"
  frontendurl: "https://{{vikunja_external_url}}/"
  enableregistration: false
  enabletaskattachments: true
  timezone: Europe/Berlin
  enableuserdeletion: true
  enablepublicteams: true
  enableemailreminders: true

database:
  type: "mysql"
  user: "vikunja"
  password: "{{vault_vikunja_mysql_password}}"
  host: "mysql"
  database: "vikunja"

redis:
  enabled: true
  host: "vikunja-redis:6379"

cors:
  enable: true
  origins:
    - "https://{{vikunja_external_url}}"

mailer:
  enabled: true
  host: "..."
  port: 587
  authtype: "plain"
  username: "no-reply@....de"
  password: "{{vault_noreply_smtp_password}}"
  fromemail: "no-reply@....de"

auth:
  local:
    enabled: disable
  openid:
    enabled: true
    redirecturl: https://{{vikunja_external_url}}/auth/openid/
    providers:
      - name: Makerspace Login
        authurl: {{ keycloak_realm_url }}
        logouturl: {{ keycloak_logout_url }}
        clientid: vikunja
        clientsecret: "{{vault_vikunja_kc_client_secret}}"
        scope: openid email profile vikunja_scope

metrics:
  enabled: true
  username: prometheus
  password: "{{vault_vikunja_prometheus_password}}"

# Provide default settings for new users. When a new user is created, these settings will automatically be set for the user. If you change them in the config file afterwards they will not be changed back for existing users.
defaultsettings:
  week_start: 1
  language: de-DE
  timezone: Europe/Berlin
  discoverable_by_name: true
  discoverable_by_email: true

We’re mostly sharing the projects using teams created from OIDC, and haven’t seen the duplicate notifications yet. The fact that they’re shown twice in the UI probably rules out any mail related configuration though

wusa88 · 22 2024 05:43

I think I have found the issue.

If i subscribe just to one task, the notification is shown once.

If i subscribe to the project, so every task is automatically subscribed, the notification is shown twice.

Maybe you could try this?

Whats best practice to get notifications from every task inside the project?
It’s just me and my teammate. We like to get every comments, that we stayed informed from each other.

Wasabi · 22 2024 06:42

Yes, I can confirm this behaviour - when I’m subscribed both to the project and to the task and someone comments, I’m getting the same notification twice. This seems like a bug to me, although no simple idea how to fix it. I’ve raised a bug report in the issue tracker.

Also can’t come up with a simple workaround unfortunately, as the UI won’t allow you to unsubscribe from an issue if you’re subscribed to the project

wusa88 · 22 2024 06:55

But i think that’s ok.
If i subscribe to the whole project, i like to be informed about the whole project.

But i understand, sometime it makes sense to unsubscribe just a simple task.

But how did you received the notifications till now?
Or you had to look in every task by youself?

kolaente · 24 2024 13:47

Can confirm this as a bug. Will look into a fix.

kolaente · 29 2024 08:35

This is now fixed in efde364224, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

wusa88 · 30 2024 08:50

I think it’s not fixed yet.

I use the unstable build.
grafik

grafik

I am the owner of this project and i shared it with my colleague with admin rights:
grafik

E-Mail and Notifications are twice.

Thank you!

kolaente · 30 2024 09:51

Which Vikunja version are you using?

wusa88 · 2 2024 05:43

vikunja/vikunja:unstable

as you told.

I don’t know which version is here: Vikunja
But it’s possible to reproduce it here as well.

kolaente · 2 2024 13:22

I meant the actual Vikunja version, the one you can see in the about dialouge.

I was unable to reproduce this on try. Can you specify the exact steps you took to reproduce it?

wusa88 · 2 2024 13:56

Do you mean the unstable version? I just used this tag:
vikunja/vikunja:unstable
But i will have a look in the about page. You will receive this later.

But i can reproduce it on try.vikunja.io as well:

I created a new user called: demo2 (Password: Demo2Demo2)
Inbox → Share → User demo → share with admin rights.
Subscribe to the whole project
create a new task (which is automatically subscribed to the user)

grafik1428×560 39.7 KB
now i change to the user demo

grafik1774×792 42.9 KB
open the task, and leave a comment

grafik517×662 24.3 KB
switch back to user demo2
there are 2 notifications
on your test instance with this version:

If you need some other test, on other version, please tell me.

Thank you!

kolaente · 2 2024 21:38

I was able to reproduce this locally and pushed a fix in 2c9becec10. Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

wusa88 · 3 2024 05:52

Same problem as yesterday.
On try, I was able to reproduce the problem again.

grafik

Edit:
I have just noticed that the version is the same as yesterday.
Is this still the same version as yesterday, or is the version number not updated?

grafik