mstefan said:TommyCarlier said:*snip*Not to mention the huge number of legacy MUAs that are still out there which only implement RFC 821, and not all of those are clients running on a desktop PC. For example, a lot of devices have options to send email notifications, and unlike software on desktops, those devices aren't usually replaced and/or updated frequently (presuming you can even get a firmware update). So requiring any kind of substantive change on the mail client side would just break a lot of code and tick off a lot of users and their admins.
For anything to be really successfully adopted, I think it has to be solely on the server end of things, and it needs to be implemented in a way that penalizes servers that don't comply with the "new rules", but doesn't actually drop the message (at least during a transition period). Instead, the postmaster for the domain gets hate mail from the other servers saying "Hey, update your mail server software or we're going to stop delivering to you eventually".
Also any change has to have a way to allow a transition and to have a window of time where old and new can mingle and interoperate.
any chnage that does not do that at least in the early stages is also a "non starter"
I would love to see a mix of your ideas and my ideas actually get used .... I think we both agree that making the bulk senders have to pay a cost for bulk sending w/o having to take them to court will be a very effective tool in this area.
