Here's an example email structure:
```
multipart/mixed
 - multipart/report; delivery-status
   - multipart/alternative
     - text/plain
     - text/html
   - message/delivery-status
   - message/rfc822
```

The previous code would only find the body if the email main headers had:
Content-Type: multipart/report; report-type="delivery-status". In such a
case it would scan for a plain/text body.

This patch will scan for the usual body if the scan for the body as usual if
the report scan did not find anything.

Also, output errors to stderr when running API from the command line

It seems that most systems handle the newline character alone without a
problem; however, some systems cannot handle the standard CRLF line ending
at all.

The %ticket_email_info table needs an index on thread_id. This is done in
the `develop-next` branch; however, this patch helps alleviate performance
issues on the main branch until the `develop-next` branch is collapsed for
main line development.

Fixed typo

This also adjusts the logic internally to lookup the priority by the
priority_urgency field, which should be constrained to follow priority
precedence over the priority_id field.

Because CSV has no way of indicating a content character set, writing the
file with a Unicode byte-order mark is useful to declare the content in
UTF-8 encoding.

When sending alerts to agents, consider the setting of the new message alert
configuration.

This will help when saving rules with trailing spaces for instance, which
may make things not match when visually the administrator would otherwise
expect the filter to match.

Fixes #1834

For a yet unknown reason, the association between the field implementations
and the DynamicFormEntry object is not maintained from calls to
DynamicFormEntry::getFields().

This patch addresses the issue by always associating the "form" when
returning from ::getFields()

Preserve the fields indexed keys
Only sort the fields once, after adding missing fields

Reset field content when building a new form

See: http://osticket.com/forum/discussion/85083/osticket-sends-no-html-mails#latest

Looked at crowdin and the term "Add Organization" is already used in the following context:
#: include/staff/templates/org-lookup.tmpl.php:82

So my suggestion is to use it also for this context here, which would not require a new translation ;)

Michael

Fixes #1809

Get all dynamic fields in DynamicFormEntry, not just fields with answers

This partially reverts commit bff191b6.
The hasSpecialSearch() method can be retired in `develop-next` — NOT in the
`develop` branch

If the system receives an email by a collaborator which has not yet been
added to the ticket (a friend of a friend — that is, a collaborator forwards
an email to a third-party), a header is added to the thread body something
like:

Received From: afriendofafriend@mycompany.tld

However, if the thread body is text and the HTML ticket thread is enabled,
then the text formatting hint will be lost and the body will be assumed as
HTML deeper inside the thread entry creation process. Therefore, the
whitespace inside the resulting thread entry will be collapsed.

This patch addresses the issue by maintaining the original format hint with
the thread body.