Newsletter switching to mass mail services.

[unckleg]

Consider switching to some mass mail service (mailchimp, mailgun) and subscribing through service API's.
Or implementing reCAPTCHA (similar protection system) because DB 'll be filled with spam subscriptions if not already (bots are madness :) ).

[tasmaniski]

Basically this is a good idea. At the moment, we don't have any problems with the current implementation, although that's what you are saying is correct.

When or if we decide to change it, that would be through a completely separate package, e.g. MailchimpNewsletter.

I could recommend something similar to you :)
if you want to contribute "Contact Us" package. We don't have it.

Contact us should be completely separated package with one more DB table.

Contact us package should hold:

• Web page with route eg. /contact-us
• POST request to web page eg. /contact-us-post
• Admin pages (CRUD)
• Service layer: ContactUsService, ContactUsEntity, ContactUsMapper, Filters etc.
• Migration for new db table eg. "contact_us" (migration should be in data/phinx/)
• The bonus is: reCAPTCHA and Mailchimp (or similar)

Instalation of new package in the existing system:

• Register new package in config/config.php
• Run migration to create new table
• Add link to Admin menu (changes in admin's layout)
• Add link through admin in the menu with URI "/contact-us"

Please check "Page" for the details and inspiration.

If you would like to continue with this contribution,
feel free to continue the discussion on this thread.

[unckleg]

When or if we decide to change it, that would be through a completely separate package, e.g. MailchimpNewsletter.

Then I think it would be better to develop some MailServiceFactory logic for resolving our Collection MailService packages and it would be easier for developer to plug-in his package into CMS.
But we can talk about it later.

I'm interested in developing ContactUs package so expect new PR soon.