It is possible that a recipient received and processed by the system may not
have a name set. In that case, the email mailbox should be used. As a
failsafe, avoid crashing if the User::save() should fail.

This is a slight edit over the previous implementation of the same feature.
Previously, an "account" was required, which implies a user account with a
password. This implementation simply requires a user record. Importing of
users by organization domain is still supported -- even if the user does not
yet exist.

  * Auto confirm remote accounts
  * Don't send out emails for remote account activation
  * Forbid password changes on remote accounts

Previously we required an account to associate a user to an organization.

Show user status on the user listing table

Useful if the staff members administratively configure a static password
that the user should never change.

Add CLI import/export support for organizations

Conflicts:

	include/class.user.php

Implement CLI user import/export in a well formatted CSV file. Name and
email address are the only supported fields at the moment.

Add routine to get ticket's recipients (owner + active collaborators)

And define getInitials() function for %{ticket.name.initials}

Replace phone number on ticket owner update

Change fromForm routine takes the actual form and do validation and call
fromVars with clean data

Add fromVars to do the actual user creation (previously named fromForm.

Unpack user data for filtering purposes for staff created tickets

Add update routine
Add updated date getter