SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-16 05:01:57 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Netbird treats my many-user custom email domain as an org? Cannot invite other users? #199

New Issue
Open
opened 2025-11-20 05:07:47 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:07:47 -05:00
Owner
Copy Link

Originally created by @endigma on GitHub (Oct 7, 2022).

I own and operate mailcat.ca and several other email domains, netbird treats them as "private organization domains" and groups all signups under them together? I also don't think I'm able to invite users at all and the system entirely relies on domain sharing?

  1. My domain is not an org and assuming it is because not (google, gmail, etc) seems nonsensical? This should at least be a setting someone who owns the domain can opt-in to.
  2. Is it at all possible to invite users without using this functionality?
Originally created by @endigma on GitHub (Oct 7, 2022). I own and operate `mailcat.ca` and several other email domains, netbird treats them as "private organization domains" and groups all signups under them together? I also don't think I'm able to invite users at all and the system entirely relies on domain sharing? 1. My domain is *not* an org and assuming it is because not (google, gmail, etc) seems nonsensical? This should at least be a setting someone who owns the domain can *opt-in* to. 2. Is it at all possible to invite users without using this functionality?
saavagebueno added the feature-requestconfig-idp labels 2025-11-20 05:07:47 -05:00
saavagebueno commented 2025-11-20 05:07:48 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 8, 2022):

Hello @endigma our apologies regarding our classification system. Unfortunately the system didn't classified your domain correctly. We verify if the domain doesn't offer a public webmail, not only if they are gmail.com or other famous service, we also try to identify a few cases with public paid inbox (assuming this is your case) and some disposable email.

Can you tell us a bit more about your domain mailcat.ca?

We are working on a better experience and prevent any unwanted grouping with a 2 steps requests for some domains with lower classification scores.

The option to send invites will also be release soon.

In the mean time, I've checked your account and sent your an email asking you to revoke any existing setup key.

@mlsmaycon commented on GitHub (Oct 8, 2022): Hello @endigma our apologies regarding our classification system. Unfortunately the system didn't classified your domain correctly. We verify if the domain doesn't offer a public webmail, not only if they are gmail.com or other famous service, we also try to identify a few cases with public paid inbox (assuming this is your case) and some disposable email. Can you tell us a bit more about your domain `mailcat.ca`? We are working on a better experience and prevent any unwanted grouping with a 2 steps requests for some domains with lower classification scores. The option to send invites will also be release soon. In the mean time, I've checked your account and sent your an email asking you to revoke any existing setup key.
saavagebueno commented 2025-11-20 05:07:48 -05:00
Author
Owner
Copy Link

@endigma commented on GitHub (Oct 8, 2022):

Perhaps this could be configured by the domain owner?

I'm not sure what process you could use to determine the presence of public webmail, not all domains are co-located with their own webmail panel.

Attempting to automatically handle this via email domain heuristics at all is going to be inherently insurmountably insecure, I suppose you checked all the fastmail.com available domains, all the cock.li domains, all the email forwarding domains, all the private email domain services, all the protonmail domains, all the anonymous email providers on the entire internet?

You could do all the magic in the world and you'd never be able to ascertain from existing records or web scraping if the owner of an email domain definitively wants their domain to be treated as an org on your service.

I say the above as an email domain admin, and the below as an engineer.

You should look into using TXT or another record type to move control of this functionality to the domain owner explicitly. If you don't have the settings pages to control this in-app it should be pretty easy to work a DNS lookup into whatever code makes this happen.

@endigma commented on GitHub (Oct 8, 2022): Perhaps this could be configured by the domain owner? I'm not sure what process you could use to determine the presence of public webmail, not all domains are co-located with their own webmail panel. Attempting to automatically handle this via email domain heuristics at all is going to be inherently insurmountably insecure, I suppose you checked all the fastmail.com available domains, all the cock.li domains, all the email forwarding domains, all the private email domain services, all the protonmail domains, all the anonymous email providers on the entire internet? You could do all the magic in the world and you'd never be able to ascertain from existing records or web scraping if the owner of an email domain definitively wants their domain to be treated as an org on your service. I say the above as an email domain admin, and the below as an engineer. You should look into using TXT or another record type to move control of this functionality to the domain owner explicitly. If you don't have the settings pages to control this in-app it should be pretty easy to work a DNS lookup into whatever code makes this happen.
saavagebueno commented 2025-11-20 05:07:48 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 8, 2022):

thanks @endigma for the suggestion, we will discuss it for the improvements moving forward as well because it can make the experience more seamless after validation.

@mlsmaycon commented on GitHub (Oct 8, 2022): thanks @endigma for the suggestion, we will discuss it for the improvements moving forward as well because it can make the experience more seamless after validation.
saavagebueno commented 2025-11-20 05:07:48 -05:00
Author
Owner
Copy Link

@timwsuqld commented on GitHub (Oct 18, 2022):

The way this works in most systems is you need a TXT record to verify ownership of the domain, before any "org domain" features are active. If we default to all domains being "shared domains" and then have a TXT record to verify ownership, this would be the safest way. This should be treated as a security issue.

@timwsuqld commented on GitHub (Oct 18, 2022): The way this works in most systems is you need a TXT record to verify ownership of the domain, before any "org domain" features are active. If we default to all domains being "shared domains" and then have a TXT record to verify ownership, this would be the safest way. This should be treated as a security issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label config-idp feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#199
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?