We are planning to use your module one of our new sites. We already have a subscriber base of around ~25000 users on the existing site and will be migrating these memebers to your module.
It will be great if you are able to assist us with the following questions:
oAny issue using the tools for a list of 25000 email address. The emails will be sent once every couple of weeks and won't always be 25000. In general, it will be a
oWill this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
oIs their any value in using Newsletter studio in a separate instance of Umbraco (different to the production site) and if yes then do you have any tips on mplementation: database replication…
oAny potential issue regarding getting black listed? Do you have any tips around best practice for not getting black listed?
1. Any issue using the tools for a list of 25000 email address. The emails will be sent once every couple of weeks and won't always be 25000. In general, it will be a
The system has been tested with 100 k emails and works great.
2. Will this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
During this the development of the send out engine we spend alot of time optimizing this to take up very little resources, but of course it will use some. We decided to make the send out slower to save load from the server. The load is shared between the web and mail servers, but if this is critical you sohuld
3. Is their any value in using Newsletter studio in a separate instance of Umbraco (different to the production site) and if yes then do you have any tips on mplementation: database replication…
It would be possible but in the most senarios this will introduce more complexity than value.
4. Any potential issue regarding getting black listed? Do you have any tips around best practice for not getting black listed?
This risk is always present. Don't spam people and make sure that you mail server i configured in the right way. To really avoid this you could use an SMTP-relay service like MailGun och SendGrid.
5. Any potential issues regarding timeout? The send out runs in its on thread that will not time out until the send out is done. During this process everyting i persisted in the db so you don't need to keep the browser open if you don't want to. If something happens and the thread is killed, the send out will continue when the server is running again (thanks to a scheduled job in Umbraco that will fire ths action).
Just let me know if you need anything else or want to have a full license for the testing.
One of your answers is incomplete. it will be great if you can add to it...
2. Will this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
During this the development of the send out engine we spend alot of time optimizing this to take up very little resources, but of course it will use some. We decided to make the send out slower to save load from the server. The load is shared between the web and mail servers, but if this is critical you sohuld
You should do some testing of the package and see how it works in your enviroment. If you need a full license for the testing just let me know. My email is markus [at sign] enkelmedia.se.
Module query
Hi Mark
We are planning to use your module one of our new sites. We already have a subscriber base of around ~25000 users on the existing site and will be migrating these memebers to your module.
It will be great if you are able to assist us with the following questions:
o Any issue using the tools for a list of 25000 email address. The emails will be sent once every couple of weeks and won't always be 25000. In general, it will be a
o Will this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
o Is their any value in using Newsletter studio in a separate instance of Umbraco (different to the production site) and if yes then do you have any tips on mplementation: database replication…
o Any potential issue regarding getting black listed? Do you have any tips around best practice for not getting black listed?
o Any potential issues regarding timeout?
Hi Karan!
Thank you for looking at the package!
1. Any issue using the tools for a list of 25000 email address. The emails will be sent once every couple of weeks and won't always be 25000. In general, it will be a
The system has been tested with 100 k emails and works great.
2. Will this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
During this the development of the send out engine we spend alot of time optimizing this to take up very little resources, but of course it will use some. We decided to make the send out slower to save load from the server. The load is shared between the web and mail servers, but if this is critical you sohuld
3. Is their any value in using Newsletter studio in a separate instance of Umbraco (different to the production site) and if yes then do you have any tips on mplementation: database replication…
It would be possible but in the most senarios this will introduce more complexity than value.
4. Any potential issue regarding getting black listed? Do you have any tips around best practice for not getting black listed?
This risk is always present. Don't spam people and make sure that you mail server i configured in the right way. To really avoid this you could use an SMTP-relay service like MailGun och SendGrid.
5. Any potential issues regarding timeout?
The send out runs in its on thread that will not time out until the send out is done. During this process everyting i persisted in the db so you don't need to keep the browser open if you don't want to. If something happens and the thread is killed, the send out will continue when the server is running again (thanks to a scheduled job in Umbraco that will fire ths action).
Just let me know if you need anything else or want to have a full license for the testing.
// Markus
Thanks Markus
One of your answers is incomplete. it will be great if you can add to it...
2. Will this slow down our server when sending emails? If the load is actually shared between the SMTP and the web server. Our guess is that the web server is just creating the email and the SMTP will queue them to be process… so the load will be more on the SMTP side…
During this the development of the send out engine we spend alot of time optimizing this to take up very little resources, but of course it will use some. We decided to make the send out slower to save load from the server. The load is shared between the web and mail servers, but if this is critical you sohuld
Ohhh
Haha =D I'm sorry.
You should do some testing of the package and see how it works in your enviroment. If you need a full license for the testing just let me know. My email is markus [at sign] enkelmedia.se.
// Markus
is working on a reply...