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

[GH-ISSUE #2522] SMTP issues #6692

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

Originally created by @2manyvcos on GitHub (Apr 2, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2522

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Mails sent from my Vikunja instance are regularly rejected by the receiver Email server (in my case mx01.mail.icloud.com) with the following error:

Message rejected due to local policy. Please visit https://support.apple.com/en-us/HT204137

If I understand it correctly, this error is returned when Apple categorizes an email as Spam, so I looked at the messages in detail to find out what might be the cause for this.

One thing that I was able to find when comparing an email sent by Vikunja to others is, that the Message-ID header differs:

Others: Message-ID: <Some-Random-ID@some.domain>
Vikunja: Message-ID: <Some-Random-ID>

In the support URL provided by Apple in the error message (https://support.apple.com/en-us/HT204137), it is mentioned that emails should conform to the RFCs 5321 and 5322.
In RFC 5322, Section 3.6.4 (https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.4), the msg-id is specified like follows:

msg-id          =   [CFWS] "<" id-left "@" id-right ">" [CFWS]

So my guess is that the emails are being rejected because the Sender domain is missing in the Message-ID header. (In other messages this is set to the domain that is also used in the From email address, so e.g. for From: Vikunja <demo@example.com> the message ID should look like Message-ID: <002dc1a0-3a7f-4344-95bc-2748dde7c725@example.com>)

Also, not directly related to this issue but could you please allow to specify a custom From name, I would like to have something like From: My Notes <demo@example.com>, in other self hosted solutions you usually just set the whole value for the From header, not just the email.

Thanks a lot for your great work!

[EDIT]:

I just looked at some more emails from Vikunja and it seems like sometimes the hostname is sent in the message ID, sometimes not. In both cases, I think it doesn't match what over clients do, but this at least explains why some messages are delivered and others are not. (All emails were sent using vikunja testmail <myemail>)

Vikunja Version

2.2.2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @2manyvcos on GitHub (Apr 2, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2522 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Mails sent from my Vikunja instance are regularly rejected by the receiver Email server (in my case mx01.mail.icloud.com) with the following error: ``` Message rejected due to local policy. Please visit https://support.apple.com/en-us/HT204137 ``` If I understand it correctly, this error is returned when Apple categorizes an email as Spam, so I looked at the messages in detail to find out what might be the cause for this. One thing that I was able to find when comparing an email sent by Vikunja to others is, that the `Message-ID` header differs: Others: `Message-ID: <Some-Random-ID@some.domain>` Vikunja: `Message-ID: <Some-Random-ID>` In the support URL provided by Apple in the error message (https://support.apple.com/en-us/HT204137), it is mentioned that emails should conform to the RFCs 5321 and 5322. In RFC 5322, Section 3.6.4 (https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.4), the msg-id is specified like follows: ``` msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] ``` So my guess is that the emails are being rejected because the Sender domain is missing in the `Message-ID` header. (In other messages this is set to the domain that is also used in the `From` email address, so e.g. for `From: Vikunja <demo@example.com>` the message ID should look like `Message-ID: <002dc1a0-3a7f-4344-95bc-2748dde7c725@example.com>`) Also, not directly related to this issue but could you please allow to specify a custom From name, I would like to have something like `From: My Notes <demo@example.com>`, in other self hosted solutions you usually just set the whole value for the From header, not just the email. Thanks a lot for your great work! > [EDIT]: > > I just looked at some more emails from Vikunja and it seems like sometimes the hostname is sent in the message ID, sometimes not. In both cases, I think it doesn't match what over clients do, but this at least explains why some messages are delivered and others are not. (All emails were sent using `vikunja testmail <myemail>`) ### Vikunja Version 2.2.2 ### 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:16:37 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 3, 2026):

This might get fixed by https://github.com/go-vikunja/vikunja/pull/2536

<!-- gh-comment-id:4184589093 --> @kolaente commented on GitHub (Apr 3, 2026): This might get fixed by https://github.com/go-vikunja/vikunja/pull/2536
GiteaMirror commented 2026-04-20 17:16:37 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 3, 2026):

This issue has been fixed in #2536, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4184700596 --> @vikunja-bot-app[bot] commented on GitHub (Apr 3, 2026): This issue has been fixed in #2536, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 17:16:38 -05:00
Author
Owner
Copy Link

@2manyvcos commented on GitHub (Apr 7, 2026):

I tested the current unstable version and all emails were delivered. Thank you!

<!-- gh-comment-id:4196955794 --> @2manyvcos commented on GitHub (Apr 7, 2026): I tested the current unstable version and all emails were delivered. Thank you!
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#6692
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?