Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Replace text in message content on base64 messages #679
We've been testing and on base64 encoded messages, replacing text (to remove previous replies) does not appear to work.
It looks like the matching occurs before the content is processed to text.
I'd assume this might be a bug but may also be valid as the content is encoded.
Do you have an example of one of these message sources, along with the behavior you're running?
I'm not able to reproduce the issue with a sample like:
Where the decoded body is "This is a test message that was Base64-encoded".
I can set up a rule like:
And the ticket we parse becomes:
The transfer decoding from Base64 would be happening in ext/Mailparse, and it's not something we're doing at the app level.
The raw email message may give a clue -- like the content actually coming from a message/rfc822 attachment or something. Or being double base64-encoded by the sender (stranger things have happened). I wouldn't suspect the latter if you do see normal text in the ticket (just not substituted by your bot).
You could peek into what the bot sees for that message by having the bot send you a copy of the
I wonder if it is their headers in that case not setting something but the message is still being pushed through.
Only have the headers from the message we do have which are unlikely to help.
Have enabled and will get a message checked once we get a new one which will likely be Monday.
In the headers as before:
Then the message with content stripped.