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

"Couldn't properly send message to **Secured**!." #151

Open
BryceStevenWilley opened this issue Sep 8, 2023 · 0 comments
Open

"Couldn't properly send message to **Secured**!." #151

BryceStevenWilley opened this issue Sep 8, 2023 · 0 comments

Comments

@BryceStevenWilley
Copy link
Collaborator

Somehow, someone in IL was able to make a successful filing from a non-confidential case, where both the name of the user and the email seem to be redacted. The name was **Secured**, and the email was *************

I'll have to look into this more, I'm not sure what it could be. Unfortunately, this happened right before I restarted the Efile Proxy for getting MA ready for production, and I failed to save the logs before restarting, as mentioned in #123, logs are still tied to docker containers, so the specific logs were lost. I do have access to the case number filed into and the court, and will take a look at things to see if I can fix them soon.

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