wojtek opened 5 months ago
|
||||||||||
Tried but can not get it reproduced. Can you please restart OneDev server and try again to see if the problem still exist? If yes, please let me know your system email address and the other service desk email address that is not working. |
||||||||||
After restarting 1dev pod it seems to work, odd. |
||||||||||
Robin Shen changed state to 'Closed' 5 months ago
|
||||||||||
Closing. Feel free to reopen if this occurs again. |
||||||||||
wojtek changed state to 'Open' 5 months ago
|
||||||||||
As long as you mention somebody, they will be authorized to access the confidential issue automatically. So @kobit and @andrzej can now access the issue. Can you please help to set up a test OneDev system from scratch, and reproduce the issue and let me know the procedure? |
||||||||||
Robin Shen changed state to 'Closed' 4 months ago
|
||||||||||
Please reopen this if you have more info |
||||||||||
andrzej changed state to 'Open' 4 months ago
|
||||||||||
I'm not sure if that is exactly what is causing the issue, but this issue repeats (so it is reproducible), in our case when sender of the message has the same email as the recipient of the message. In this case, I think, that if the same email appears twice (or more) and user for this email doesn't exist in the OneDev database, then application tries to create it as many times as many times it appears in TO/FROM/CC email headers. Could you check if that is a possible cause of this issue? and maybe add some workaround in this case? as it may happen that somehow same email address will end up in the TO as it was in FROM email header. As for CC, I'm not sure if those are processed by 1dev, but if so, the I would suggest adding the same workaround there. |
||||||||||
Robin Shen changed fields 4 months ago
|
||||||||||
@andrzej thanks for the info. I do get the bug reproduced. |
||||||||||
Robin Shen changed confidential 4 months ago
|
||||||||||
I removed all sensitive info in this issue, and made the issue public so that it can appear in public release notes of next version. |
||||||||||
OneDev changed state to 'Closed' 4 months ago
|
||||||||||
State changed as code fixing the issue is committed (f155c82e) |
||||||||||
Referenced from commit 4 months ago
|
||||||||||
OneDev changed state to 'Released' 4 months ago
|
||||||||||
State changed as build #4468 is successful |
||||||||||
@wojtek the option |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
<=9.4.6
|
Labels |
No labels
|
We disabled "only monitor system address" option from https://code.onedev.io/onedev/server/~issues/1616#IssueComment-5968 but mails to different addresses yield this error (we use 9.2.4):