Previous the options defined for the Mailer::send() function were confusing
when sending an In-Reply-To header

Previously, the References header emitted by the system for new thread
entry auto-responses and alerts included the message-id for which the email
was a reply in the `References` header. This patch corrects the issue by
placing the reply message-id in the In-Reply-To header, and constructs a
correct References header.

That is, if available, the References header received in the email that was
used to create the thread entry is appended to the message-id the email is
actually in reply to. This is the expected usage of the References header.

Support ticket thread items in email templates

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

Strip quoted reply revisited

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

Order FAQ by question

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

Remove accidental inclusion of remote web page

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

* %{ticket.thread.original} represents the original message submitted when
    creating the ticket
* %{ticket.thread.lastmessage} represents the most recent message submitted
    by the end user

The XKCD index page was accidentally added when testing a new feature for
osTicket-1.8

Include category when searching the knowledge base 

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

Support non-standard port numbers for MySQLi

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

Mark tickets overdue which have no SLA

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

Make Crypto::random() more reliable on Windows

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

Handle parsing email if Reply-To header is missing

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

Reduce cost of deleting orphaned files

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

Support updating the source of the ticket

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

Die on redirect

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

Validate port during installation

Add help information about the non-standard port number to the popup tips in
the install screen.

Support MySQL 'localhost' connections using a non-standard port number.
Ordinarily, MySQL will ignore the port setting on *nix systems if the host
is specified as 'localhost'

Implements/Fixes #769

This patch makes openssl the preferred source of random data on Windows and
will only use mcrypt_create_iv on PHP 5.3.7 and newer.

Fixes #771

Fixes #772

Previous explain included a nested sub-select, which exponentially increased
the count of the rows to be examined. This patch eliminates one layer of
nesting on the sub-select and dramatically increases the performance finding
orphaned files.

Fixes #773

References:
http://www.osticket.com/forums/forum/osticket-1-7-latest-release/troubleshooting-and-problems-aa/9446-version-1-7-much-slower-than-1-6

Support incorrectly labeled us-ascii charsets

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

Some email clients (names omitted to protect the innocent) advertise the
encoding as us-ascii when iso-8859-1 was really implied. This patch allows
the two charsets to be interchangable.

If a ticket has a due date and does not have an SLA set, the ticket would
never transition to overdue. This patch addresses an SQL flaw preventing the
ticket from being transitioned.

Fixes #757

Change PDF print to show custom logo

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

If the GD extension is not available for the PHP installation, then use a
copy of the default client-site logo with the alpha channel removed.

Crazy performance penalty scanning blob tables

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

Better converting from ticket thread to PDF

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

Die with internal server error on misconfiguration

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

Fix parsing of attachments

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

Use base64 encoding for text version of emails

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

Assume that text in the database is encoded in UTF-8 and assume that it is
HTML text and the entities should be decoded prior to display in the PDF.

Fixes #756

When scanning the file_chunk table for orphaned file chunks that can be
deleted, apparently, MySQL will read (at least part of) the blob data from
the disk. For databases with lots of large attachments, this can take
considerable time. Considering that it is triggered from the autocron and
will run everytime the cron is run, the database will spend considerable
time scanning for rows to be cleaned.

This patch changes the orphan cleanup into two phases. The first will search
just for the pk's of file chunks to be deleted. If any are found, then the
chunks are deleted by the file_id and chunk_id, which is the primary key of
the table.

The SELECT query seems to run at least 20 times faster than the delete
statement, and DELETEing against the primary key of the blob table should
be the fastest possible operation. Somehow, both queries required a full
table scan; however, because the SELECT statement is explictly only
interested in two fields, it is more clear to the query optimizer that the
blob data should not be scanned.

References:
http://stackoverflow.com/q/9511476

Or internal server (database) outage

Some mail clients and mail brokers do not properly handle quoted-printable
encoding, used in osTicket outgoing emails. Oddly, the end mail clients
render the email with trailing equal signs (=) at the end of every line,
where it was added due to QP encoding.

References:
http://www.osticket.com/forums/forum/osticket-1-7-latest-release/troubleshooting-and-problems-aa/10708-solved-microsoft-exchange-internet-mail-lines-end-with
RFC 2045 section 6.7, http://www.ietf.org/rfc/rfc2045.txt