Github vs. Email Aliases
Github vs. Email Aliases
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're viewing a single thread.
What do you mean by email aliases?
Basically another email address that forwards everything to your main email.
So a redirect instead of alias? E-mail alias is the address+alias@... thing.
Yeah let's say you got [email protected], on simplelogin you can make a [email protected] and now sign up for services using aleeas with those emails being forwarded to your protonmail
Here's an illustration
What was this feature called again... basically linking, right?
It's called an email alias: https://en.wikipedia.org/wiki/Email_alias
I thought that was a gmail specific thing.
It is, an email alias is a redirect. They've just been calling plus codes aliases and didn't know they were mixed up.
Thats an extension
How would they even detect that? Blacklist common alias providers?
I dont think so. I get my self hosted aliases banned. They must read the dkim/spf/dmarc or other types of headers against a base of mainstream email providers
Wouldn't that ban self hosted email period?
Depends on what header they read and how
I guess so
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.
