Dennis Gearon wrote:
Jonathan A. Zdziarski wrote:
How about an XML standard that defined ways that a mail server could
accept/bounce/drop down a canyon/etc emails? The users uploads the
file and voila, enforcement happens while email client is offline.
Of course, it needs a nice SIMPLE GUI, etc.
XML is pretty bandwidth intensive though, as compared to some smaller
protocol. If this were to become a widely accepted standard, an
architecture might emerge where you could have 100 "dumb" mail servers,
and one or two "policy servers" for lack of a better name. In that
case, you'd want to have the most lightweight protocol for communicating
between them. Maybe XML will work... hmm.
This XML file only gets transmitted when the user changes his/her
policy. It resides for the most part, unchanged on the user's email
server, telling the mail server the mail user's wishes by 'proxy'.
This would be a very easy way to combine:
white lists
gray lists
filtering standards
DNS based stuff
for the filtering standards, something like this could be done:
<filter application>
<filter name>Spam Assassin</filter name>
<min version>4.5.6.7.8.9-super_duper_beta<min version>
<specific criteria one> likdra;lekfwe;ofjn</specific criteria one>
<specific criteria two> likdra;lekfwe;ofjn</specific criteria two>
</filter application>
Upon upload, the mail system can reject it saying, 'don't have such
application', or if the application exists, the application can reject
the input based on the version number or the
missing/wrong/inappropriately mixed criteria, transparently to the MTA.
It just returns the string.
Or in the cases of point-to-point enforcement:
<filter application>
<filter name>body_embedded_PKI_digitally_signed_testing
application</filter name>
<accept list>
<accept from>
<email address>joe_smuckatelly(_at_)foo(_dot_)bar</email_address>
<name>joe smuckatelly</name>
<embedded phrase at beginning of body>chicken ranchers
have lots of chicken doo doo for sale</embedded phrase at beginning of body>
<encryption method>blah blah</encryption method>
<base_64_crypto_key>iebt0uq2b350[n9u2 b5p9n
2b45p'24 b 'u2b45p9 2v459nqwvtu.onjvrlinvwn</base_64_crypto_key>
</accept from>
<accept from>
blah blah blah
</accept from>
</accept list>
</filter application>
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg