figment
New Member
Hi guys,
We have a web application that relies on email (eg: template@newsletter.com) to deliver the final result (email newsletter template). Now we have some restrictions in place in that you can only send the final newsletter to the email address you sign up with (you look after your own distribution) and you have to click on a confirmation email link the first time you sign up.
Even with this restriction i know at some point someone is going to play silly buggers and report this email address as spam. When this happens it will effectively shut down the application until fixed. So to pre-empt this what are my alternatives? I am actually looking for two options. 1st a cheap temporary solution that we can use until the application is generating revenue and supporting itself. Second a long term strategy that we can use when we have a budget to play with.
Any ideas?
We have a web application that relies on email (eg: template@newsletter.com) to deliver the final result (email newsletter template). Now we have some restrictions in place in that you can only send the final newsletter to the email address you sign up with (you look after your own distribution) and you have to click on a confirmation email link the first time you sign up.
Even with this restriction i know at some point someone is going to play silly buggers and report this email address as spam. When this happens it will effectively shut down the application until fixed. So to pre-empt this what are my alternatives? I am actually looking for two options. 1st a cheap temporary solution that we can use until the application is generating revenue and supporting itself. Second a long term strategy that we can use when we have a budget to play with.
Any ideas?