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

MaildbPrivacy Policy ‧ not tracked anymore #2867

Open
1 task
tosdr-bot opened this issue Jun 22, 2024 · 0 comments
Open
1 task

MaildbPrivacy Policy ‧ not tracked anymore #2867

tosdr-bot opened this issue Jun 22, 2024 · 0 comments
Labels
to clarify Default failure label [managed by OTA]

Comments

@tosdr-bot
Copy link
Collaborator

No version of the Privacy Policy of service Maildb is recorded anymore since 22 June 2024 at 9:40:12 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

  • Fetch failed: request to https://maildb.io/privacy failed, reason: write EPROTO 80FC62697C7F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 80

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-06-22T09:40:12Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-22T09:40:12Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@tosdr-bot tosdr-bot added the to clarify Default failure label [managed by OTA] label Jun 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to clarify Default failure label [managed by OTA]
Projects
None yet
Development

No branches or pull requests

1 participant