No, that's not something I'd expect the general public to use, but it's a good start and proof of concept.
Email itself provides you transport, storage, and overall format definitions.
MIME gives you attachment encapsulation for whatever format you care to provide.
MIME encoded signatures give you authentication and/or privacy (you care about that shit, right?)
Now "all you need to do" is define a task management standard and the interchange format that it uses. Drag'n'drop or procmail/maildrop filter attachments to your task management tool.
Wait for the world to beat a path to your door.
You've identified ONE use-case for mail. As with other use-cases, there are a few bits that could be tweaked to make it so (the standards adoption bit is the hard one). And while email / SMTP certainly has its warts, there's no need to scrap the entire system for your specific needs.
What you want is at task management system with a defined format which can be encapsulated in email messages.
Say, like, Debian's BTS: http://www.debian.org/Bugs/server-control
No, that's not something I'd expect the general public to use, but it's a good start and proof of concept.
Email itself provides you transport, storage, and overall format definitions.
MIME gives you attachment encapsulation for whatever format you care to provide.
MIME encoded signatures give you authentication and/or privacy (you care about that shit, right?)
Now "all you need to do" is define a task management standard and the interchange format that it uses. Drag'n'drop or procmail/maildrop filter attachments to your task management tool.
Wait for the world to beat a path to your door.
You've identified ONE use-case for mail. As with other use-cases, there are a few bits that could be tweaked to make it so (the standards adoption bit is the hard one). And while email / SMTP certainly has its warts, there's no need to scrap the entire system for your specific needs.