Github dislikes email “aliases” so much that they will shadow ban your otherwise normal activities for months, and once flagged, support will request not only a “valid” email domain but also that you remove the “alias” email from the account completely.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.97K Posts
- 74.6K Comments
- Modlog
Exactly it’s a completely false distinction. All email addresses are an “alias”.
Not true, there is a distinction between your reply address and any secondary addresses you have configured on the mailbox. Still, as far as I know that’s not something they should be able to see from outside your email server. You are setting up aliases on your own server right, not using some third party as an intermediary? Using a third party intermediary would possibly be something they can see from the delivery routing.
It’s most likely that this is just them shitting on you for using an “untrusted” provider. Most big sites and email providers are really getting stingy lately with who they’ll accept email from and what is accepted as a valid email domain. There’s also a big push for properly configured SPF and DKIM records that aren’t set to allow spoofing sender domain. It’s combining to cause a lot of issues for self hosters lately, and also for companies that have vendors who insist on sending email from the vendor’s servers but appearing as from the company itself.