I try with and without expunge of the incoming email using incoming_email_expunge_deleted parameter but the problem is still here.
It’s quiet annoying because it works (create issue and sending acknowledge email) … but it does not fully work (sending an error notification email). So today I can not use it in production.
If it is something relevant, gitlab is installed using omnibus. I have not change the configuration for a long time (since version 12 of gitlab), just adding the service desk now.
I have another server for testing, with a fresh install of the same gitlab version, with the same configuration and everything is working fine with this one.
My testing server wasn’t exactly using the smae configuration as the production : no HTTPS and no proxy.
Now I have set up the proxy and HTTPS, and I can reproduce the same error. I will try removing HTTPS than proxy to figure if it is one of those that could trigger the error.
All right I found it, and it has nothing to deal with gitlab config.
There were 2 gitlab servers accepting service desk email from the same mailbox. So one say “ok I create issue and notify all is fine” and the other “What is that project ? Send error notification”.
Hmm yeah might want to use separate mailboxes for multiple Gitlab instances so that it doesn’t get confused what email belongs where. Glad it’s solved though. Sorry couldn’t help much.
@iwalker
I have a similar issue but mine is solely the rejection mail I get. And this happens for just internal users, our external users are able to send in mails and it gets registered on Service Desk.
I would appreciate some insight.