[GH-ISSUE #1206] Missing mandatory header in Email notification #851

Closed
opened 2026-05-07 00:28:11 +02:00 by BreizhHardware · 2 comments

Originally created by @didier13150 on GitHub (Oct 22, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1206

🐞 Describe the bug

Email notifications sent by my private ntfy instance were not accepted by remote smtp server due to missing header Date (https://tools.ietf.org/html/rfc5322#section-3.6).

Here is the amavis scanner (email spam and virus scanner) report

554 5.6.0 bounce, id=3454424-13 - bad header
Missing required header field: "Date"

💻 Components impacted

ntfy server

💡 Screenshots and/or logs
Full email headers

Return-Path: <notify@example.com>
Received: from localhost (unknown [172.30.0.15])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by smtp.example.com (Postfix) with UTF8SMTPSA id 3C4397E1B4E
	for <user@example.com>; Tue, 22 Oct 2024 17:18:54 +0200 (CEST)
From: "notify.example.com/alertes" <notify@example.com>
To: user@example.com
Subject: =?utf-8?b?8J+OiSBCb25qb3VyIE1vbmRl?=
Content-Type: text/plain; charset="utf-8"

🔮 Additional context

Just add the missing header to email notification to make ntfy perfect 😉

Big thanks to the team

Originally created by @didier13150 on GitHub (Oct 22, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1206 :lady_beetle: **Describe the bug** Email notifications sent by my private ntfy instance were not accepted by remote smtp server due to missing header **Date** (https://tools.ietf.org/html/rfc5322#section-3.6). Here is the amavis scanner (email spam and virus scanner) report > 554 5.6.0 bounce, id=3454424-13 - bad header > Missing required header field: "Date" :computer: **Components impacted** ntfy server :bulb: **Screenshots and/or logs** Full email headers ``` Return-Path: <notify@example.com> Received: from localhost (unknown [172.30.0.15]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.example.com (Postfix) with UTF8SMTPSA id 3C4397E1B4E for <user@example.com>; Tue, 22 Oct 2024 17:18:54 +0200 (CEST) From: "notify.example.com/alertes" <notify@example.com> To: user@example.com Subject: =?utf-8?b?8J+OiSBCb25qb3VyIE1vbmRl?= Content-Type: text/plain; charset="utf-8" ``` :crystal_ball: **Additional context** Just add the missing header to email notification to make ntfy perfect :wink: Big thanks to the team
BreizhHardware 2026-05-07 00:28:11 +02:00
  • closed this issue
  • added the
    🪲 bug
    label
Author
Owner

@wunter8 commented on GitHub (Oct 22, 2024):

This has been added to ntfy, but it hasn't been released yet: https://github.com/binwiederhier/ntfy/pull/1141

You can download the current source code and compile ntfy yourself or wait for the next release. (I'm not sure when it will be)

<!-- gh-comment-id:2430014103 --> @wunter8 commented on GitHub (Oct 22, 2024): This has been added to ntfy, but it hasn't been released yet: https://github.com/binwiederhier/ntfy/pull/1141 You can download the current source code and compile ntfy yourself or wait for the next release. (I'm not sure when it will be)
Author
Owner

@didier13150 commented on GitHub (Oct 23, 2024):

Thanks for your reply, I just test the main branch and it works like a charm

<!-- gh-comment-id:2432891071 --> @didier13150 commented on GitHub (Oct 23, 2024): Thanks for your reply, I just test the main branch and it works like a charm
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#851
No description provided.