'Recipient "" has too many recent signup requests' error

[EmilyNL]

Anyone know how to fix this?

Thanks.

[marckrejci]

I'm getting this too... :(

[vierkantemeter]

Did you ever find a solution or a cause for this problem? I'm getting it too.

[kraftbj]

My guess would be that the e-mail form field value is incorrect or something to that effect.

[daveschappell]

I just had the same error. It was only happening on iPhones. I double-checked that I had the correct info in the Form field. I thought that I was able to fix the error by disabling the 'Recaptcha' option on the Mailchimp signup-form-page. After I did that, it worked for me -- but then a friend tried it again (the same guy who found the error initially) and it didn't work for him. Help!

[vierkantemeter]

After some investigation we've tracked down the issue is not at Mailchimp's side, but some code in the form that makes iOS10 iPhones show the 'Recipient "" has too many recent signup requests' error.

We're almost there, but as we don't have a iOS10 device to test with (we asked friends) so it's hard to test for us.

We came to the conclusion that:

• This form triggers the error on iOS10 devices: http://van-vlerken.nl/form-en/form3en.html

• This form works good, and doesn't triggers the error: http://van-vlerken.nl/form-en/form4en.html

So, some HTML code in the first form triggers the error. But we're unable to test any further. Can someone else test this, and maybe alter the HTML code to see what exactly triggers the error?

_(Note; the form mentioned above only does a post to the result page which shows a print_r($_POST). No information is send to me, mailchimp or anyone else.)_

(Note 2: The iPhone emulator at https://appetize.io/demo won't trigger the error at all, so that emulator is unfortunately unusable in this case)

I've also posted this issue on stackoverflow: http://stackoverflow.com/questions/40914117/mailchimp-embed-form-too-many-recent-signup-requests-on-ios-10-devices

[kraftbj]

Thanks for the links. I'll see if I can duplicate the error in iOS 10 and go backwards from there. I'll let you know if I find anything.

[deinBaum]

I had this problem (on our website build with webflow) for some weeks now, but not only on iPhones, on Desktop Safari & Chrome too.

I checked your other post on stackoverflow and tried to add "http:" before the "//". I can't believe it's that easy, but this works for me!

[JohnCrch]

Was having this issue in a local test environment using the FireFox browser. I added EMAIL in the E-Mail Field just under the Form Action and it seems to be working...

[daveschappell]

Brandon -- are John & deinBaum's recommendations the final fix? or are you still researching?

[vierkantemeter]

We've finally found the fix. Remove target="_blank" from the form tag.

[thehungryhutch]

I've removed target="_blank" from the php file, but I'm still getting this error.

class-bjgk-genesis-enews-extended.txt

[paulmaunders]

We have also been getting the 'recipient has too many recent signup requests' error using MailChimp's widget on a completely different project.

I read a few posts about it here, here and here as well as this github thread and as a result I tried:

1. Removing the anti-bot hidden div
2. Updating the action url to be specifically https:// instead of just //
3. Disabling the re-captcha option in MailChimp
4. Removing target=_blank from the form tag.
5. Removing novalidate from the form tag, and adding required to the input tag

Steps 4 or 5 both seemed to fix it for me, but 5 displayed the submission page slightly better.

[JamieRohrbaugh]

I am having the same issue with eNews Extended and MailChimp on 3 different sites. I'm trying to fix it per the instructions above, but am not sure where to find the form tag (in order to make the changes recommended above) since the form action is the only thing in eNews Extended. Help? Thanks!

[digitalmaster]

@paulmaunders I think step #2 worked for me.. Thanks champ 👍

[kraftbj]

I haven't heard of any new issues with this, so I'm going to presume an iOS update helped? I'm going to close it for now, but if y'all are still seeing issues, please comment.

[zschuessler]

I was getting this error when the email field was disabled. Removing the disabled attribute allowed the form to work again.

This issue is a top hit in Google, hopefully it helps someone else!

[mrcoles]

I also got this error when my form was using "email" instead of the expected uppercase format of "EMAIL".