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

If failed to send encrypted email, send unencrypted error mail #3308

Open
MichaelDwucet opened this issue Jun 4, 2018 · 3 comments
Open
Labels
S: stale Status: stale. This issue has had no activity in a long time, it may not be relevant anymore T: enhancement Type: enhancement. This issue requires improving an existing feature

Comments

@MichaelDwucet
Copy link

On our MISP platform we forced in the MISP settings that outgoing emails have to be encrypted.

We now have a bunch of users, who's PGP keys have expired. Now I see regularly the following error messages in the logs:

Error message:
Email to "email address", titled "subject" failed. Reason: the message could not be encrypted because the provided key is either expired or cannot be used for encryption.

So the users do not get any emails from the MISP platform and did not know about this.

Feature request:
If outgoing email could not be encrypted, have an option to send the user an unencrpyted error mail.

Example text:
Dear $user,
the message titled "subject" could not be sent to your account, because the provided key is either expired or cannot be used for encryption.

Please check your PGP / S/MIME Key in your MISP profile and update it, if it has expired.

$Admin

@iglocska
Copy link
Member

iglocska commented Jun 4, 2018

Good idea. We have to be careful not to spam users with these reminders though, so perhaps the best strategy would be to add a pgp warning lock on the user profile - send a warning, lock it and keep it locked until the user logs in again.

@adulau
Copy link
Member

adulau commented Jun 4, 2018

@iglocska The issue. It's a lot of users don't log very often because they rely on email notification, API or sync. The email replacement idea of @MichaelDwucet seems an acceptable solution as the spam number will be the number of potential notifications.

@adulau adulau added the T: enhancement Type: enhancement. This issue requires improving an existing feature label Jun 4, 2018
@iglocska
Copy link
Member

iglocska commented Jun 5, 2018

Ok could do. Worst case we get complaints, in which case we can still rework the idea.

@SteveClement SteveClement added this to To do features in Feature Enhancements via automation Jul 17, 2018
@enjeck enjeck changed the title Feature Request: If failed to send encrypted email, send unencrypted error mail If failed to send encrypted email, send unencrypted error mail Nov 30, 2020
@enjeck enjeck added the S: stale Status: stale. This issue has had no activity in a long time, it may not be relevant anymore label Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S: stale Status: stale. This issue has had no activity in a long time, it may not be relevant anymore T: enhancement Type: enhancement. This issue requires improving an existing feature
Projects
Feature Enhancements
  
To do features
Development

No branches or pull requests

5 participants