Conflicts:
	include/class.usersession.php

This patch addresses an issue where a client may have upper-case letters in
their email address. When visiting the client portal to check the ticket
status, previously, the exact same case would be required in the 'Email
Address' box.

This patch removes the case sensitivity for email logins.

Correct the PK on %ticket_email_info

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

Fixup a few email piping issues

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

If the content of the message is of type `message/rfc822`, then support
downloading the body of the message and sending it off to the mail parsing
system, simulating a piped email.

They are only available for tickets arriving via the email channel. All
other channel (including email) use the new ticket form to record the
subject and body, which are mapped to the 'Issue Summary' and 'Issue
Details' fields respectively

Structure the drop-down list for the `what` column to be future-minded
concerning custom user data matching.

Previously, if a message had a Content-Disposition header, then it could not
be considered as the body of the message.

If the mail received into the system has a content type of 'message/rfc822',
then unwrap the inner message and use it as the parsed email. Effectively,
assume the email was forwarded as an message/rfc822 attachment.

Previously, the subject was duplicated, which is really confusing

This patch partially reverts the previous database migration patch which
added a primary key to the table on the `thread_id` column. This column
cannot be used, because there may be multiple entries for thread_id = 0.

This also allows ticket_collaborator.isactive to be negative, as well as
adds the database portion of regex support for ticket filters.

Conflicts:
	include/api.tickets.php
	include/class.client.php
	include/class.mailfetch.php
	include/class.thread.php
	open.php

Handle email bounce notifications

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

Timeout after max timeout while fetching emails

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

Delete junk records from the %ticket_email_info table before adding a
primary key. Since there was previously no PK, there could be duplicate
records.

Hide close/hide dialog when esc key is pressed fixes issue #441

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

forms: Fix ticket submission if already logged in

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

If a client is already logged into the client portal and attempts to submit
a new ticket, the ticket will be rejected if the contact-information form
has a required field other than `name` and `email`.

This patch fixes `class Client` so that the user-id is fetched from the
database and made available via the `::getUserId()` method. This was already
corrected in the `develop-next` branch for v1.8.1. The `uid` field is passed
into `Ticket::create()` so the user form validation is bypassed.

This commit should be ignored when merged into the 1.8.1 codebase.

Processing fetching in ASC order of the last fetch time
Remove LIMIT of 10 emails per fetch
Flush the buffer and terminate the request cleanly on autocron

Conflicts:
	include/staff/tickets.inc.php

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

Previously, the mail parsing and fetching system would recurse unbounded
searching for bodies by content-type

If a custom list item were added to an email template, and there is no data
for the field (ie. the field is not required) when the template is rendered,
the system would crash.

toString() is required to return a string, no matter what. This patch
cascades the (string) coercion to the current value of the list field if it
is not an instance of a DynamicListItem

Don't send out SQL error on upgrade to 1.8.1

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

Fix display of priority field in queue export

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

Also removes the fetching of priorities separately and addresses sorting of
priorities by the ID field rather than the urgency field.

oops: Fixup deploy for 1.8.1 and onward

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

Fixup querying drop-down lists via advanced search

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