Codeberg/Community
54
325
Fork
You've already forked Community
12

Can't receive registration activation mails (TrendMicro QIL repuration blocklist issue) #1796

Closed
opened 2025年02月20日 15:51:01 +01:00 by hbbuergerschaft · 8 comments

Comment

Hi there,

we're having trouble signing up with/adding specific e-mail addresses to our account, because we never receive activation link mails. I've seen #328, but we're not using throwaway-addresses.
As a work-around we use'd a private personal address, that we'd like to remove again.

Any ideas? Or are the codeberg mail servers maybe still in some providers'/clearinghouses' blocklists after the spam attack last week?
(We tried to sign-up on the day of the spam attacks, coincidentally.)

Regards

### Comment Hi there, we're having trouble signing up with/adding specific e-mail addresses to our account, because we never receive activation link mails. I've seen #328, but we're not using throwaway-addresses. As a work-around we use'd a private personal address, that we'd like to remove again. Any ideas? Or are the codeberg mail servers maybe still in some providers'/clearinghouses' blocklists after the spam attack last week? (We tried to sign-up on the day of the spam attacks, coincidentally.) Regards

ping @fnetX

ping @fnetX
Owner
Copy link

Did you retry sending an activation code after the day of the attack? As explained on Mastodon we have lost several hours of emails due to an issue in Forgejo queues.

Did you retry sending an activation code after the day of the attack? [As explained on Mastodon](https://social.anoxinon.de/@Codeberg/113998529178075152) we have lost several hours of emails due to an issue in Forgejo queues.

@fnetX We tried a complete new sign-up shortly before I opened the ticket.

@fnetX We tried a complete new sign-up shortly before I opened the ticket.

Also, I tried re-sending activation mails right after posting the last message – did not arrive.

Also, I tried re-sending activation mails right after posting the last message – did not arrive.
Owner
Copy link

There have been successful deliveries to your systems at 2025年02月24日T10:45:27.838000+01:00 (7FB051600AD) and 2025年02月24日T11:35:53.430971+01:00 (EE28F16006A) for the mail address h....y@. Your mail server at mx1.ondataport.de accepted our messages. Please check your server logs or spam folder.

There have been successful deliveries to your systems at 2025年02月24日T10:45:27.838000+01:00 (7FB051600AD) and 2025年02月24日T11:35:53.430971+01:00 (EE28F16006A) for the mail address h....y@. Your mail server at mx1.ondataport.de accepted our messages. Please check your server logs or spam folder.

Thanks for confirming. Antispam quarantine is empty. Will contact our provider.

Thanks for confirming. Antispam quarantine is empty. Will contact our provider.

Hi @fnetX,

Provider says codeberg Mailserver IP is blocklisted due to bad reputation at TrendMicro.

193.26.156.135

Reputation: Bad
List in: Dynamic Reputation Database (QIL)

https://servicecentral.trendmicro.com/en-US/ers/ip-lookup/
(does not work in Firefox for me)

I filed an removal request / appeal here in the role of an end-user (linking to the blog post).

Site said:

193.26.156.135 has been removed from the spam list
Please be aware that this IP address may be blocked again if it sends more spam
Trend Micro limits the number of excepion requests to prevent abuse.

edit: Seems to be removed from the list, indeed.

Maybe you want (削除) to file another appeal in on of the other roles or (削除ここまで) add codeberg to the Global Approved List, if you find the time one day or another.

Thanks a lot!

Regards

Hi @fnetX, Provider says codeberg Mailserver IP is blocklisted due to bad reputation at TrendMicro. > 193.26.156.135 > > Reputation: Bad > List in: Dynamic Reputation Database (QIL) > > https://servicecentral.trendmicro.com/en-US/ers/ip-lookup/ (does not work in Firefox for me) I filed an removal request / appeal [here](https://servicecentral.trendmicro.com/en-us/ers/blocked-list-exception/?feedback=QIL&ip=193.26.156.135) in the role of an end-user (linking to the blog post). Site said: > 193.26.156.135 has been removed from the spam list > Please be aware that this IP address may be blocked again if it sends more spam > Trend Micro limits the number of excepion requests to prevent abuse. edit: Seems to be removed from the list, indeed. Maybe you want ~~to file another appeal in on of the other roles or~~ add codeberg to the [Global Approved List](https://servicecentral.trendmicro.com/en-us/ers/global-approved-list/), if you find the time one day or another. Thanks a lot! Regards
hbbuergerschaft changed title from (削除) Can't receive registration activation mails (削除ここまで) to Can't receive registration activation mails (TrendMicro QIL repuration blocklist issue) 2025年02月27日 15:43:35 +01:00
Owner
Copy link

I have submitted the form for the Global Approved List. Let's see.

I have submitted the form for the Global Approved List. Let's see.
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 Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, 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
3 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#1796
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?