From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id C21EA1FF136 for ; Mon, 09 Mar 2026 16:12:41 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7FF1337918; Mon, 9 Mar 2026 16:12:34 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH proxmox v3] sendmail: conform more to mime Content-Disposition header and wrap lines Date: Mon, 9 Mar 2026 16:12:23 +0100 Message-ID: <177306914148.1893639.11752608256412530021.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260225112107.99905-1-s.sterz@proxmox.com> References: <20260225112107.99905-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773069117956 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.014 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: V5RXJSQOQAFWDQXEPSJU4EBBKGVJJI5K X-Message-ID-Hash: V5RXJSQOQAFWDQXEPSJU4EBBKGVJJI5K X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 25 Feb 2026 12:21:06 +0100, Shannon Sterz wrote: > the http and mime Content-Disposition headers function slightly > differently. for the http version the following would be valid > according to rfc 6266 [1]: > > Content-Disposition: attachment; filename="file.pdf"; > filename*=UTF-8''file.pdf > > [...] Applied, thanks! [1/1] sendmail: conform more to mime Content-Disposition header and wrap lines commit: 1ab5baa14e198306f9b7e5f055997a8ce7d5f0df Best regards, -- Fabian Grünbichler