[resolved] Email Loop

andrewgem

Our incoming email address is support@xxxxx.com. For some reason a select number of notification emails (ticket assignment etc.) are being sent to that address which is triggering the email loop warning.I have looked through the DB and can't find support@ anywhere else, but it's still making a loop.Can anyone suggest where I can start looking at this? Thanks.

blueyeguy

Please help us to help you by reading and following the posting guidelines located in this thread: Please read before requesting assistance. The more information you give us the better we will be able to assist you. Thank you.osTicket Version? Make sure you don't have your incoming email address listed for any of your agents.

ntozier

My guess is that you have an alias or account Ccing to a mailing list. I would check your mail server.

andrewgem

Blueyeguy:Sorry, I thought as I was posting in the 1.10 that'd be enough, but more specifically

v1.10.1 (9ae093d) running on IIS on Windows 2012R2.I've checked all agent email accounts, there's no CCing or auto-replying going on anywhere.Is there any more detail I can put into the logs to track this down?Looking through the code, I'm seeing that the email variable is not being set, the sprintf says:"sprintf( _S('It appears as though <%s> is being used as a forwarded or fetched email account and is also being used as a user / system account. Please correct the loop or seek technical assistance.'), $mailinfo)"But the log message shows "It appears as though is being used as a forwarded or fetched email

account and is also being used as a user / system account. Please

correct the loop or seek technical assistance. "So $mailinfo is not being populated.

andrewgem

More info:In the $info arrray the $info is always coming back as the same value, regardless of the message.

andrewgem

UPDATE:I've found the cause of the problem. There was a filter rule on Gmail which was moving emails from Sent to Inbox for some unknown reason (I shall have words with the person responsible tomorrow).Thanks for your help on this. Case closed!

ntozier

Glad to hear that you got this sorted. I'll mark this as resolved and close the thread.