Hi!

No at the moment I would create a "test lits" and send for real, then copy it back into the draft-folder, that also good to make sure that all the "live"-render tasks works as the should.

// m

The emails our customer is sending are coming from the content section. At the moment we are not allowing them in the newsletter studio section. To keep it simple for them. So making a copy isn't an option.

Hi Sander!

I see!

I will add this to our backlog and include it in the next update but I can't give you an exact date for the release - how urgent is this for you?

Thanks for putting it on the backlog. I'll discuss the urgency with our customer and I'll keep you posted.

It'd be good to have as sending to test lists doesn't allow you to send a test of the email etc.

For now you should be able to hack it and change SendTestEmail to something like this:

[HttpPost]
public HttpResponseMessage SendTestEmail(HttpRequestMessage request, SendNewsletterViewModel vm)
{
    var sendTo = vm.SendTestEmailTo;

    if(string.IsNullOrWhiteSpace(sendTo))
    {
        return request.CreateResponse<ApiResponse>(HttpStatusCode.BadRequest, new ApiResponse()
        {
            Success = false,
            Message = this.Localize.Get("ns_couldNotSendDueToEmail")
        });
    }

    var emails = sendTo.Split(',', ';');
    foreach (var email in emails)
    {
        if (Common.IsValidEmail())
        {
            ... as it is now
        }
    }
}

It would be better doing the loop once the content has been customised but as a quick fix... :)

is working on a reply...