Some security inspection appliances and load balancers don't appreciate
something in the HTTP headers that is not a valid HTTP header. Furthermore,
the browser needs the Content-Type header to identify that the image is not
the PHP default of text/html

Remove requirement of external-ticket-id in subject line

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

This patch affords an administrator the ability to remove the
[#%{ticket.number}] from the email template subject line for the new ticket
autoresponse and the new message autoresponse. Previously, the ticket number
with a prefixed hash in brackets was used to identify which ticket thread an
email was in reference to.

With this patch, the email message-id (which was already kept on file) is
sent in the MIME "References" header. When a user responds to and
autoresponse email, the "References" will include this message-id in the
return email. The ticket thread is then matched up with the email based on
the message-id rather than the subject line.

Ticket numbers are still supported in the subject line, in the event that
non-compliant email clients do not properly include the References header.

Files _MUST_ be readable by Apache or IIS in order for the attachment
migration to complete and properly keep all attachments between osTicket 1.6
and 1.7

Don't leak private FAQ titles

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

Encourage sign-ups on the mailing list

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

Don't log the user out after changing account info

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

Require encryption.

Fixes #683

Search results on the client interface for knowledgebase articles would
previous show hits for the internal (private) knowledgebase articles. The
subjects were shown but the articles were not viewable.

This addresses the SQL logic issue causing the private hits to be shown.

overwrite vs. override

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

Also raise awareness of the hosted platform for osTicket

Also include
  * username validation -- no spaces or weird chars
  * no longer base64 encoded sha1-hex hash for CSRF token
  * refresh login page every two hours to keep session active

Support Reply-To headers in ticket filters

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

Fix incorrect file attachment if filetype is rejected
Reviewed-By: Peter Rotich <peter@osticket.com>

Add files new to 1.7.1 to the download package

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

Copy typo on the site-pages management

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

 * web.config
 * pages/{.htaccess,index.php}

Fixes #667

The email filtering feature supports a 'Use Reply-To' feature, but seems to
never have been implemented. This patch officially supports using the
Reply-To email header as the From header for emails matching the filter.

If an attachment is submitted via the API and the filetype is rejected, the
file would be attached anyway. However, if the file was encoded base64, the
content would not be decoded.

If reading the remote_addr from X-Forwarded-For header, ensure that there is
no leading or trailing whitespace. If ip_binding is enabled for staff
sessions, this could cause unnecessary logouts

And ensure that the email address is trimmed to help matching against email
registered for previous tickets.

Anything that would happen after the last patch was applied would never be
logged, because the system would immediately indicate that no upgrade was
pending.

Conflicts:
	include/client/view.inc.php
	include/staff/ticket-view.inc.php

Fixes #575

Fixes #588