RE: CBV

> From: Meng Weng Wong
> Sent: Thursday, April 29, 2004 3:03 PM

<...>

> If an SES message has a dozen addresses on a CC line, and one of those
> addresses is a web archiver, another is a regular user, and a third
> address bounces, the same message with a single SES
>
>  - has been successfully delivered,
>  - is the cause of a DSN,
>  - is exposed to the web.

Just like any other MTA, we would expect the web archiver to use an
SPF/SRS/SES compliant front end which would unwrap the signed return path
into an unsigned Return-Path: header.  If the web archiver is broken enough
that it saves raw signed addresses and exposes them to the web, customers
that use either SRS or SES would not use their service and they would either
change their configuration or suffer a significant loss of business.  I
suggest this problem would rapidly self-correct, just like broken mailing
lists that use MAIL FROM: rather than the From: header for user
confirmation.  Losing customers is a terrific motivator for change.

--

Seth Goodman