Overview

You might be getting a lot of emails and as such a lot of new cases created  with the content:

Your message to person@company.com couldn't be delivered. Person wasn't found at company.com

where person@company.com is the email you set for one of your virtual users used for creating cases with API or other automation, but the email address is not a valid email address.

 

---

Information

 

Root Cause

If this virtual user has notifications turned on, FogBugz will try to send notifications to this email address.

If the email address is not found by the email server, it will reply with the "couldn't be delivered" message mentioned in the Overview, notifying the sender (FogBugz) that the email address is not valid. Since the server will use a different sender address (not person@company.com), the message will result in a new case being created.

 

---

Solution

You have the following options:

• disable notifications for this virtual user (recommended)
• use a valid email address for your virtual user

 

Back to the top

---

Testing

Disabling notifications for the virtual user will stop sending notifications by FogBugz, and as such will stop the "couldn't be delivered" replies from the email server, and the related case creation.

 

Back to the top