[Mailsec] Re: SMTP headers in DATA block?
"Murray S. Kucherawy" <superuser@gmail.com> Tue, 10 June 2025 10:24 UTC
Return-Path: <superuser@gmail.com>
X-Original-To: mailsec@mail2.ietf.org
Delivered-To: mailsec@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A449D331B65D for <mailsec@mail2.ietf.org>; Tue, 10 Jun 2025 03:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQS1p-3nCELU for <mailsec@mail2.ietf.org>; Tue, 10 Jun 2025 03:24:24 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2C684331B652 for <mailsec@ietf.org>; Tue, 10 Jun 2025 03:24:24 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-5fff52493e0so6728422a12.3 for <mailsec@ietf.org>; Tue, 10 Jun 2025 03:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749551063; x=1750155863; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7U+6irZw+7qm2ohp7w2BPxE0wAsk9YWXtwsTh466R2A=; b=cYzrQZ6x4pX+YXEFU75FqflnkVneNbyDhgeIAFFK1g9NKjkUzQvxP0tOOEfxfkSdjQ 49L/rrNqvo6jahbFdqftgyGBQXSXxmKwmvcOodgaPE4s7A0Cs6/tgZgbGwjM8ewpb3Xa NziP5v7D47G6n4qSAK43fHF7ZAe8pXyrKdYV6yVuMVMGhV3q6jcD2TR/MEbbj9EJBDDU swDM+0oLg8aP1FZYITmSzOdUe8rR/QrEebiRRmw4Paj8f2JLzRvn5lH0Z09x2nP9Wash /UZXZSSCL187X4UNKXO91qDQrDAc21fKElq52YBo4daqNbzh+GHSdvnEWOGupQPP56+k 1CEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749551063; x=1750155863; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7U+6irZw+7qm2ohp7w2BPxE0wAsk9YWXtwsTh466R2A=; b=bg0fSUHwW2D3M9nXHDjijtrbuK/cP9axvuKTD/BSfCpQBgtzFZtGscm08lkIom8uww 8KovwtUne1tIM8mO83FTUerffBNT+A75KQnaFq3lOyZS6AHoFz4UpXmx9B0M6WRRSvWv uVcEo2asYvtLXXqUWmcci1hayoGnwm2yUu+uImSnODWuQXYmMqfc7qfUqoZC9muhsmnT J6UkX+RzIIjTDSaLxXeQoXaiTDbwntAM6MEFJ/Gtdf+VxdKcNEmz/qwcbmgldBvLYdd+ ovjfEIs0lIQ3Xebsi6xSBKVnuXf37bErCglfHKDNZ2L2FVGhJINZDn/1xp/s5+Yip0F8 8OfA==
X-Gm-Message-State: AOJu0YySp5n3jKCz1lYhZVLpeRAI/ByE8dAuQWuY6/BLWh5Qdg7dCE0s vid4Za9BfDuYNo7gYiDrr9W81jl+NPTd08mD2acMpcNdMSIA1OmRVHcc3L4bE8QyJsK3L8XYp8r 7fCFDMaSI2uoPXZ6HFg5mNjGjN4etFGcX5wxqKstyhg==
X-Gm-Gg: ASbGnctK42oiExPBIaTTT4Jxr5ntKfEltLw1wknV8Obw6TPLd9qtS6Zb7Bhs+OfI2QY M4psmknJ+H095FH2t8LjJhJ2lcgkOCRsJe9Jw19cG7jHFmxrFrnFauL9QrVassL0J+RWMH3zRs7 ClU9mWipEWWJbIkIrk0oXXzWdCZQlmnw9tGtuSKuB/vIjgvhO+5YBWpLxfSsM=
X-Google-Smtp-Source: AGHT+IEbWJ7IR7L9qjwmrmxdnmDBLvP0L8tD/dJgl5YZCqFe9hgF2ZVNv1ycPDGmW+dUKW3GrR7vSlFQkyr7lfxmys8=
X-Received: by 2002:a17:907:7b85:b0:add:fa4e:8a7e with SMTP id a640c23a62f3a-ade7acdf295mr194922766b.32.1749551062826; Tue, 10 Jun 2025 03:24:22 -0700 (PDT)
MIME-Version: 1.0
References: <5223991.nocEyzAEji@workstation.vm.ideapad.lan> <3253776.Jjng342dlF@workstation.vm.ideapad.lan>
In-Reply-To: <3253776.Jjng342dlF@workstation.vm.ideapad.lan>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 10 Jun 2025 11:24:10 +0100
X-Gm-Features: AX0GCFuF2fN4RETxNkHurfJpJmTUoAvcUzqAvIEWIJNrXDCLUzu-Z1eK_rgMfxQ
Message-ID: <CAL0qLwbBJex82nLwT482eg8V7kjeG=XQT0Z7S5jOWj2ZN2VvXw@mail.gmail.com>
To: Michael De Roover <ietf@nixmagic.com>
Content-Type: multipart/alternative; boundary="0000000000009dd3f506373519b8"
Message-ID-Hash: BPI4SJ565IWROUKVABO5VO6FIHIR3BNN
X-Message-ID-Hash: BPI4SJ565IWROUKVABO5VO6FIHIR3BNN
X-MailFrom: superuser@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mailsec@ietf.org, "Hollenbeck, Scott" <shollenbeck@verisign.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Mailsec] Re: SMTP headers in DATA block?
List-Id: Email Security Issues <mailsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mailsec/8WaQazoYj531n0ceLrRhR-6TFKY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mailsec>
List-Help: <mailto:mailsec-request@ietf.org?subject=help>
List-Owner: <mailto:mailsec-owner@ietf.org>
List-Post: <mailto:mailsec@ietf.org>
List-Subscribe: <mailto:mailsec-join@ietf.org>
List-Unsubscribe: <mailto:mailsec-leave@ietf.org>
On Fri, Jun 6, 2025 at 6:27 PM Michael De Roover <ietf@nixmagic.com> wrote: > > I wonder if it would be appropriate to discuss this here? > > So far, I've identified the following mailing lists as potential > candidates: > > - imapext@ietf.org > > - ietf-smtp@ietf.org > > - ietf-dkim@ietf.org > > - dmarc@ietf.org > > - spfbis@ietf.org > > These were all identified using https://mailman3.ietf.org/mailman3/lists. > But I really don't know where this would be most suitable. My guess would > still be mailsec, on account of this discussing security aspects of the > email protocol suite. But certain aspects of it may be better suited here > or there, not sure. Please let me know. > > I would like to include Scott Hollenbeck in CC, on account of the > cautionary message having been copied from a conversation between us on > DNSOP earlier today. Thank you, it was inspirational! > I suggest: https://mailman3.ietf.org/mailman3/lists/ietf-822.ietf.org/ IMHO, none of the lists you proposed above are appropriate for this proposal. -MSK
- [Mailsec] SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? John Levine
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Lyndon Nerenberg (VE7TFX/VE6BBM)
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? John R. Levine
- [Mailsec] Re: SMTP headers in DATA block? Steffen Nurpmeso
- [Mailsec] Re: SMTP headers in DATA block? Steffen Nurpmeso
- [Mailsec] Re: SMTP headers in DATA block? Steffen Nurpmeso
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? John R Levine
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael Peddemors
- [Mailsec] Re: SMTP headers in DATA block? Murray S. Kucherawy
- [Mailsec] Re: SMTP headers in DATA block? Mike Hillyer
- [Mailsec] Re: SMTP headers in DATA block? Murray S. Kucherawy
- [Mailsec] Re: SMTP headers in DATA block? John R Levine
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover
- [Mailsec] Re: SMTP headers in DATA block? Michael De Roover