[GH-ISSUE #289] [BUG] 'Confirm Payment' email arrives unencrypted despite recipient having PGP key uploaded #245

Closed
opened 2026-03-01 17:46:00 +03:00 by kerem · 2 comments
Owner

Originally created by @alexaka1 on GitHub (May 19, 2022).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/289

I have changed my subscription and got an email from mailer@anonaddy.me with subject 'Confirm Payment'. The body contains the usual AnonAddy styling, and this

Confirm your $XX.XX payment
Extra confirmation is needed to process your payment. Please continue to the payment page by clicking on the button below.
[Confirm Payment]

My default recipient (which this email was sent to) does have a PGP key set and it's activated.
I've read in a previous patch note / blogpost that you updated the code to use the PGP key during billing as well (if set). Here's what I was thinking of.
I think this is a bug.

I can send you more details in private, if needed. Just point me in the direction.
(Also, the email wasn't sent to the alias that is set up on the Stripe billing portal. It was To-d directly to the recipient address. That alias correctly got the receipt later in encrypted format.)

Originally created by @alexaka1 on GitHub (May 19, 2022). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/289 I have changed my subscription and got an email from mailer@anonaddy.me with subject 'Confirm Payment'. The body contains the usual AnonAddy styling, and this > Confirm your $XX.XX payment Extra confirmation is needed to process your payment. Please continue to the payment page by clicking on the button below. [Confirm Payment] My default recipient (which this email was sent to) does have a PGP key set and it's activated. ~~I've read in a previous patch note / blogpost that you updated the code to use the PGP key during billing as well (if set).~~ [Here's what](https://github.com/anonaddy/anonaddy/projects/1#card-52590392) I was thinking of. I think this is a bug. I can send you more details in private, if needed. Just point me in the direction. (Also, the email wasn't sent to the alias that is set up on the Stripe billing portal. It was To-d directly to the recipient address. That alias correctly got the receipt later in encrypted format.)
kerem closed this issue 2026-03-01 17:46:00 +03:00
Author
Owner

@willbrowningme commented on GitHub (May 20, 2022):

Thanks, you're right I must have overlooked this notification when I added encryption for all other notifications since it's in the Laravel Cashier vendor files.

I'll override that notification and try to get it updated shortly.

<!-- gh-comment-id:1132701651 --> @willbrowningme commented on GitHub (May 20, 2022): Thanks, you're right I must have overlooked this notification when I added encryption for all other notifications since it's in the Laravel Cashier vendor files. I'll override that notification and try to get it updated shortly.
Author
Owner

@willbrowningme commented on GitHub (Aug 3, 2022):

Just fixed this, thanks again for letting me know.

<!-- gh-comment-id:1204144199 --> @willbrowningme commented on GitHub (Aug 3, 2022): Just fixed this, thanks again for letting me know.
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#245
No description provided.