If images are included inline in an email and the quoted-response removal
algorithm drops them, then silently drop the attachments

It was also the last-modified date of the category -- not the actual FAQ
article itself

This is necessary to allow for creative department based access control and
alerts.

This happens when upgrading from 1.6, the company information does not yet
exist (neither do the form tables)

Properly escape company name for display

Background: osTicket allows access to assigned open tickets (both personal
and team assignments) regardless of the assigned department or group. This
is necessary to allow staff to work on tickets in an otherwise restricted
department.

When a staff member closes a ticket, they're credited (ticket.staff_id is
set to staff's id) for the purpose of showing who closed the ticket.
osTicket mistakenly allowed continued access to closed tickets even when the
staff doesn't have access to the ticket based on departmental access.

Join to staff/user tables to get current name when fetching thread entries.

Reported by @ntozier

email.

This is necessary to eliminate possible loop when an email is sent to a
virtual/aliased address. Not all mail servers add delivered-to header!

Because the file type normally defaults to the system default (for fetched
emails at least), the backend char was not saved, because the file type char
was left at the system default. Therefore, if a file is saved to a backend
other than the default (in the database), the data will likely be saved to
the backend, but the file metadata will reflect the incorrect backend.

The only reason the file type char was not defaulted in the
AttachmentFile::save() method was for the migration process from osTicet 1.6
to osTicket 1.7. This is mitigated by passing `false` specifically from the
migration task.

Since otherwise the file type char is now set, the backend char is now saved
with the file metadata.

If a ticket is created via email for an existing user, under some
circumstances, no user will be associated with the new ticket.

If a remote user is found by name and does not have an email address, a bad
SQL query would be generated

If a non-text attachment specifies a charset in the content-type header,
don't transcode the content before saving it to the database. This can
corrupt attachments which have a header like the following:

Content-Type: application/pdf; charset=UTF-8

Since a PDF contains binary data, coercing it to UTF-8 encoding will drop
characters not valid in UTF-8 and will corrupt the attachment data.

Also support the TransportName in the properties list and prefer it over the
attachment-level attribute, as it is Unicode encoded.

The priority setting was broken when priority was added to the dynamic data