Place the message-id in the body of the email

Reviewed-By: Peter Rotich <peter@osticket.com>

email: Fix incorrect matching of user ids

Reviewed-By: Peter Rotich <peter@osticket.com>

If an email loop is detected, in addition to dropping the message, also log
an error to the system log, but do not send an email to the administrator in
the event that it is the administrator's email that is looped.

Outbound message-ids are predictable, with a consistent code unique and
static to each osTicket installation. This will help detect email loops
where message is delivered back to the system in an email loop.

pwreset: Fixup password reset system

Reviewed-By: Peter Rotich <peter@osticket.com>

Turns out that the new authentication system incorrectly cancels the reset
tokens when it processes logins rather than after the user successfully
resets his/her password

Fix department's auto response email

Reviewed-By: Jared Hancock <jared@osticket.com>

Decide if we need to keep the just selected SLA on ticket edit

Reviewed-By: Jared Hancock <jared@osticket.com>

Issue/pwreset again

Reviewed-By: Peter Rotich <peter@osticket.com>

If a client is already logged into the system and follows a second ticket
link, show the ticket instead of the list of tickets.

Fix several small issues

Reviewed-By: Peter Rotich <peter@osticket.com>

Conflicts:
	include/class.ticket.php

Support viewing tickets without a departments

Reviewed-By: Jared Hancock <jared@osticket.com>

forms: Better failsafe for __toString

Reviewed-By: Peter Rotich <peter@osticket.com>

Unpack user information

Reviewed-By: Jared Hancock <jared@osticket.com>

This can happen when associated department is private and the system has no
default department (which is possible with v1.6 upgrade)

This mostly helps when fields change types. If the type of the field
currently cannot convert previous data to a string (like if a short-answer
field was changed to choices), the textual representation of the PHP value
of the field data is given.

Allow new ticket without required contact fields

Reviewed-By: Peter Rotich <peter@osticket.com>

Also, default size should not decrease if different signatures are selected

If a staff member creates a new ticket and cancels the user-lookup /
create-new-user dialog, and the contact information form has a required field
other than the name and email address fields, the ticket cannot be created
because the required fields for new clients are not shown and can therefore
not have a required value.

This patch allows new clients to be created without the required fields when
the ticket is created by staff members.

This issue was addressed for htmLawed, where the UTF-8 version of a
non-breaking space, 0xc2a0 would be collapsed to 0xa0, which would very
likely create an invalid Unicode character, and the text block would be
dropped or truncated.

fix: Restrict access to closed tickets

Reviewed-By: Jared Hancock <jared@osticket.com>

sla: New SLA's default to alert when overdue

Reviewed-By: Peter Rotich <peter@osticket.com>

When checking ticket access - only consider assignment IF the ticket is
open. This is required since staff_id field is overloaded to show who closed
the ticket.