Easylink: Would like to have our account to the test environment be able to create jobs as if in production but do not want any emails sent out. Is there a setting I can change in the portal or does Easylink need to do it. Thanks.
One approach that might work for this requirement is for us to insert a block for a particular destination address, and for you to use that address in your test messages.
All deliveries to that address would be blocked, but you would still be able to submit your jobs and see them process in the test system.
Would this approach be acceptable?
We're pulling lists from a pool of recipients (20 million) based upon user's input on our client's website. Part of their UAT is reviewing the list. The client manages the data so the test environment has real email addresses. I do see where you suggest keeping job size to 20 recipients so we can't do a full production test as our application will need to have a "test mode" to limit job size. My request stems from an incident we had last July, were the application went into an infinite loop and before it was killed it had sent a total of 3 million emails ($$$$) to the same 15K recipients. This can't happen again, especially coming from a test environment. Alot of anxiety. They changed our account to where we could create but not execute jobs until things were corrected. May just create a mock Easylink service that dumps lists to a folder where they can review instead of the portal. We're not using much of the API so have to see what it would take to do that. Is there a Mock EasyLink service out there?
We don't have a separate test mode for the service that would do this generically, but we could configure your account on the test system so that it would not deliver any live traffic - all traffic would be automatically cancelled. That would allow you to verify the list contents. If you wanted to specify a couple "live" addresses that could be used to allow for real delivery, that would be possible as well.
Would that work?
The cancelling would be perfect. No need for live traffic. Autocancel every job after creation would work perfectly.
Please provide your test system user ID so this config can be added to it.
We will put this in place for you early next week.
And now 5 months later I'm ready to send the tests through. I had sent my information "pt/conclusive" via email back then. I went to create a manual email job and send it. My expectation would be that the job would be cancelled. It isn't canceled but looks to be stuck in the delivering status as I haven't received an email. This scares me as it looks that it could possibly be sent. I'll be sending a test through the API this afternoon of test data to confirm the API jobs are being canceled and not going out. Can you confirm jobs will be canceled. Thanks.
I've looked at your account, and it does not appear that the special routing was done for your account.
To make matters more complicated, we are in the process of migrating our API test traffic from the current system and URL to a different test system.
Rather than make the routing changes for you more than once, it probably makes more sense for you to get an account on the new test system and then we can make the changes there.
Have you been working with a sales account team or sales engineer who could arrange to have your account migrated over to the other test system?
I haven't. I'll have our business contact call and discuss.
Spoke w/ easylink rep, she wasn't sure what to do so she was supposed to call back w/ a tech person. She didn't so we'll follow up tomorrow.
Based on my emails with tech support, you should be good to go.
Your test system credentials should have been provided to you, and the special configuration to suppress deliveries has been added. If you need to add some exception addresses that will actually deliver, let us know and we can configure them.
I suggest trying a small test to make sure the configuration works before firing off your full list.
Please get back to us if you have further questions.
Thank you very much.. will send a sample through. Thanks again.
Ticket 948397 cont. I created several new email jobs. What i'm seeing is different than before. I used to see a fully populated job and see all the recipients (they were all set to blocked). What I'm seeing now is just the job with incorrect settings and no recipient list attached. Has the test environment been changed or are there issues with how the jobs are created? All the jobs are created with the API.
Most likely there are issues with the jobs or with the configuration of your account. Please provide job ID's and we'll take a look.
Example Job Ids
837962, 813480, 829711, 813484, 829743, 829747, 813504, 813500, 829707, 829703
Few examples. Last change to the test environment was related to the expiration days. We were sending 60 and 90 days and the errors we were getting said it was longer than our profile can do.
Any information on this?
Sorry for the delay.
It appears that the thing that caused these jobs to be held out was that they were requested an "enhanced" delivery report:
Thanks for the response. The delivery report type is not configurable on our side and would require a code change. Please go ahead and update our profile to allow for enhanced reporting. Is there a report where I can document the settings for our test and production accounts?
OK, I have made the config change in the test2 system so your jobs will work properly. I retried the jobs that were in error and they are setting up properly.
By the way, the configuration that prevents all deliveries for this account is also preventing delivery of the reports. If you want the reports to be delivered, we should be able to tweak the "non-delivery" configuration to allow mail to go out for specific destination addresses. Let me know if you'd like me to make that config change.
As for your question about the settings in test2 and production, I don't know of a report on that, but customer care should be able to compare them for you and let you know what needs to be synced up.
Just created 2 jobs, 815880, 832107 and 840306. Both jobs I can't see the list or see the send options
815880 is in "Awaiting Setup" status, I'm assuming this hasn't been processed yet.
840306 and 832107 I'm getting error: expiration time is too long for user's profile. The expiration time is 30 days. For this one I'm confused as our expiration time can be up to 90 days. I have asked about this error before and was told our profile would be updated. Like our profile to allow up to 120 days, or even better, I'd like our test profile to match our production profile. Seems the Issues I'm having with testing all relate to the differences between the two profiles.
I have updated this setting and retried the errors - both jobs have now processed.
I do apologize for the back-and-forth on this. Unfortunately I'm not personally aware of how your account was set up in production, so I've been working from the other end trying to make sure your jobs work right.
It might be a good idea for you to contact your account team to see if they can work with customer care to make sure any other required settings are in place in the test system.
Thank you! I'm communicating w/ them now...
