Re: homework, not an experiment, draft-crocker-email-deliveredto
Sam Varshavchik <[email protected]> Tue, 03 Aug 2021 17:20:42 -0400
| Newsgroups | gmane.ietf.smtp |
|---|---|
| Message-ID | <[email protected]> |
Viktor Dukhovni writes: > On Tue, Aug 03, 2021 at 08:25:11AM -0400, Sam Varshavchik wrote: > > > > Some abuse of Delivered-To to trigger bounces has been reported now and > > > then, and the idea of obfuscated Delivered-To: had been discussed, but > > > has not yet been implemented. The freedom to do that some day remains. > > > > I don't see anything intrinsically wrong with this, by itself. It's better > > than nothing. But if the actual goal is to prevent proxy DDOSes, this > should > > be addressed directly: no bounce should be sent via SMTP for mail that was > > accepted via SMTP. > > Getting rid of all after-queue bounces is too drastic a step. It could > some day prove necessary, but I don't think it is warranted at this > time. A more conservative change (already possible, but not enabled by > default in Postfix) is to always include only the headers in bounces > (text/rfc822-headers): > > https://datatracker.ietf.org/doc/html/rfc3462#section-2 > > That should have been the required format for bounces of EAI mail, > obviating the need for the message/global (transfer-encoding of > composite MIME parts) abomination. This still leaves plenty of room for bandwidth amplification: EHLO MAIL FROM:<[email protected]> RCPT TO:<[email protected]> DATA Delivered-To: [email protected] . This gets returned with comparable SMTP commands, with minimal net change, there. But then extra bandwidth in terms of the message envelope from the bouncing mail server, a brief introduction containing the complaint that the Delivered-To: header already exists, a copy of this sole header, and MIME scaffolding. That's going to be several degrees of magnitude larger than this sole header, for certain. _______________________________________________ ietf-smtp mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-smtp
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEMWrVnbBKLOeG9ifkazpiviedvyUFAmEJsyoACgkQazpivied vyUS7xAAubEyVP5woD2yHv6sCzP6NzQMoRvzfxsL0HkpYHRb5g2gpLKJc/ykq3xb KF1KbE+7K/9NfgZtcE/Z3olDDMr5vAokgll4gMwJXhAUTglIyVV+NtQX2yq2e51G p03HYPy0SuvH8tzLA94huGvwbKdV6eB8o7NG6/TLUDYWkSHLpDb/lcbxaqREvRB3 lDUtSAnPed2kgODQ3CS23QxJZvD389lfRaqsiqaNuOVFpvHefbW8SqkNDZqVvWqr NbJxIvIayj0dESIJ8lx/r1zt19bnbTuBtRSkni7lWRYKVMx5Od4iFZJjzLurhBhg mRIaVdFQsAyWM8/kajyI3ea9FOnAlle+Mr2YEUvjRpFYtsG8Rjz6tJzIdNG4VzFk 28BA/ElNfJVhKo+YmZDh4FGt50yrRJ4yMMKbSSNnYkhKDamjovD/7gTrcP9+JyLd Uju1Jz4NNxRzkDdj3aOm+VepUm2Oaq3GhpkzYBKrQDmPMLcqCC7PpNkEzD7Y92nI djLXCHqThYDnkm41jg1U6v3zzEyeCR7Y8oAQkpYlmUvHaPnP498XHnLm2TcfDv/A FWiU9ifdkK6lNvW/r4r7kCeSrpzZYiBIlKoBiENifTrC1XjkIu9LKP9DVO5bPT+N hsZtlnftUxOVJORuoo8nPMkFt0QnO9GmdiFG+E0YhJhrQ8yn3QY= =2wc0 -----END PGP SIGNATURE-----