Also try harder to send a relevant In-Reply-To and References header back
to the client with the email message.

This patch suggests a change to the message-id creation process that
includes stamping the receiving user-id (staff or client) along with the
thread-id of the originating notice. This allows detection of threading if
the clinically brain-dead mail client drops all the other header detection
mechanisms, including the tag placed in the email body, on response.

This patch works for both client and agent communication.

forms: Properly export choices lists

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

files: Avoid crash if `file info` extension missing

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

Disable auto-responses on staff created tickets

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

i18n: Clarify attachment settings labels

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

pdf: Fix invalid UTF-8 characters error message

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

Take into consideration the auto-response settings when sending out new
ticket by staff notice to the end user.

i18n: Add a few forgotten strings #2

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

thread: Fix regex for ticket # in email subject

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

forms: Drop custom data when removing a user

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

The ticket number regex was changed with the advent of custom ticket
numbers, and it matches the closing punctuation in [#12345], that is, the
closing bracket would be included in the ticket number sought in the
database. Therefore, it would never match the ticket number properly.

The new regex attempts to match punctuation and non-punctuation groups so
that punctuation in the middle of the ticket number is matched; however,
punctuation at the end is not. So #12345+DEPT will match properly and will
ignore any trailing whitespace and punctuation.

bug: Check to make sure $ost is initialized

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

Previously, this was not ported properly now that multiple selections are
supported in the choice field and derivatives.

Fix subject display when a ChoiceField is used

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

There was a slight issue when transitioning from a short answer field to a
drop-down field, and when the CDATA table is dropped and rebuilt.

forms: Fix interpretation of custom list data

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

Rollback to auto commit, except for sequence  iteration

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

Prior to osTicket v1.9.4, drop down lists only allowed for a single entry.
After upgrading to 1.9.4 the database data for drop downs changed to allow
for multiple entries. However, the old data format was not properly handled
by the SelectionField::to_php() method which handled interpreting and
upgrading the database data.

Keeping the transaction active for the entire request increases the
likelihood of a deadlock on Galera clusters.

search: Escape non-word chars for search queries

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

oops: Always strip embedded images unless

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