and it works fine while users send emails with email clients and subject is ISO-8859-1 plain text. But some users do it with Google Mail’s web interface. Then outgoing email subject is in UTF-8 and encoded with Base64. Based on «String expansion» section of documentation, I have tried to add second stage to the filter with the same content, but prepended with
headers charset "UTF-8"
- no luck.
Then I’ve tried to determine the problem. I’ll bypass some intermediate steps, but I have ended with following in filter:
In my understanding of «String expansion» this both should result with additional headers, decoded from Base64 — however, I’m getting three identical headers:
Once again, according to my understanding of «String expansion» this means that Exim cannot decode the original header for some reason. I have tried to decode « UmU6IFtFWFRFUk5BTF0gUmU6IFJlOiBSZTog0JzQsNGA0YjRgNGD0YLQuNC30LDRhtC4» manually on the same server with
(tag [EXTERNAL] is one of the actual tags in use).
What am I doing wrong in filters? Or how can I do further diagnostic to determine why Exim cannot decode the headers? Does multiline in subject header influences the result?