I'm still unsure why this block was put in place, but MC support was not very helpful either. My options were to "wait it out" or change the website IP. I was able to work around the issue because there is more than public IP address assigned to my server so I needed a way to tell this library to use a specific IP address. I tested this by just live editing the files in my vendor folder to implement CURLOPT_INTERFACE to set the customized outbound IP and this did work around the issue.
To that end, I pulled a fork and pushed a PR with the code change that would allow me specify the source IP I want to use for the connection in the __construct().
The PR is here: #326
The changes are 100% backward compatible.
I'm not sure when (or if) my PR will be merged, so to any future readers needing this functionality, you can feel free to use my fork instead (I'm not planning on having to maintain it but I will do my best if I have to).
https://github.com/BelniakMedia/mailchimp-api
I'm still unsure why this block was put in place, but MC support was not very helpful either. My options were to "wait it out" or change the website IP. I was able to work around the issue because there is more than public IP address assigned to my server so I needed a way to tell this library to use a specific IP address. I tested this by just live editing the files in my vendor folder to implement
CURLOPT_INTERFACEto set the customized outbound IP and this did work around the issue.To that end, I pulled a fork and pushed a PR with the code change that would allow me specify the source IP I want to use for the connection in the __construct().
The PR is here: #326
The changes are 100% backward compatible.
I'm not sure when (or if) my PR will be merged, so to any future readers needing this functionality, you can feel free to use my fork instead (I'm not planning on having to maintain it but I will do my best if I have to).
https://github.com/BelniakMedia/mailchimp-api