I’m hoping this will be an easy one to fix - but, for some reason, one particular type of email that my RT instance is receiving is resulting in tickets which state:
Message body not shown because it is not plain text.
However, the content is entirely plain ASCII text, no UTF-8, nothing fancy at all. It’s about four lines, and I’ve gone over it repeatedly looking for what could be triggering this in RT.
This is new behaviour that came about after the email path/route changed for these messages. The message content is not changed at all, it’s just being sent to a different email address before being injected into a queue in RT.
In fact the new email address is a more direct path - previously, it was going to an email alias, which went to an IMAP folder which Fetchmail would then send to the RT instance. Now it skips Fetchmail.
It started with RT 5.0.3, but, I updated to 5.0.4 this morning and that (unsurprisingly) has not had any impact.
The email I get from RT now says:
“This transaction appears to have no content”
And the plain ASCII email comes through as “Attachment.txt”.
However, it’s not a MIME message, there are no parts, it is an insanely simple email.
Any suggestions on what to look at?