On Nov 5, 2007, at 7:49 AM, James Edward Gray II wrote:

> On Nov 3, 2007, at 11:10 AM, Douglas Wells wrote:
>
>> In article  
>> <57a815bf0711030047x813fe18r6f6d79c1be251092 / mail.gmail.com>,
>>   raasdnil / gmail.com writes:
>>> Thanks for your work James.
>>>
>>>>> According to my scan of the log this morning, every email the  
>>>>> gateway
>>>>> sent since yesterday's upgrade was accepted by Usenet.  I was even
>>>>> able to find messages modified by the gateway and they looked  
>>>>> great
>>>>> on comp.lang.ruby.
>>>>>
>>>>> This transition appears to be a success.
>>>>>
>>>>> James Edward Gray II
>>
>> Well, there appears to be at least one little glitch remaining.
>> The following header line in the immediately referenced article
>> shouldn't appear with an unencoded article body:
>>
>>     Content-Transfer-Encoding: Base64
>
> I've deployed some fixes to the gateway this morning that I hope  
> will correct this issue.  Please let me know if you see more problems.

I have deployed another set of fixes to the gateway tonight.

I've attempted to correct a reported problem where the name was being  
dropped from "From" fields.

I've also made the code that adds the this-message-was-modified note  
more careful.  I now only add it to 7bit, 8bit, and binary encoded  
bodies, so I don't damage something like Base64 encoded content.  The  
note will now always appear in an X-Gateway-Modified header  
regardless of body encoding, so we will have a means of tracking  
this.  I realize that means it's not immediately visible for some  
message types, but it seems safer to me than reencoding the message.

Please let me know if you locate further issues.

James Edward Gray II