mail client eating =23 characters, solaris/linux

I'm trying to send html mail via cron of open bugzilla tickets.
Server is on sendmail on solaris, mail client is Evolution on linux.
The lines appear to be going out correctly:

Test


but the characters "id=22402" are being switched or interpreted
as "id#402" so it appears that =22 is being interpreted as a
special character. If I switch it to =21 or =23 I get different
behaviour.

The header delivered to sendmail is:

Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

One more datum is that on SquirrelMail the data comes through
as ascii text. Not sure there if I just don't have some switch
on or off.

Any ideas or pointers?

Don

Re: mail client eating =23 characters, solaris/linux

On 21 Jul 2005 06:31:22 -0700,
dshesnicky@yahoo.com wrote:


>
> I'm trying to send html mail via cron of open bugzilla tickets.
> Server is on sendmail on solaris, mail client is Evolution on linux.
> The lines appear to be going out correctly:
>
> Test

>
> but the characters "id=22402" are being switched or interpreted
> as "id#402" so it appears that =22 is being interpreted as a
> special character. If I switch it to =21 or =23 I get different
> behaviour.

That is correct hehaviour exept that id=22402 would be id="402
and id=23402 would be id=#402. If you want a literal equals sign
you put =3D in the file.

>
> The header delivered to sendmail is:
>
> Content-Type: text/html; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable


Notice the Content-Transfer-Encoding header and read rfc2045 to
see what it means.


Villy

Re: mail client eating =23 characters, solaris/linux

>
> That is correct hehaviour exept that id=22402 would be id="402
> and id=23402 would be id=#402. If you want a literal equals sign
> you put =3D in the file.

Villy,
Sorry for the late reply but I was offered a weeks vacation
at the last moment and decided "Why the hell not". Anyway I tried
the above fix and it worked like a charm. Will read the below
as well.

Thanks,
Don


>
>
> Notice the Content-Transfer-Encoding header and read rfc2045 to
> see what it means.
>
>
> Villy