What is the "to" address for these reply emails?

The to is to itself. So both from and to are "support@...". However, I do get emails to another email (but I'm assuming that's just watcher stuff).

Perhaps there is a way to say "hey, don't create tickets from" and put in "support@...", or something like that?

When send issue notification email, OneDev will specify reply-to address as support+issue~<issue id>@..., for instance you may hit reply of this notifation email, the reply address should be [email protected]. With the special plus addressing, OneDev knows to append the mail content as comment to existing issue, instead of creating a new issue.

So it seems odd that the reply address is still support@... at your side. Maybe your mail server does not support plus addressing?

Do you mean for a particular repo, OneDev sending issue notification using reply address directly as support@... without subaddressing?

Also I suggest to upgrade to latest version to see if it makes any difference.

Yes, there is no sub-addressing in the emails, with both To and From fields being support@... This endlessly creates a new ticket to the email that comes in saying a ticket has been created. I use support@... as a catchall (just in case a client forgets).

Using the sub-addressing properly, within the different repo's and from other emails (so not Support emailing itself), works as intended.

This is quite odd. If you can reproduce the issue with a sample database, it will be of a lot help.

I've been able to replicate it again. What data do you need?

All you need to do is send an email to the service desk (in this case support@...) from the service desk email support@.... OneDev sends emails out as support@....

You can also send an email from support@... to a project (support+project-name@...) and it will create a ticket there, but then will continue to create tickets as "catch all's" if you have that set up. In my case, anyone who just sends emails to support@... goes to the "Client" parent project.

I am happy to get an export of the database, is that helps.

Also, this is the current settings (the exclude does not work). https://i.imgur.com/TqY5L0U.png

Got this reproduced. Will be fixed in next patch release. Thx!

State changed as code fixing the issue is committed

State changed as build #3105 is successful