Frank Kotler wrote:

....
 > I'm cc'ing this to the clax86-submit address - we need test messages.
 > This may or may not get posted twice... Sorry for the rubble -
 > construction!

Okay... I guess the nntp server recognized it as an identical message... 
Try *just* by mail... I need a test message to add a "Newsgroups:" 
header to!

Best,
Frank

On 2010-01-26, Frank Kotler <fbkotler@comcast.net> wrote:
> Frank Kotler wrote:
>
> ...
> > I'm cc'ing this to the clax86-submit address - we need test messages.
> > This may or may not get posted twice... Sorry for the rubble -
> > construction!
>
> Okay... I guess the nntp server recognized it as an identical message... 
> Try *just* by mail... I need a test message to add a "Newsgroups:" 
> header to!
>
> Best,
> Frank
>
>

I'm a test message...  I'm a test message... Over!

Duke Normandin wrote:

....
> I'm a test message...  I'm a test message... Over!

Thanks, Duke! Just to try to keep it on-topic, the "test" instruction 
appears 4 times in the program approving this message, each time "test 
eax, eax". I must try to be more imaginative! :)

Best,
Frank

On 27 Jan, 22:56, Frank Kotler <fbkot...@myfairpoint.net> wrote:
> Duke Normandin wrote:
>
> ...
>
> > I'm a test message... =A0I'm a test message... Over!
>
> Thanks, Duke! Just to try to keep it on-topic, the "test" instruction
> appears 4 times in the program approving this message, each time "test
> eax, eax". I must try to be more imaginative! :)

In a piece of software consistency is usually better than imagination!
It sounds good as it is. Are you serious that you have written some
bespoke moderation software in assembler?

Whatever it is here's a message with Google's funny character encoding
for equal signs. =3D=3D=3D

On 28 Jan, 07:54, James Harris <james.harri...@googlemail.com> wrote:
> On 27 Jan, 22:56, Frank Kotler <fbkot...@myfairpoint.net> wrote:
>
> > Duke Normandin wrote:
>
> > ...
>
> > > I'm a test message... =A0I'm a test message... Over!
>
> > Thanks, Duke! Just to try to keep it on-topic, the "test" instruction
> > appears 4 times in the program approving this message, each time "test
> > eax, eax". I must try to be more imaginative! :)
>
> In a piece of software consistency is usually better than imagination!
> It sounds good as it is. Are you serious that you have written some
> bespoke moderation software in assembler?
>
> Whatever it is here's a message with Google's funny character encoding
> for equal signs. =3D=3D=3D

Sweet! Looks like you've fixed that problem too.

James

James Harris wrote:
> On 27 Jan, 22:56, Frank Kotler <fbkot...@myfairpoint.net> wrote:
>> Duke Normandin wrote:
>>
>> ...
>>
>>> I'm a test message...  I'm a test message... Over!
>> Thanks, Duke! Just to try to keep it on-topic, the "test" instruction
>> appears 4 times in the program approving this message, each time "test
>> eax, eax". I must try to be more imaginative! :)
> 
> In a piece of software consistency is usually better than imagination!

Agreed. It isn't jazz. I was surprised to see that I'd used "test" so 
few times, actually, and always with eax. Well, we add some bit flags to 
munge address and all, it'll crop up more, probably.

> It sounds good as it is. Are you serious that you have written some
> bespoke moderation software in assembler?

"Am writing" or "Am attempting to write" would be closer than "have 
written", but yeah, these messages we're reading have been fetched from 
a mail server and posted to an nntp server by a program written in asm. 
The "in between" parts are just text manipulation. There are more 
"appropriate" languages for text manipulation than asm, but I don't know 
'em. As Rod points out, we've got some work to do in that area. It might 
actually be easier to learn one of those "more appropriate" languages. 
But this way is more "fun". (hey, some people jump out of perfectly good 
airplanes for "fun" - doin' this isn't *that* crazy!)

> Whatever it is here's a message with Google's funny character encoding
> for equal signs. ===

Thanks! With help from several people, we figured out that the problem 
was deleting too many headers - a "quoted-unprintable", and a couple of 
others. Nathan tweaked up "PyModerator" to fix it (not our software - 
the other guy did it). When we get to "header management", which as Rod 
points out, should be Real Soon Now, we'll try to keep it right.

Best,
Frank