About SitePM Messaging System 

Concepts Behind the SitePM Messaging System:
SitePM Messaging System is a rather large, conceptual change in how messaging works. Modern email defense is a hybrid of filtering, algorithms, software, and other means that, despite sincerest efforts, have left us with more problems that we had before, and they still have not put a dent the spam problem.

When we designed SitePM we first addressed the most common problems associated with email in general, not just spam. Let us explain:

If you could picture the general idea of how email works, it would be a straight line. On the far left would be a sender--> That sender connects to the web and sends a message--> The message is delivered to the server--> Once it is delivered it encounters filters and security--> You open your email and receive the message.

We identified four key problems and built SitePM Messaging System around solving those problems, as well as a few minor ones. The four problems we identified were:

  1. Lack of User Control: Users were loosing more and more control to ISP's and other services. While some solutions are effective at identifying spam, they aren't very effective at identifying valid emails. In many cases, security would block valid emails.

    The result was a systemic need for allow sender lists and other methods to prevent the loss of important messages. The problem wasn't solved; just moved to another folder. While the majority of spam was no longer in your inbox, people were now spending countless amounts of time going through a spam folder to find valid emails.

  2. Required Spam: From an information technology standpoint, spam prevention is backwards. In order for security to work, it requires that spam be delivered in the first place. That is the equivalent of letting everyone into a bank vault and then having security try to filter out who is supposed to be there and who isn't.

    Current spam prevention does not work because it is message-based and not sender-based. Also, where security is placed in the line is wrong. Security should be before the message is delivered to the server.

  3. No Trust: Going back to the bank vault example... Now that everyone is in the vault, security is trying to filter out who is supposed to be there and who isn't, but no one has any credentials, so they use a general profile for everyone, (the equivalent of a filter). Today, anyone to send you a message from anywhere at any time or any place, without credentials, whether you trust them or not. A sender has no accountability when using the system and that means that if that person abuses the system, there is no repercussion.

  4. Attachments: The majority of viruses, malware, worms, Trojans, spyware and other malicious software and infections come from attachments. Things like key loggers compromise security and your identity. It is also a trust issue that anyone can send you attachments without your permission.

There are several other problems associated with email today that can be listed, however by solving those four problems, upwards to 99% of them would be solved. Moving forward, here is what SitePM Messaging System does.

Addressing the Problems.
The first step was to solve user control, so what we did was take away the server-controlled security and gave it to the user. This let's the user decide who can and can't send a message. The only downside is that without a pre-defined spam detection list, the user is temporarily open to spam. The upside is that it is just temporary. The more the user's use their security, the more effective it becomes.

It is effective because of where security is placed. Security is placed before a message is sent. This forces the user to pass not only the built in security of SitePM Messaging System, but the security preferences of the user. Remember that line example of how email works? Spam is no longer required as security is applied at the first stage, before a message is sent and not after it is received.

This was the first step in establishing trust. With security built before a message is sent, it automatically solved the trust issue. Everyone now has permission to send a user a message until it is revoked. Some argue that this is how it is today, but it isn't.

They key difference is that with the existing system, blocked data is still delivered to the system and then 'hidden' from the user until it is discarded by the ISP or service. With SitePM Messaging System, no data is delivered. Instead the sender receives an error message and all data is automatically discarded.

Addressing attachments was a mess. Not only did the majority of computer infections stem from attachments, but managing the files was a hassle, and there was still the trust issue of anyone being able to send you any file w/o your permission. We scrapped the existing concept of attachments and replaced it with something more practical - File Management.

The benefits of file management are staggering. Most of them are mentioned in the whitepaper (soon to be released), but the most beneficial is that now it was possible to add a security measure that made certain that only people with your permission could send you any file.

This conceptual approach to control, security, and messaging has made this system one of the most effective solutions for not just spam prevention, but several other problems as well.