Re: [Ietf-dkim] Misuse of antiforgery protocols

2022-12-25 Thread Michael Deutschmann
On Sun, 25 Dec 2022, you wrote: >> It's easy to sort wanted mail between forwards/mailing-lists and normal >> narrow-casted mail. Spam can masquerade as either; but if possible a >> spammer would want to look like narrow-casted mail as that is the only >> kind that could be expected to arrive from

Re: [Ietf-dkim] Rechartering

2022-12-25 Thread Michael Thomas
On 12/25/22 7:55 AM, Murray S. Kucherawy wrote: On Sun, Dec 25, 2022 at 6:31 AM Barry Leiba wrote: I agree with Mike and Scott on the point that it’s worth explicitly allowing the result to be a “can’t do it” publication.  Implicit “couldn’t do it” is fine in most cases, but here

Re: [Ietf-dkim] Rechartering

2022-12-25 Thread Murray S. Kucherawy
On Sun, Dec 25, 2022 at 6:31 AM Barry Leiba wrote: > I agree with Mike and Scott on the point that it’s worth explicitly > allowing the result to be a “can’t do it” publication. Implicit “couldn’t > do it” is fine in most cases, but here we might say something like, “If the > working group decid

Re: [Ietf-dkim] Misuse of antiforgery protocols

2022-12-25 Thread Murray S. Kucherawy
On Sat, Dec 24, 2022 at 9:12 PM Michael Deutschmann wrote: > On Mon, 12 Dec 2022, you wrote: > > > Blind-carbon-copy is already a sign of spam. > > > > Except when it's not, like this very mailing list. > > Only if you don't whitelist *all* forwarders you set up and mailing lists > you have joine

Re: [Ietf-dkim] Rechartering

2022-12-25 Thread Barry Leiba
I agree with Mike and Scott on the point that it’s worth explicitly allowing the result to be a “can’t do it” publication. Implicit “couldn’t do it” is fine in most cases, but here we might say something like, “If the working group decides that none of the proposed approaches will work acceptably