3 ms·

Yeh I agree with that, I recently joined a new company and was a little disappointed that I wasnt asked what email I wanted 'dale@company.com' (dale is usually

Yeh I agree with that, I recently joined a new company and was a little disappointed that I wasnt asked what email I wanted 'dale@company.com' (dale is usually just rare enough that I can get firstnames in these situations) I got dharvey@company.com, and within a few days I realised that every time I needed to email someone I didnt know I never needed to go searching for their email address, I already knew it.

rdl 14y ago
I usually set up "preferred address" (specified by the user, defaulting to firstname), then set up aliases for firstname, lastname, firstname.lastname, firstnamelastname, flastname, firstl. The thing which annoys me is when I have firstname on a major public service, and other people have weird derivatives (like first1@ or firstl), and I get misdirected mail. On google I have firstname.lastname and an annoying realtor(tm) has firstname.b.lastname@ and I get huge amounts of useless mail.
javajosh 14y ago
I wonder why corporate email systems aren't smart enough to take reasonable action. The first time I try to send a message to 'dale' the system should be able to infer the recipient from context. With a good naming convention to avoid false positives (forcing subsquent dales to add a distinguishing letter) this system would be very reliable.
- flomo 14y ago
  Unfortunately, I've been singed when Gmail decided 'dale' actually meant 'daboss@client.com'. So, please no second-guessing in email addressing. With good directory typeahead (I won't mention the system because its blue and yellow and smells), it's not really a problem.
bostonvaulter2 14y ago
This is solved at my company because we use Google Apps and everyone in the company is auto-completed when typing an email (based on their full-name). Of course we also mostly do a first letter of first name followed by last name as well.

rdl 14y ago

I usually set up "preferred address" (specified by the user, defaulting to firstname), then set up aliases for firstname, lastname, firstname.lastname, firstnamelastname, flastname, firstl. The thing which annoys me is when I have firstname on a major public service, and other people have weird derivatives (like first1@ or firstl), and I get misdirected mail. On google I have firstname.lastname and an annoying realtor(tm) has firstname.b.lastname@ and I get huge amounts of useless mail.

javajosh 14y ago

I wonder why corporate email systems aren't smart enough to take reasonable action. The first time I try to send a message to 'dale' the system should be able to infer the recipient from context. With a good naming convention to avoid false positives (forcing subsquent dales to add a distinguishing letter) this system would be very reliable.

flomo 14y ago
Unfortunately, I've been singed when Gmail decided 'dale' actually meant 'daboss@client.com'. So, please no second-guessing in email addressing. With good directory typeahead (I won't mention the system because its blue and yellow and smells), it's not really a problem.

bostonvaulter2 14y ago

This is solved at my company because we use Google Apps and everyone in the company is auto-completed when typing an email (based on their full-name). Of course we also mostly do a first letter of first name followed by last name as well.