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.
Another way to save on the need to read this file for every mail is to
have the relevant applications cache this either in memory, or in a
filetype of their choosing and under their control.
The command set to each application or the API would have a commmand for
'reload' and give the file location. It would take out what is relevant
to it and ingnore the rest. I think a GET/POST/argv/argc/command line
argument approach would work to supply file name.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg