It is the defacto standard to reference an inline image in an email by
referencing the Content-ID header of the referenced attachment in the @src
attribute of the image. For instance, `<imc src="cid:image001.png">` where
the `cid:` scheme of the attribute indicates that the referenced image URL
is a separate content of the email. The image attached to the email would
have an accompanying header like: `Content-Id: <image001.png>`. However,
some mail systems, including a certain fax to email service, do not
correctly indicate the location of the image with the content-id URL.
Instead, the referenced image tag would be `<img src="image001.png">`

This patch addresses the issue by searching the message body for all
references to attached content-id's in all @src attributes with or without
the content-id URL scheme indicator. Previously, such images would not be
displayed inline in the ticket thread.

References:
https://tools.ietf.org/html/rfc2392

It is perfectectly fine to have an image cited in an HTML body similar to:

<img width=909 height=302 src=cid:image002.jpg@01CF5426.BF5A72A0 alt=image>

Which may or may not have quoted @src attribute, and may very well have an
at sign (@) somewhere in the attribute text. The previous regular expression
would not match such a @src attribute.

Thread entries now have a flexible `format` specification, which allows the
system to save the format alongside the original text. This allows the
system not to have to convert everything to HTML when storing in the
database

The bug prevented attachments from being sent out if it was previously
attached to the ticket - for example, you could resend a file to end user.

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.

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

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

This approach will help detect responses to the ticket thread from mail
clients which do not include the References and In-Reply-To MIME headers.
This also allows the Subject line to continue to omit the ticket number.

level.
Handle cases where thready body is sent in as a string

We're going to assume HTML of html thread is enabled - otherwise text is
assumed.

Cleanup and make HTML safe by default
Strip empty lines in TEXT content

This will be helpful to keep track of whether a text is html or text and
provide a way to convert it exactly once.

Rename routines to make it a little clear on what they do

This allows the email system to detect something like a bounce mail and
specify that the associated message should be an internal note.

Fixes the rewriting of the `key` field in the ticket thread body. The
storage de-duplication system may replace the `key` value with an existing
one. The ticket thread system will use the `key` value assigned when the
file is committed to the database or the existing key of the duplicate file.

Also fixup installation issues with the attachment storage plugin
architecture

  * Include a `bk` column to store the storage backend
  * Include a `signature` column which represents a repeatable hash of the
    file contents
  * Rename `hash` to `key` since it isn't a real hash

The concept of extid is being retired to pave-way for customizatable ticket
numbers.

 - This is necessary so we'll have a name on record - even on user deletion.

Pass the user id (uid) to ticket create instead of unpacked data.

Using email headers try to determine the user.