[FEATURE] Newsletter Subscription confirmation email

[r3yc0n1c]

Why do we need this improvement?

Currently, users who subscribe to the newsletter do not receive any confirmation or feedback acknowledging their subscription, which can cause confusion. A confirmation email enhances the UX, builds trust, and ensures proper communication.

How will this change help?

• Improves UX: Users will receive instant feedback that their subscription was successful.
• Builds trust: A confirmation email reassures subscribers and establishes credibility.
• Reduces errors: If users accidentally subscribe with a wrong email address, they can recognize the mistake and take corrective action.
• Increases engagement: The confirmation email can include a brief introduction to the newsletter, setting expectations for future content.

Screenshots

newsletter-email-conf.mp4

How could it be implemented/designed?

1. Trigger on successful subscription:
   • When a user subscribes to the newsletter, trigger an event to send a confirmation email.
2. Design of the email:
   • Subject
   • Body
   • A personalized greeting (e.g., "Hello [User], thank you for subscribing!")
   • Brief description of the newsletter content and frequency (e.g., "You’ll receive updates every [X] weeks.")
   • An option to unsubscribe or manage preferences.
3. Create a new Netlify Cloud function for the confirmation email, following the same approach as the newsletter updates.

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[r3yc0n1c]

Waiting for triage. I'm willing to work on it once it passes triage.

[Aditya-Prakash14]

/assign

[r3yc0n1c]

/assign

please read CONTRIBUTING... the issue is awaiting triage and is already being worked on

[neerja-1984]

is the issue solved / being solved .. as of now its not assigned to anyone and i wish to contribute

[priyanshuxkumar]

is anyone working on this issue ??

[r3yc0n1c]

I'll, once they approve it

[Amaan2402]

Can i work on this issue??

[anshgoyalevil]

@r3yc0n1c
That's actually a good to have feature, but please propose the basic idea before creating a PR. Some points that I think would be worth noting:

• How would you manage rate limiting? Suppose a bot submits temp emails as a DOS attack
• Which mail server would you suggest? We are an open-source organization that can only rely on free tools and services.
• Newsletter forms ingest the email data to MailChimp. How do integration and duplicate email check systems work here?

[Manancode]

We can use reCAPTCHA or IP-based rate limiting to prevent bots. As for integrating with Mailchimp their API allows us to check for duplicates before passing data and for mail server either we can rely on free trial services or we can self-host using Postfix or Exim. @anshgoyalevil
I'll make a PR after @r3yc0n1c if any of these issues remain.