Caught in an edless loop of verification emils

[Matthew Doering]

We have a service email account that customers use to submit ticket requests.  A customer recently did this and now we are getting flooded with Account Verification emails to the service account from Atlassian.  How to stop this and why did it happen.

[John Funk]

Hi Matthew - Have you verified the account? What do the emails look like? 

[Matthew Doering]

A bit of a catch 22.  The account was a service alias (all emails to that address are forwarded to Jira and to 2 other internal accounts on our support team) so there is no real email account to verify.  When we tried to verify the email jira wanted us to log in with that account but that can't be done.

So jira sent a reminder email ("DSM-391 [Action required] Veryify your email to finish signing up ....":).  

Since the verification email was sent to the service account (alias) it was also forwarded to Service Management and then open a new ticket, which kicked off the need to verify the account etc.

I stopped the cycle (after 400 or so tickets opened) by disabling the account in Jira.  But the fundamental issue remains.

[Matthew Doering]

To clarify not only are we getting emails but each email, since it is sent to the service address, generates a new service ticket.  100s so far.