Hi @zhakkarn first off thanks for the assistance with the heroku app. I was able to show them the user interface and that alone was enough to get their gears spinning.
Previously we used a paid platform that allowed our database/ BE layer to take new users events parse them and then feed them to a paid mailing platform. We currently have multiple mailing lists, and I'm envisioning take the event, format it, and send to the mail four good application. Upon where it gets placed into the correct mailing list. Additionally it would be nice to have the response status from the mail blasts to be sent back to the primary backend so we can figure out what to do with those.
Pretty much we want to have our non-technical marketing person not have to perform weekly database queries, or use our admin dashboard and manually update the lists.
The weird {email}},<
link points to:
https://bingobo.herokuapp.com/clickthrough?url=div><div><br></div><div>Go to {freecodecamp/https://www.freecodecamp.com&trackingId=example-tracking-id
maybe some parsing issue or i'm missing something?
And if i remove either the email variable or the link, it works as expected
@QuincyLarson @zhakkarn @karuppiah7890
{label/link}
, in this case it took {{email}},</div><div><br></div><div>Go to {freecodecamp/https://www.freecodecamp.com}
instead of what you intended (see the missing '{' on the left of the variable in the second image and the fact that the variable hasn't been replaced by its value). I'll keep searching as to why it was done in this order because to me the code looks synchronous and deal with the variables before.
Trying to revive an older Github issue: freeCodeCamp/mail-for-good#226
Looks like @karuppiah7890 or @4iar might know how to solve it
TL;DR, I'm having trouble getting MfG to consume the feedback from Amazon SES. That is, when Amazon SES tells my app that an address has bounced or complained about spam, the app won't show that info in the campaign report, and more importantly, it won't removed bounced addresses and complaint addresses from my email list.
The list I'm working with unfortunately has enough faulty emails that my SES account will get put on probation if I try to send more messages (Amazon requires a bounce rate of less than 5%). If I can just get one good round of feedback from SES, I should be able to clean out that list.
Hi, I had a working MFG instance about a year ago. I recently booted it back up and it seems I am having trouble with Google oAuth. I get an internal server error upon trying to log in. Here is the trace:
app_1 | Error
app_1 | at /usr/src/app/node_modules/passport-google-oauth20/lib/strategy.js:95:21
app_1 | at passBackControl (/usr/src/app/node_modules/oauth/lib/oauth2.js:132:9)
app_1 | at IncomingMessage.<anonymous> (/usr/src/app/node_modules/oauth/lib/oauth2.js:157:7)
app_1 | at emitNone (events.js:110:20)
app_1 | at IncomingMessage.emit (events.js:207:7)
app_1 | at endReadableNT (_stream_readable.js:1045:12)
app_1 | at _combinedTickCallback (internal/process/next_tick.js:138:11)
app_1 | at process._tickDomainCallback (internal/process/next_tick.js:218:9)
What are the most common issues with Google oAuth, I've tried just about everything and can't get it to work.