An organization sent a poorly constructed email just before 8:00 AM ET on Tue, Oct 2, with over 2,000 email addresses in the CC field. The header of the email was too long to process as expected, creating a unique situation that contributed to a large amount of resource utilization.

Once the team identified the email message, custom handling for this poorly formed email was built. This allowed the message to be processed as expected without increasing resources. Future incidents with poorly constructed emails that exceed typical header data will be handled gracefully.