Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Habeas Watermark Not Really used Anymore? #65

Closed
justingit opened this issue Sep 14, 2010 · 2 comments
Closed

Habeas Watermark Not Really used Anymore? #65

justingit opened this issue Sep 14, 2010 · 2 comments

Comments

@justingit
Copy link
Owner

It's not clear if there's any support for the Habeas Watermark anymore - it looks like the Haiku stuff isn't very effective anymore and was replaced by a difference system:

quote: http://www.returnpath.net/habeas/Knowledge-Base/Miscellaneous/
Isn't Habeas the company that uses a haiku as a way to identify legitimate email? What happened to the haiku?

At its inception, Habeas licensed a copyrighted haiku to be used in email message headers as a method for receivers to identify legitimate, wanted email from senders that had passed the Habeas Certification process. Litigation would be pursued against those who used the haiku without being licensed to do so. Habeas successfully sued several spammers for unauthorized use of the haiku. However, so many spammers began using the haiku without authorization that it was impossible to pursue litigation against all of them. Consequently, Habeas developed the Safelist as an adjunct to the haiku. A message containing the haiku would trigger a check of the Safelist to determine if the message had originated from an authorized IP address.

As time passed, Habeas realized that the Safelist was a more efficient way of identifying Habeas Certified senders. Use of the haiku was disfavored, and two header lines were substituted. These two new headers also triggered a check of the Habeas Safelist, but the headers were not copyrighted and were not the basis for litigation. Senders using Confirmed Opt-in address collection practices may still use the haiku, but it is no longer a requirement.

This would be more of a .1 kind of change... I wouldn't mind replacing this with a more up to date system - whatever Return-Path has in mind. But it's not a super-duper priority for me as a bug fix kind of thing.

@justingit
Copy link
Owner Author

I've added this as a "known issue" in the docs.

@justingit
Copy link
Owner Author

Closed.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant