Detect attachments with Content-Type: ...; name=

RFC2045, section 5.1 seems to indicate that arbitrary parameters can be
appended to a Content-Type header specification. Some email clients seem to
use the Content-Type header to specify an attachment without giving a
separate Content-Disposition header normally used to signify attachments.

This patch corrects attachment detection for piped emails to detect such
emails. The patch also correctly decodes filenames specified either in the
Content-Disposition or Content-Type headers using RFC5987, where the
filename can be encoded using an arbitrary character set (ie, not us-ascii).
Merge pull request #737 from greezybacon/issue/mailparse-attachments

Detect attachments with Content-Type: ...; name=

Reviewed-With: Jared Hancock <jared@osticket.com>
Actually show correct template description

Fixes #742
Accept attachments from email messages

if the References or In-Reply-To header matches in a way that continues a
ticket's thread, include the attachments in the thread if allowed by the
system settings.
Merge pull request #743 from greezybacon/issue/tpl-description

Actually show correct template description

Reviewed-By: Peter Rotich <peter@osticket.com>
Merge pull request #745 from greezybacon/issue/message-reply-attachments

Accept attachments from email messages

Reviewed-By: Peter Rotich <peter@osticket.com>