email failure

[g]

On 01/20/2014 03:27 AM, Patrick O'Callaghan wrote:
> On Jan 20, 2014 2:22 AM, "g" <geleem at bellsouth.net> wrote:
>> On 01/19/2014 07:20 PM, Patrick O'Callaghan wrote: <>
>>
>>> IOW it *was* in plaintext. It did however also have a "Rich
>>> Text" alternative part, which presumably is what violates the
>>> Guidelines
>>
>> if you look up from bottom, you will also see that it has;
>>
>> }>  --e89a8f646f8f93fa7504f051c062 }>  Content-Type: text/html;
>> charset=UTF-8 }>  Content-Transfer-Encoding: quoted-printable
>>
>> which also violates  guidelines.
>
> That would correspond to the alternative part, which I already
> mentioned.


/(-:
no. that relates to the *html* part that you failed to mention

your emails have and still are producing;

     Content-Type: multipart/mixed

which gives;

     Content-Type: text/plain; charset=UTF-8

     Content-Type: text/html; charset=UTF-8
     Content-Transfer-Encoding: quoted-printable

     Content-Type: text/plain; charset="utf-8"
     Content-Transfer-Encoding: base64

so why it is that you have not changed your gmail configurations/
options,  or what every it is called, like you said you would in
a previous post?
/:-)

-- 

peace out.

in a world with out fences, who needs gates.

tc.hago.

g
.