[pgtan]

Ha! I saw a very big multinational F500 company completely reorganize its AD, because users were unable to login to Office 365 with their standard accounts user@<location>.company.com. After weeks of complete disasters the company decided to switch to [e-mail] just for O365.

It's a hard life as microserf.

[millzlane]

Same thing happened at one of the largest employers in the state. They have several entities all with different domains. Now everyone's login is different from their email domain. Even though no matter which domain you use in the To: field, It will still be routed properly.

[throwawayboise]

That makes more sense anyway. Why should your individual identity be hardwired to your current location or department? If you changed jobs within the company you had to get a new email address and login?

[reaperducer]

Why should your individual identity be hardwired to your current location or department?

When you have a workforce the size of IBM it makes sense.

At my last company, with about 300 workers, we had three people with the same first name and last name. Two had the same middle initials.

At my current company, pre-pandemic, even though my department was only 50 people, we still had two with the same first, middle, and last names. They ended up being "1" and "2" in their e-mail addresses.

If your company has a large number of first, second, or third-generation immigrants from Central or South America in it, you run into name collisions all the time.

[syshum]

>At my last company, with about 300 workers, we had three people with the same first name and last name. Two had the same middle initials.

Just assign everyone a salted sha1 hash of their name and employee number as user name and email address

<<evil laugh>>

[banana_giraffe]

A company I worked for did that. Not really for geo-location reasons, but brand ones. People that worked for foobar got a @foobar address, and barfoo people got @barfoo. It was all owned by the same company, but the companies that got bought up kept their brands alive, and this was part of it.

I bounced around divisions, so I kept getting new logins. The old emails would forward to the new ones, but the logins would be sunsetted out as I no longer needed access to old projects. I actually don't know how the backend works, other than every time I need some permissions or something fixed, invariable the IT people get very confused by the mess, whatever it is.

[bellyfullofbac]

My guess would be that's just their login, but their email would not have their location sub-domain (I've never seen a sub-domain in e-mail, well actually not true, people with domain + country TLDs all have it, e.g. [e-mail]).

Of course moving locations/departments would mean getting a new login which is all sorts of problematic.

[bombcar]

Lots of older companies still have subdomains in email, left over from when that was actual machine to route to.

[navanchauhan]

I use pi4.navan.dev for my emails, while I’m getting the rDNS stuff figured out with my ISP.

No reason, but it just signifies that the mail server is hosted on my pi4 at my home, while I host navan.dev on a VPS

[boardwaalk]

There’s no reason to do that, though. You can set your MX record to whatever you want for your domain. Why would you set yourself up to have to change your email? Not to mention advertising that your email is on a raspberry pi. Somebody will probably come along and DDOS that thing just for fun.

[navanchauhan]

I just use that as a disposable email. I know there are better ways, but then with a subdomain, I can just experiment as much as I can.

I would like to believe that I have put the correct measures to prevent a DDOS attack, and it’ll be fun to combat a real time attack honestly