yfb
Sep '16

I received the message you refer to in the help page on integrating e-junkie with third party services - I have no idea where to start to fix it. Are you able to tell where the process with Mailchimp is falling down?

Thanks;



This is a notification that for the transaction 6KN77216J31484121, we were unable to notify your server at 1http://eepurl.com/xxxxx1 as we we received the error: HTTP Error 302



POST /xxxxx HTTP/1.1



Accept: /



Host: eepurl.com



Content-type: application/x-www-form-urlencoded



Content-Length: 1407



Expect: 100-continue











HTTP/1.1 100 Continue







HTTP/1.1 302 Moved Temporarily



Server: nginx



Content-Type: text/html; charset=UTF-8



X-UA-Compatible: IE=edge,chrome=1



Location: http://yourfamilybudget1.



Content-Encoding: gzip



Vary: Accept-Encoding



Date: Sat, 10 Sep 2016 14:12:05 GMT



Connection: close



Set-Cookie: AVESTAENVIRONMENT=prod; path=/

  • created

    Sep '16

  • last reply

    Sep '16
  • 1

    reply

  • 1.7k

    views

  • 2

    users

  • 3

    links

E-junkie_MonsterSupport Monster
Sep '16

Unfortunately Mailchimp is no longer going to support integration with E-junkie and to our knowledge they aren't giving out working notification URLs any longer.



If you do have a notification URL from them try entering it directly as your Common Notification URL instead of using their URL shortener. From the error message it looks like the redirection from the short URL to the real thing didn't take and there's no need for a shorter URL in the notification field since that's handled automatically.