D
drek
I am not the poster but here is the available information.
User posting agent is: Microsoft-Entourage/12.10.0.080409
Post is a single-part jpeg as attachment.
A Hogwasher/4.3 user sent screenshot of post that reads:
"Hogwasher encountered an error decoding this attachment. It will be
saved undecoded.
This indicates that this attachment is corrupt. Use with
caution."
A MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) user reported:
"I also got a "problem decoding attachments" message from NewsWatcher,
but it decoded them OK."
On the Windows side:
Outlook Express 6 decoded without comment but offered to save 2 files
with the same name but different sizes.
nascar jets1.jpg - 53KB
nascar jets1.jpg - 118KB <--(the image itself)
Forte Agent successfully saved a single jpeg of 118KB without comment.
From what I could make out in the RFC the resource fork portion of the
article should have a special character prepended to it's filename. As
can be seen below that is not the case.
My question, is this the source of the problem?
If so has it been noted as a bug or fixed in later versions of
Entourage?
Any information on properly configuring the reader for Usenet posting
would be greatly appreciated.
Regards,
======
Post information:
User-Agent: Microsoft-Entourage/12.10.0.080409
Date: Sun, 27 Mar 2011 13:18:01 -0700
Subject: Nascar prerace flyby today (3-27-11)
From:*********
Newsgroups: alt.binaries.pictures.scenic
Message-ID: <C9B4E98C.390A%[email protected]>
Thread-Topic: Nascar prerace flyby today (3-27-11)
Thread-Index: AcvsvBH9S1QKEbu8KUCPtf9n8pFuew==
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3384076686_9149100"
Lines: 3256
X-Postfilter: 1.3.40
Bytes: 240160
X-Original-Bytes: 240097
=======
Below are the full MIME headers from the message including the first
line of encoded text.
User posting agent is: Microsoft-Entourage/12.10.0.080409
Post is a single-part jpeg as attachment.
A Hogwasher/4.3 user sent screenshot of post that reads:
"Hogwasher encountered an error decoding this attachment. It will be
saved undecoded.
This indicates that this attachment is corrupt. Use with
caution."
A MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) user reported:
"I also got a "problem decoding attachments" message from NewsWatcher,
but it decoded them OK."
On the Windows side:
Outlook Express 6 decoded without comment but offered to save 2 files
with the same name but different sizes.
nascar jets1.jpg - 53KB
nascar jets1.jpg - 118KB <--(the image itself)
Forte Agent successfully saved a single jpeg of 118KB without comment.
From what I could make out in the RFC the resource fork portion of the
article should have a special character prepended to it's filename. As
can be seen below that is not the case.
My question, is this the source of the problem?
If so has it been noted as a bug or fixed in later versions of
Entourage?
Any information on properly configuring the reader for Usenet posting
would be greatly appreciated.
Regards,
======
Post information:
User-Agent: Microsoft-Entourage/12.10.0.080409
Date: Sun, 27 Mar 2011 13:18:01 -0700
Subject: Nascar prerace flyby today (3-27-11)
From:*********
Newsgroups: alt.binaries.pictures.scenic
Message-ID: <C9B4E98C.390A%[email protected]>
Thread-Topic: Nascar prerace flyby today (3-27-11)
Thread-Index: AcvsvBH9S1QKEbu8KUCPtf9n8pFuew==
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3384076686_9149100"
Lines: 3256
X-Postfilter: 1.3.40
Bytes: 240160
X-Original-Bytes: 240097
=======
Below are the full MIME headers from the message including the first
line of encoded text.