How to decode the email subject?


I have send a mail with Subject line as

[BILLING #PHY-945-49853]: [Ticket #12622] Payment Method

But in the source of the message the line is like below


It is encoded in Base 64.How can i decode it back to the original subject line in English using php ? I have tried with the php base64_decode($subject) but it does not decode it to the original subject ([BILLING #PHY-945-49853]: [Ticket #12622] Payment Method)

I’m also attaching a sample email message in this mail.


Return-Path: …
X-Original-To: …
Delivered-To: …
Received: …
To: …
From: =?UTF-8?B?U0FWVllFSE9TVElORyBTQUxFUw==?=
X-Priority: …
X-MSMail-Priority: normal
X-MimeOLE: Produced By Kayako Fusion v4.01.204
X-Mailer: Kayako Fusion v4.01.204
Reply-To: …
Date: …
Content-Type: multipart/alternative;
MIME-Version: 1.0
Message-Id: …

This is a message in MIME Format.
If you see this, your mail reader does not support this format.

Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Support Center:
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

If anyone knows please help me…

it seems that the subject is blank due to some reason that is why you are getting this…

This occurs usually because one of your parameters contains a non-ASCII character in it, causing the headers to be UTF-8 Encoded.

Base64 Decoding your data shows the following:
Subject: [SALES #BBN-935-37917]: [Ticket #12622] Payment
Metho <– Hmmm…

seems like your subject line is too long for the mail daemon, so it’s mangling the result. But I could be wrong there.

I’ve seen that format of characters before, but for the life of me cannot remember where. =34 =EF etc…

It’s encoded, but not base64…

Er… yes, it is base64.


Q = Quoted Printable
B = Base64

It’s worth pointing out that there’s nothing WRONG with having the string encoded - it’ll still come out on the other end correctly.

Ahh, I see. Learning is awesome.

So, am I imagining seeing something like =C34 in emails before?

In the actual email itself? Shouldnt have gotten that far (Your local mail daemon (or is it the email program itself… not sure.) should have decoded the data back into readable form)…