Control whatever to read attached RFC822 mail content

Reading into the attached RFC822 message as osTicket does by default may cause troubles when the first mail section does not contain a content type text/html. OsTicket will in this case use the body from the attached mail as content as it searches recursive for text/html content first. Email clients will normally show this messages as attachments

We have several cases where emails are handled wrongly especially spam reports.

This change will add an option in the admin panel settings->email tab to control whatever the inline message content should be read or treated as an attachment by osTicket
Would you consider a purely random, consistently-generated filename, such as
```php
$filename = 'email.'.Misc::randcode(8).'.eml';
```
Consider that any valid unicode characters can go in the subject line. So a Japanese email with Katakana characters in the subject line might be reduced to just an empty string