Codeberg/Community
62
386
Fork
You've already forked Community
12

Confirmation email not received #2807

Open
opened 2026年06月25日 16:13:44 +02:00 by Cyberbeni · 1 comment

Comment

I have this personal account with the email address cyberbeni@gmail.com and I wanted to create an account specifically for my company device, so that it has access to the private repository where I store my dotfiles and nothing else. I used the email address cyberbeni+codeberg_company_devices@gmail.com during registration but I never got the confirmation email, even after trying to resend it. (Manually sending an email to this address works as expected)

### Comment I have this personal account with the email address `cyberbeni@gmail.com` and I wanted to create an account specifically for my company device, so that it has access to the private repository where I store my dotfiles and nothing else. I used the email address `cyberbeni+codeberg_company_devices@gmail.com` during registration but I never got the confirmation email, even after trying to resend it. (Manually sending an email to this address works as expected)

Email confirmation issues can be frustrating, especially when everything else appears to be working normally. One thing that sometimes gets overlooked is whether the service has any restrictions or filtering around "+" email aliases. If the registration system accepted the address but no confirmation message arrived after multiple attempts, there could be a delivery problem somewhere between the platform and Gmail.

On a related note, I recently read an article about handling urgent situations where timing really matters, and it reminded me how important clear communication is when services rely on email notifications. The guide at same day dentist phoenix discusses responding quickly to dental emergencies and highlights how delays can make a situation more stressful. Different topic, but the same principle applies here fast follow-up and reliable communication can make all the difference.

Hopefully the maintainers can check the mail logs and confirm whether the messages were actually sent.

Email confirmation issues can be frustrating, especially when everything else appears to be working normally. One thing that sometimes gets overlooked is whether the service has any restrictions or filtering around "+" email aliases. If the registration system accepted the address but no confirmation message arrived after multiple attempts, there could be a delivery problem somewhere between the platform and Gmail. On a related note, I recently read an article about handling urgent situations where timing really matters, and it reminded me how important clear communication is when services rely on email notifications. The guide at [same day dentist phoenix](https://phoenixarizonadentistry.com/emergency-dentist/) discusses responding quickly to dental emergencies and highlights how delays can make a situation more stressful. Different topic, but the same principle applies here fast follow-up and reliable communication can make all the difference. Hopefully the maintainers can check the mail logs and confirm whether the messages were actually sent.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2807
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?