conduct@gitea.com: User not found #12437

Closed
opened 2025-11-02 10:09:48 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @oliverpool on GitHub (Feb 5, 2024).

Description

Following the Gitea Community Code of Conduct (introduced in #23188) I sent an email to conduct@gitea.com.

I received an Undelivered Mail Returned to Sender reply stating:

<conduct@gitea.com>: host m1.feishu.cn[54.221.254.138] said: 550 verify address
    failed, User not found conduct@gitea.com (in reply to RCPT TO command)

What is the correct e-mail address to contact the Gitea Project Stewards regarding the Code of Conduct?

Gitea Version

main

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Database

None

Originally created by @oliverpool on GitHub (Feb 5, 2024). ### Description Following the [Gitea Community Code of Conduct](https://github.com/go-gitea/gitea/blob/0d136df3f0b3920d34ce850499e1346fbff29e30/CODE_OF_CONDUCT.md) (introduced in #23188) I sent an email to conduct@gitea.com. I received an `Undelivered Mail Returned to Sender` reply stating: ``` <conduct@gitea.com>: host m1.feishu.cn[54.221.254.138] said: 550 verify address failed, User not found conduct@gitea.com (in reply to RCPT TO command) ``` What is the correct e-mail address to contact the Gitea Project Stewards regarding the Code of Conduct? ### Gitea Version main ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? - ### Database None
GiteaMirror added the type/bug label 2025-11-02 10:09:48 -06:00
Author
Owner

@techknowlogick commented on GitHub (Feb 5, 2024):

Thank you for your report. I will open a ticket with our email provider to investigate. In the mean time, please feel free to email me at my username @gitea.com and I'll be able to bring it to the rest of the TOC.

In case anyone comes across this thread in the future, please send reports to the appropriate email address, this is just a one off situation. If there are issues with the email in the future please create an issue

@techknowlogick commented on GitHub (Feb 5, 2024): Thank you for your report. I will open a ticket with our email provider to investigate. In the mean time, please feel free to email me at my username @gitea.com and I'll be able to bring it to the rest of the TOC. In case anyone comes across this thread in the future, please send reports to the appropriate email address, this is just a one off situation. If there are issues with the email in the future please create an issue
Author
Owner

@techknowlogick commented on GitHub (Feb 7, 2024):

Closing as the ticket has been resolved with the email provider. The above mentioned report is in review with the TOC, but that is managed separately from this issue.

@techknowlogick commented on GitHub (Feb 7, 2024): Closing as the ticket has been resolved with the email provider. The above mentioned report is in review with the TOC, but that is managed separately from this issue.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 28, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 28, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12437