Hello, yes, it requires different receivers to know each other capabilities.
Here a new proposed wording, if policy quarantine will be kept: Messages, subject to the quarantine policy, directed to a single recipient that does not support the concept of quarantining, can be either accepted and delivered, accepted and discarded, accepted and bounced, or rejected at SMTP level. Messages, subject to the quarantine policy, directed to many recipients, some of which support the concept of quarantining, and the others not supporting this concept, can be either: * accepted, quarantined for the first group of recipients and discarded for the other recipients, * accepted, quarantined for the first group of recipients and delivered to the other recipients, * accepted, quarantined for the first group of recipients and bounced for the other recipients, * segmented, * rejected as whole, or * quarantined for the first group of recipients, discarded for the other recipients, and at the same time rejecting the message at SMTP level, spelling in the reply to which recipients the message was delivered and to which not. An example for a reply line for the last case is: 550-5.7.1 The mail was delivered in the Junk folder for [email protected] and 550 [email protected]. The mail was not delivered to [email protected]. Discarding and bouncing are to be avoided. Accepting and delivering the message ignores completely the DMARC policy. Segmentation imposes delivery delays. This specification recommends in both cases overriding the policy and rejecting the message at SMTP level. For a message, subject to the quarantine policy, if the receiving server does not know whether a recipient supports the concept of quarantining, the recommendation is to override the policy and reject the message. [...] In the absense of failure reports, rejecting messages with failed DMARC validation allows the sender to determine for which messages the validation failed. When messages with failed DMARC validation are quarantined, the sender cannot find out for which messages the validation failed. I propose this text irrespective of whether policy quarantine will be kept: When the DMARC validation fails, the enacted actions are up to the receiving site. It can simultaneoulsy quarantine the message and reject it at SMTP level, spelling in the rejection reason that the message was delivered in the Junk folder. Regards Дилян On Wed, 2019-07-31 at 20:34 -0700, Murray S. Kucherawy wrote: > On Tue, Jul 30, 2019 at 7:29 AM Дилян Палаузов <[email protected]> > wrote: > > if policy quarantine will be kept, I propose including this text in the > > specification: > > > > Messages, subject to the quarantine policy, directed to a single recipient > > that does not support the concept of > > quarantining, can be either accepted and delivered, accepted and discarded, > > or rejected. > > > > Messages, subject to the quarantine policy, directed to many recipients, > > some of which support the concept of > > quarantining, and the others not supporting this concept, can be either: > > * accepted, quarantined for the first group of recipients and discarded for > > the other recipients, > > * accepted, quarantined for the first group of recipients and delivered to > > the other recipients, > > * segmented or > > * rejected as whole > > Doesn't this, as proposed, require different receivers to know each other's > capabilities? > > -MSK > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
