Benjamin Piouffle
Benjamin Piouffle
cc @opencollective/productdesign
That's a good one to fit into the coming sprint. The 1st part should be pretty straightforward.
Also: - https://github.com/opencollective/opencollective/issues/7276
Thanks for documenting this issue @SudharakaP! I wasn't able to pinpoint the root cause. The email failed with one of these contributions, but they look pretty normal: - https://opencollective.com/handsoffuhuru/contributions/733277 -...
@Jibby2k1 It's open for contributions, feel free to open a PR and comment with the link here :slightly_smiling_face:
@MarwanBz it's yours
@hdiniz looks like we've released https://github.com/opencollective/opencollective-frontend/pull/9923, which supposedly fixes this?
**Collective communications** We don't collect user consent for this today, and it's indeed a violation of GDPR. We should: - Have a checkbox in the contribution flow (I think @Memo-Es...
Related: on January 22nd, we sent a changelog entry and noticed a corresponding spike in SPAM reports for our emails (to 0.7%).  What happened: - We [normally](https://github.com/opencollective/opencollective-api/blob/e563b179cd2260c64b7768492d110099f1fdea0a/server/lib/notifications/email.ts#L305) don't send...
Some changes related to this issue: - We've improved our unsubscribe links to better match the standards (https://github.com/opencollective/opencollective-api/pull/9771) - We're making sure that emails are never sent for updates coming...