Re: Updated draft for "SMTP Response for Detected Spam"

Good idea Alex.

I like and support this idea for a "259" reply code to indicate a 
message was accepted but imported/move to the MSA/MDA "spam" folder.  
This can drastically reduce/address support questions regarding 
unsolved non-inbox deliveries.   I can add support to Wildcat! SMTP as 
an experiment.

I take it, there are no legacy clients who will "fail" on a 259 reply 
code.  I think overall, 259 or just 250, MSA/MDA receivers should help 
delivery support issues by describing inbox versus non-inbox reception 
in the acceptance response text.

In fact, it should be extended to beyond spam, for example, mail 
accepted but discarded for local policy reasons.  I hope Google would 
support this because I have a few cases where customer mail is 
received (250 positive response) by gmail but are not delivered, nor 
found in any folder, i.e. as if it was discarded.

Thanks


On 3/30/2022 1:37 PM, Brotman, Alex wrote:
> Hey folks,
>
> I wanted to send an update for this draft.  I received (negative) feedback from one person via the list, though several outside of the list were supportive.  I wanted to try to clear up some of the language in the draft.  Appreciate feedback from those who are interested to read.
>
> https://www.ietf.org/archive/id/draft-brotman-srds-01.txt
> https://datatracker.ietf.org/doc/html/draft-brotman-srds-01
>
> Thanks
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> ietf-smtp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ietf-smtp
>
>


-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos