These are ‘test addresses’ you can use during the test or development phase for your project. They will not be counted against any quotas or limits that may be added to the system. (As of this writing, there aren’t any).


You need to click the ‘Allow Test Addresses’ setting in the Admin panel for these addresses to work. Other, non-test addresses will continue to work normally, and any billing or limits or costs on those addresses will work as normal. This setting is not recommended for Production!


BASIC TESTS

These always return the same thing, no matter what.


AddressValue
[email protected]always GOOD, no matter how often called
[email protected]always BAD, no matter how often called
[email protected]always CHALLENGE
[email protected]always returns an error, simulates an ‘internal error’ on our end (will actually return HTTP Status code 500!)

DETAILED TESTS

These will return different values based on form configuration, and the health of the IP you are submitting from:


AddressValue
[email protected]The default treatment for ‘valid’ addresses (almost always ‘GOOD’)
[email protected]however your form handles ‘invalid’ addresses (always ‘BAD’)
[email protected]The default treatment for ‘Unknown’ addresses
[email protected]The default treatment for ‘Catch-all’ addresses

SPECIAL DELAY TEST:

This is good for testing how you will handle a slow response from our server:


AddressValue
slow-{mode}-{n}@test.goodforms.comwait ‘n’ seconds before returning ‘mode’ (for the above modes)

e.g. [email protected] would wait 15 seconds before returning a ‘good’ result (based on your form settings and number of submissions, etc.)


CERTIFICATION TESTS:

AddressValue
[email protected]A ‘GOOD’ verification, but when you submit it, and you try to certify it, it will act like you’re out of credits
[email protected]A seemingly ‘GOOD’ verification, but it will fail certification

UNIQUENESS CHECKS:

You can use a google-style +something extension to guarantee uniqueness - e.g. -
[email protected] - will always be GOOD