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

Sending activation codes via live.com causes issues. #191

Closed
opened 2020年06月13日 08:12:44 +02:00 by BoilingOil · 7 comments

Ok, I wanted to open an issue on one of the projects hosted here, so I needed an account.
Everything set up, and I'm asked to activate by clicking a link in an email I'm about to receive. So far, so good.
I go to my gmail account, nothing... (I have gmail.com as my main account, but for all my registrations, I use a live.com account, which I've configured my gamil reader to process.)
So I log into live.com, and there it is, mail from codeberg in the spam box!
I click "Not Spam" and it moves to my inbox.

I go to the inbox and click the link... and was sent to some "Bad Request" page on outlook.live.com itself. Apparently, your activation codes are toxic when clicked in Firefox on a live.com page.

Today, I tried again, but the code had expired. So I asked for a new one. Again, it ends up being called spam. Again I tapped "Not Spam" and clicked the link... again, same problem.
Now I waited for the mail to be sent thru to gmail, and clicked it there. Seeing as how I'm writing this, THAT apparently worked.

But maybe you could still look into that "Bad Request" thing at live.com, because something there might keep some people out of here, if they're not as persistent nasty buggers as I am.

Ok, I wanted to open an issue on one of the projects hosted here, so I needed an account. Everything set up, and I'm asked to activate by clicking a link in an email I'm about to receive. So far, so good. I go to my gmail account, nothing... (I have gmail.com as my main account, but for all my registrations, I use a live.com account, which I've configured my gamil reader to process.) So I log into live.com, and there it is, mail from codeberg in the spam box! I click "Not Spam" and it moves to my inbox. I go to the inbox and click the link... and was sent to some "Bad Request" page on outlook.live.com itself. Apparently, your activation codes are toxic when clicked in Firefox on a live.com page. Today, I tried again, but the code had expired. So I asked for a new one. Again, it ends up being called spam. Again I tapped "Not Spam" and clicked the link... again, same problem. Now I waited for the mail to be sent thru to gmail, and clicked it there. Seeing as how I'm writing this, THAT apparently worked. But maybe you could still look into that "Bad Request" thing at live.com, because something there might keep some people out of here, if they're not as persistent nasty buggers as I am.

I mean, if nothing could be done about the above code-wise, it might be an idea to detect when people are trying to use a MocriSoft/Outlook based address, and then encourage them to change it, INCLUDING a warning that completing the registration following a link from those accounts will be al but impossible.

I mean, if nothing could be done about the above code-wise, it might be an idea to detect when people are trying to use a MocriSoft/Outlook based address, and then encourage them to change it, INCLUDING a warning that completing the registration following a link from those accounts will be al but impossible.

could be related to #298

could be related to #298
Member
Copy link

This is definitely not intentional, solving the issue that activation mails are marked as spam would be important here.

This is definitely not intentional, solving the issue that activation mails are marked as spam would be important here.

This is definitely not intentional, solving the issue that activation mails are marked as spam would be important here.

Of course this is not intentional. I would never imply, or even just imagine, that it was. Because what would be the purpose of doing such a thing intentionally? Besides, I was not the one who first made the link between #298 and this issue. I only responded to someone else doing that. In fact, I'm the one who questions that link...

> This is definitely not intentional, solving the issue that activation mails are marked as spam would be important here. Of course this is not intentional. I would never imply, or even just imagine, that it was. Because what would be the purpose of doing such a thing intentionally? Besides, *I* was not the one who first made the link between #298 and this issue. I only responded to someone else doing that. In fact, I'm the one who *questions* that link...

I'm sorry if any of you got this wrong - i just thought the live.com issue could be caused by some temporary bad reputation due to spam atacs.

I'm sorry if any of you got this wrong - i just thought the live.com issue could be caused by some temporary bad reputation due to spam atacs.
Member
Copy link

I had the same understanding like you

I had the same understanding like you
Owner
Copy link

Monitoring spam reputation is some permanent and repeated job, I think we do not need to keep an issue to track this. We are having an eye on this of course.

Monitoring spam reputation is some permanent and repeated job, I think we do not need to keep an issue to track this. We are having an eye on this of course.
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
4 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#191
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?