|
Posted by Mike Z on January 19, 2008, 6:50 pm
If you were Registered and logged in, you could reply and use other advanced thread options
You posted in the digest, regarding to my earlier resubmission of
"Re: 1+10D, was 11X and N11 Codes":
> ***** Moderator's Note *****
> Mike Z said:
>> This is a RE-SEND. I originally sent this on Tuesday, but it still
>> hasn't appeared on Usenet nor in a Digest issue. I assume it was
>> simply an oversight, something overlooked, so I am resubmitting it
>> for Telecom Digest (comp.dcom.telecom).
> IIRC, I rejected the original post because the subject line
> referred to the digest instead of the article _in_ the digest.
> Sorry if I didn't make it clear you needed to resubmit.
But I did NOT refer to the "digest" in the subject line.
I put the word TELECOM in square brackets, and then the subject
line with "re" in front of that, as:
"Re: 1+10D, was 11X and N11 Codes".
> I also reject posts that have "Quoted Printable" encoding if they
> show the equal signs and hex values that quoted-printable encoding
> sometimes leaves in messages.
I have absolutely no idea about this encoding. I am using hotmail,
but I can only assume that you're getting a 7-bit ASCII text version.
> So, PLEASE don't use a Subject such as "Re: Telecom Digest". Also,
> PLEASE don't use Quoted-printable encoding _or_ html. The Digest
> is text-only.
Again, I did NOT have "Re: Telecom Digest" in the subject line. And
AFAIK, I am sending out as 7-bit ASCII text! But how would I even be
able to know otherwise?
Mike
***** Moderator's Note *****
Whichever email client you're using, it _is_ sending quoted printeble
encoding, as shown by the header info reproduced here. Please research
the options available at Hotmail, and change to 7Bit encoding.
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Bill Horne
Temporary Moderator
|