You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't need encryption, but signing ( via pgp ) the mail would be beneficial.
( not secret, but authentic sender )
and/or: if the incoming emails are pgp-encrypted, to be processed.
some servers are outside and provide status (updates needed) via email to redmine.
having that encrypted might be cool.
The text was updated successfully, but these errors were encountered:
@ sign only
What would be the usecase exactly? If users (including bots) are capable of signing/validating mails, they are also capable of en-/decrypting them. The only difference I see is that users don't need to provide the passphrase for received mails (although passhrase is needed to send signed mails). I don't see, why you should drop encryption, even if not needed explicitly.
@ import encrypted mails
If those status mails would be an encrypted mail response to a ticket, and are piped into the rdm_mailhandler, it should work fine right now. Probably I don't get your point, could you elaborate?
I don't need encryption, but signing ( via pgp ) the mail would be beneficial.
( not secret, but authentic sender )
and/or: if the incoming emails are pgp-encrypted, to be processed.
some servers are outside and provide status (updates needed) via email to redmine.
having that encrypted might be cool.
The text was updated successfully, but these errors were encountered: