What a waste of time. Seriously. Just have a look at
U.S. Patent No. 6,018,761 and see for yourself.
This won't hurt Apple, nor any of the other defendants, simply because it doesn't do anything related to the so called patent infringement.
That's what I've been trying say
Broad claims that can only be loosely tied to todays spam filtration.
As a disclaimer, I'm not a patent lawyer, nor will I pretend to be.
Furthermore, the claims are so broad that they apply to pretty much all post-email processing, which is why this patent will get shot down. In the patent it claims receiving context clues from the email, then throwing them on a database for reference, and then claims to patent the general reading of email's context clues, the aforementioned communication with a database, and then reading that database for reference. Unfortunately, this applies to pretty much everything, not just spam filtration, and the methods for obtaining the context clues are not really defined.
No one uses vCards, and while whois organization lookups can occur, no one does this to fill out contact information in the user database, which really seems to apply more to this than anything. While it was applied to initial spam filtration through context clues provided in the mail versus checking against a compiled blacklist database, it really isn't entirely used in this context today. This patent could apply both to old spam checking and old spam filter creation, as both methods require reading context clues and either checking them against a database or including them in said database, and then processing said mail accordingly.
The problem with this claim, however, is that in today's processing context clues are still used; but not necessarily the ones listed in the patent. Databases will always be accessed upon checking context clues, and the patent is overly broad and doesn't a) Define what database, b) Define what type of database, c) Doesn't define the connection to said database, and d) Simply lists any database or list outside of the email, even within the program, as within its claims. That pretty much nails any content/context clue services, as they all contact/communicate outside of the individual email. That's too broad in my opinion. This means aggregating contact information or email addresses from an email, both automatically and manually, would therefore be in violation of this patent, as they are context clues, and you're connecting to sources outside of the email.
Furthermore, current generation spam filters don't use blacklists, and instead use adaptive filtering. This goes beyond the traditional access to a database; while it uses context clues, these go outside the scope of the patent in so far as they farm data beyond address, phone numbers, etc, as defined as "context clues" within the patent. To this end they have a defense, as a lot of the data collected for adaptive filtering isn't listed as context clues, however since they also collect said context clues, and communicate outside of the email, it still falls underneath the patent, despite having a different approach. As far as I'm aware these modern day "context clues" are still complied for spam lists, as similarities between dinged emails are recorded for spam filtration. The difference, essentially, is that you're not making your own blacklist (per the old definition of banned emails, companies, etc), but rather that the filter is adaptive based on similarities the program finds between the emails, making a better, stronger, and more accurate filter that goes beyond the context clues and into text fragments, names, format, etc. This new filter, while not the same as an old blacklist filter as it carries a different format, still falls under the broad, overreaching claim of connections to sources outside of the email.
Basically, the patent claim is too broad in my opinion because of the database communication claim, as well as the context clues. If he defined a better method for communicating outside the email or farming the context clues it might hold true, but current spam filtration methods still infringe because they still collect traditional context clues as defined in this patent. To that end I think its out of line; context clues are too general and too common to be patented in a method; we're talking names, addresses, and numbers here; people's personal information. Furthermore, stating any communication to an outside source is far too broad; this means any data farmed from emails, whether it be for blacklists, graylists, adaptive filtering, or contacts falls within the scope of this patent, rendering it in violation of said claims.
To be honest this patent really seems more applicable towards auto-adding contact information based on the collected context clues in the aforementioned email, but that's just me. To this end it would make more sense in today's systems, but again, it's far too broad and can also encompass both new and old spam filtration techniques. That's just my opinion though, I'm sure those with law degrees will disagree.
This also doesn't include the argument of previous art, which can explored.
Actually, this patent does have a serious 35 USC 101 issue as it seems to claim an abstract idea. The claims are very poorly drafted.
That's what I've been trying to say, there's no specific, defined methods, its just general, overreaching claims about an idea, but little to no implementation. But again, you're the lawyer, not me