In the past year we have been emailing to our lists on Constant Contact using its browser-based tool to build and schedule the emails. Generally very good deliverability In the last few weeks we've started using the Constant Contact API to automate email generation at our server and created/schedule emails with Constant Contact via their API. Now all of a sudden we are getting reports that SOME list recipients are "not getting" their daily email from us, and those emails are ending up in their spam filters. I know, because I'm on the list, and suddenly my daily email from the list is ending up in spam too. I can "approve" the "sender" of the email in my spam filter, but every day that "sender" changes, thus triggering another email caught in spam. My spam filter is looking at the Return-Path in email head to determine sender, like: Return-Path: email@example.com ...and that Return-Path changes every day, with every email sent to list. And so now spam filters are picking up on that. But oddly, when the emails were SUCCESSFULLY posted to list (before we automated using the CC API), the Return-Path was set in precisely the same way, from all I can tell looking at older emails sent to list. So I'm stumped. I am correctly setting the from_email and reply_to_email vars in the API call, using an approved email address to set both. What am I missing?
... View more
I'm trying to create a new campaign via the CC API through: https://api.constantcontact.com/v2/emailmarketing/campaigns I find I have to "flatten" the JSON I send so there are no line breaks in it anywhere, and then it posts correctly. But how do I preserve line breaks in the text_content part of the email if I have to flatten the JSON that contains that part...and flatten the text_content as a result too? Thanks for your help!
... View more