github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-21 18:53:07 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #1543] Mailer not honoring port config option #6437

New Issue
Closed
opened 2026-04-20 17:02:20 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-20 17:02:20 -05:00
Owner
Copy Link

Originally created by @variasdesign on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1543

Description

Greetings. I've been stumped as to why my Vikunja isn't sending reminders. I've used the testmail from Vikunja's CLI and it insists on sending it to the 25 port. I have it on another port and until recently it has worked flawlessly. Setting the mailer.port option with env variable (which is what I was using) and the config file results in the same behavior:

$ sudo docker exec -it vikunja /app/vikunja/vikunja testmail vikunja@luna.lan
2025/09/24 15:06:36 failed to create modcache index dir: mkdir /.cache: permission denied
time=2025-09-24T15:06:36.384Z level=INFO msg="Using config file: /app/vikunja/config.yml"
time=2025-09-24T15:06:36.384Z level=INFO msg="Sending testmail..."
time=2025-09-24T15:06:36.391Z level=ERROR msg="Error sending test mail: dial failed: dial tcp 192.168.1.22:25: connect: connection refused"

Vikunja Version

Unstable

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @variasdesign on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1543 ### Description Greetings. I've been stumped as to why my Vikunja isn't sending reminders. I've used the testmail from Vikunja's CLI and it insists on sending it to the 25 port. I have it on another port and until recently it has worked flawlessly. Setting the mailer.port option with env variable (which is what I was using) and the config file results in the same behavior: ``` $ sudo docker exec -it vikunja /app/vikunja/vikunja testmail vikunja@luna.lan 2025/09/24 15:06:36 failed to create modcache index dir: mkdir /.cache: permission denied time=2025-09-24T15:06:36.384Z level=INFO msg="Using config file: /app/vikunja/config.yml" time=2025-09-24T15:06:36.384Z level=INFO msg="Sending testmail..." time=2025-09-24T15:06:36.391Z level=ERROR msg="Error sending test mail: dial failed: dial tcp 192.168.1.22:25: connect: connection refused" ``` ### Vikunja Version Unstable ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:02:22 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 24, 2025):

can you share your config?

<!-- gh-comment-id:3329351227 --> @kolaente commented on GitHub (Sep 24, 2025): can you share your config?
GiteaMirror commented 2026-04-20 17:02:23 -05:00
Author
Owner
Copy Link

@variasdesign commented on GitHub (Sep 24, 2025):

Sure, here it goes:

---
services:
  vikunja_db:
    image: lscr.io/linuxserver/mariadb
    container_name: vikunja_db
    environment:
      - PUID=950
      - PGID=950
      - MYSQL_ROOT_PASSWORD=secret
      - TZ=Europe/Madrid
      - MYSQL_DATABASE=VK_variasdesign
      - MYSQL_USER=secret
      - MYSQL_PASSWORD=secret
    volumes:
      - /srv/appdata/vikunja/files/mariadb:/config
    networks:
      - net
    restart: unless-stopped
  vikunja:
    image: vikunja/vikunja:unstable
    container_name: vikunja
    user: 950:950
    environment:
#      VIKUNJA_LOG_LEVEL: DEBUG
      VIKUNJA_SERVICE_PUBLICURL: https://vikunja.io.lan/
      VIKUNJA_DATABASE_HOST: vikunja_db
      VIKUNJA_DATABASE_PASSWORD: secret
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: secret
      VIKUNJA_DATABASE_DATABASE: secret
      VIKUNJA_SERVICE_ENABLEREGISTRATION: 0
      VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: 1
      VIKUNJA_MAILER_ENABLED: 1
      VIKUNJA_MAILER_SKIPTLSVERIFY: 1
#      VIKUNJA_MAILER_FORCESSL: 1
      VIKUNJA_MAILER_AUTHTYPE: plain
      VIKUNJA_MAILER_FROMEMAIL: vikunja@io.lan
      VIKUNJA_MAILER_HOST: luna.lan
      VIKUNJA_MAILER_PORT: 2552
      VIKUNJA_SERVICE_JWTSECRET: secret
    volumes:
      - /srv/appdata/vikunja/files:/app/vikunja/files
#      - /srv/appdata/vikunja/config.yml:/app/vikunja/config.yml
      - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt
    depends_on:
      - vikunja_db
    networks:
      - net
      - https-proxy_vikunja
    restart: unless-stopped
networks:
  net:
  https-proxy_vikunja:
    external: true

All options are defined by env variables, I didn't use a config file until now, testing this issue. Thanks.

<!-- gh-comment-id:3329418362 --> @variasdesign commented on GitHub (Sep 24, 2025): Sure, here it goes: ``` --- services: vikunja_db: image: lscr.io/linuxserver/mariadb container_name: vikunja_db environment: - PUID=950 - PGID=950 - MYSQL_ROOT_PASSWORD=secret - TZ=Europe/Madrid - MYSQL_DATABASE=VK_variasdesign - MYSQL_USER=secret - MYSQL_PASSWORD=secret volumes: - /srv/appdata/vikunja/files/mariadb:/config networks: - net restart: unless-stopped vikunja: image: vikunja/vikunja:unstable container_name: vikunja user: 950:950 environment: # VIKUNJA_LOG_LEVEL: DEBUG VIKUNJA_SERVICE_PUBLICURL: https://vikunja.io.lan/ VIKUNJA_DATABASE_HOST: vikunja_db VIKUNJA_DATABASE_PASSWORD: secret VIKUNJA_DATABASE_TYPE: mysql VIKUNJA_DATABASE_USER: secret VIKUNJA_DATABASE_DATABASE: secret VIKUNJA_SERVICE_ENABLEREGISTRATION: 0 VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: 1 VIKUNJA_MAILER_ENABLED: 1 VIKUNJA_MAILER_SKIPTLSVERIFY: 1 # VIKUNJA_MAILER_FORCESSL: 1 VIKUNJA_MAILER_AUTHTYPE: plain VIKUNJA_MAILER_FROMEMAIL: vikunja@io.lan VIKUNJA_MAILER_HOST: luna.lan VIKUNJA_MAILER_PORT: 2552 VIKUNJA_SERVICE_JWTSECRET: secret volumes: - /srv/appdata/vikunja/files:/app/vikunja/files # - /srv/appdata/vikunja/config.yml:/app/vikunja/config.yml - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt depends_on: - vikunja_db networks: - net - https-proxy_vikunja restart: unless-stopped networks: net: https-proxy_vikunja: external: true ``` All options are defined by env variables, I didn't use a config file until now, testing this issue. Thanks.
GiteaMirror commented 2026-04-20 17:02:24 -05:00
Author
Owner
Copy Link

@variasdesign commented on GitHub (Sep 24, 2025):

Here is the test config file:

mailer:
  enabled: true
  host: luna.lan
  port: 2552
  authtype: plain
  fromemail: vikunja@io.lan
<!-- gh-comment-id:3329447765 --> @variasdesign commented on GitHub (Sep 24, 2025): Here is the test config file: ``` mailer: enabled: true host: luna.lan port: 2552 authtype: plain fromemail: vikunja@io.lan ```
GiteaMirror commented 2026-04-20 17:02:24 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 24, 2025):

and you have the same issue with a config file?

<!-- gh-comment-id:3329483033 --> @kolaente commented on GitHub (Sep 24, 2025): and you have the same issue with a config file?
GiteaMirror commented 2026-04-20 17:02:25 -05:00
Author
Owner
Copy Link

@variasdesign commented on GitHub (Sep 24, 2025):

Yes, same issue. I haven't used a config file until now. I tried to obtain the example config from docs but it seems dl.vikunja.io is down or something.

<!-- gh-comment-id:3329503491 --> @variasdesign commented on GitHub (Sep 24, 2025): Yes, same issue. I haven't used a config file until now. I tried to obtain the example config from docs but it seems dl.vikunja.io is down or something.
GiteaMirror commented 2026-04-20 17:02:26 -05:00
Author
Owner
Copy Link

@variasdesign commented on GitHub (Sep 24, 2025):

My apologies, it seemed it was a misconfiguration on my ntfy SMTP server. However, my confusion stemmed from the testmail saying that it was trying to send the email to the 25 port. It seems that it honors the port, but when unable to send the mail, it logs the error as the 25 port. Thanks for your assistance.

<!-- gh-comment-id:3329778836 --> @variasdesign commented on GitHub (Sep 24, 2025): My apologies, it seemed it was a misconfiguration on my ntfy SMTP server. However, my confusion stemmed from the testmail saying that it was trying to send the email to the 25 port. It seems that it honors the port, but when unable to send the mail, it logs the error as the 25 port. Thanks for your assistance.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6437
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?