Searching \ for ' [ADMIN] Attachment problems go bye-bye (' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=attachment+problems
Search entire site for: 'Attachment problems go bye-bye ('.

No exact or substring matches. trying for part
PICList Thread
'All: [ADMIN] Attachment problems go bye-bye (I hop'
2000\11\15@215929 by Mike

picon face
part 1 1489 bytes content-type:text/plain; charset=us-ascii (decoded quoted-printable)

[I tried sending this once before, but it seems to have been eaten somewher
along the way.  If you get this message twice my apologies.]

All righty.  I modified the footers that were causing those attachment
problems for some, so hopefully those problems are a thing of the past.

However, after reading over the RFC delineating the Quoted-Printable
encoding, there is still the possibility of the same problem reoccuring due
to a regular message.  It seems the Q-P encoding is extremely fragile.
Anytime there is an equals sign follwed by two characters that fall into the
hex character set (i.e. 0-9 and A-F) Q-P will think that's an endoding meant
for it to interpret.  Pretty brain dead encoding, if you ask me.  But it's
what we gotta put up with.

So anyway - the attachment problems caused by the footers have been taken
care of.  If anyone is still having problems with attachments, let me know:

a) Who sent the message
b) The subject line
c) The date / time stamp on the message

Send these to me via *private mail*, not on list.  I do try and check my
email on a regular basis, at *least* once a day.  And I *will* get back to
you.  Sometimes it might take a day or two, but I will.
-- Mike Werner  KA8YSD   | He that is slow to believe anything and
                     | everything is of great understanding,
'91 GS500E            | for belief in one false principle is the
Morgantown WV         | beginning of all unwisdom.



part 2 233 bytes content-type:application/pgp-signature (decode)

part 3 131 bytes
--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2000\11\16@205954 by Bill Westfield

face picon face
   However, after reading over the RFC delineating the Quoted-Printable
   encoding, there is still the possibility of the same problem reoccuring due
   to a regular message.  It seems the Q-P encoding is extremely fragile.

I was thinking it was only a problem because the list server was appending
non-QP compatible text on a message that was mime-tagged as using QP
formatting.  A message originating on a non-QP system may contain "invalid"
"=" constructs, but it won't be tagged as being QP-format in the first
place, either.  So things should be OK?

BillW

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email spam_OUTlistservTakeThisOuTspammitvma.mit.edu with SET PICList DIGEST in the body


2000\11\16@225950 by Mike

picon face
part 1 1538 bytes content-type:text/plain; charset=us-ascii (decoded quoted-printable)

William Chops Westfield wrote:
>     However, after reading over the RFC delineating the Quoted-Printable
>     encoding, there is still the possibility of the same problem reoccuring due
>     to a regular message.  It seems the Q-P encoding is extremely fragile.
> > I was thinking it was only a problem because the list server was appending
> non-QP compatible text on a message that was mime-tagged as using QP
> formatting.  A message originating on a non-QP system may contain "invalid"
> "=" constructs, but it won't be tagged as being QP-format in the first
> place, either.  So things should be OK?

Uhh ... I think so.  Basically it should be fixed, but I can't guarantee
that something like some code snippets or an alogrithm explanation won't
still trip this problem in the future.

One of the "fun" things to be dealt with here is the possibility that the
message might not be *sent* as Q-P, but one of the transfer points might
change it to be Q-P.  I've seen a few times my ISP has done this.  No, I'm
*not* pleased with that.

As near as I can tell I've done what can be done as far as list config.  I
suppose only time will tell as to whether it really is fixed or not.
-- Mike Werner  KA8YSD   | He that is slow to believe anything and
                     | everything is of great understanding,
'91 GS500E            | for belief in one false principle is the
Morgantown WV         | beginning of all unwisdom.



part 2 233 bytes content-type:application/pgp-signature (decode)

part 3 136 bytes
--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email .....listservKILLspamspam@spam@mitvma.mit.edu with SET PICList DIGEST in the body


2000\11\17@020343 by Lee Jones

flavicon
face
>>> However, after reading over the RFC delineating the Quoted-Printable
>>> encoding, there is still the possibility of the same problem reoccuring
>>> due to a regular message.  It seems the Q-P encoding is extremely fragile.

I disagree.  But then I commute to work with one of the MIME
RFC authors.

Without quoted-printable, any email message containing 8-bit
characters must be encoded.  Originally, the only mechanism for
this was Base 64.  This turns an entire text part, even if it
only contained 1 character with the high bit set (such as an
accented character in a signature line), into an effectively
human unreadable opaque blob.

Quoted-printable was introduced to rectify this.  With Q-P
encoding, that same text message would still be primarily
human readable text with a couple embedded encoded characters.


{Quote hidden}

If the transfer point properly converts the message part into
quoted-printable, then all existing equal signs ('=') are encoded.
In the above example, the input string "=3D" becomes "=3D3D" after
the quoted-printable encoding.  Later, when decoded, it reverts to
the original "=3D" string.  As part of the conversion process, the
message part is tagged with "content-encoding: quoted-printable".

Now if the transfer point does _not_ encode the message part, but
simply tags it with a "content-encoding: quoted-printable" line,
then the transfer point software is broken.  It is not compliant
with the RFCs.  It needs to be replaced or fixed.  Period.

In other words, any time software tags an object as having a
specific encoding, such as quoted printable, when that object
is not encoded, then the software is broken.

Hopefully, you can coerce the list software to do the right
thing.
                                               Lee Jones

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamKILLspammitvma.mit.edu


'[PICLIST] [ADMIN] Attachment problems go bye-bye ('
2000\11\17@060835 by Alan B. Pearce

face picon face
>[I tried sending this once before, but it seems to have been eaten somewher
>along the way.  If you get this message twice my apologies.]

>All righty.  I modified the footers that were causing those attachment
>problems for some, so hopefully those problems are a thing of the past.

I have now seen this message three (3) times Mike. I do not know if this third
one is a bounce from somewhere, or another resend by you.

--
http://www.piclist.com hint: To leave the PICList
.....piclist-unsubscribe-requestKILLspamspam.....mitvma.mit.edu


2000\11\17@142950 by jamesnewton

face picon face
Bingo. I think Bill is right.

---
James Newton (PICList Admin #3)
EraseMEjamesnewtonspam_OUTspamTakeThisOuTpiclist.com 1-619-652-0593
PIC/PICList FAQ: http://www.piclist.com or .org

{Original Message removed}

2000\11\17@143201 by jamesnewton

face picon face
We are getting bounces. The source has been BLOWN TO HELL WITH A REALLY BIG
GUN....

...I'm getting tired of bounces...

...but the left-overs have to filter through.

---
James Newton (PICList Admin #3)
jamesnewtonspamspam_OUTpiclist.com 1-619-652-0593
PIC/PICList FAQ: http://www.piclist.com or .org

{Original Message removed}

'All: [ADMIN] Attachment problems go bye-bye (I hop'
2000\11\18@023340 by Mike

picon face
part 1 1351 bytes content-type:text/plain; charset=us-ascii (decoded quoted-printable)

All righty.  I modified the footers that were causing those attachment
problems for some, so hopefully those problems are a thing of the past.

However, after reading over the RFC delineating the Quoted-Printable
encoding, there is still the possibility of the same problem reoccuring due
to a regular message.  It seems the Q-P encoding is extremely fragile. Anytime there is an equals sign follwed by two characters that fall into the
hex character set (i.e. 0-9 and A-F) Q-P will think that's an endoding meant
for it to interpret.  Pretty brain dead encoding, if you ask me.  But it's
what we gotta put up with.

So anyway - the attachment problems caused by the footers have been taken
care of.  If anyone is still having problems with attachments, let me know:

a) Who sent the message
b) The subject line
c) The date / time stamp on the message

Send these to me via *private mail*, not on list.  I do try and check my
email on a regular basis, at *least* once a day.  And I *will* get back to
you.  Sometimes it might take a day or two, but I will.
-- Mike Werner  KA8YSD   | He that is slow to believe anything and
                     | everything is of great understanding,
'91 GS500E            | for belief in one false principle is the
Morgantown WV         | beginning of all unwisdom.



part 2 233 bytes content-type:application/pgp-signature (decode)

part 3 154 bytes
--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads


More... (looser matching)
- Last day of these posts
- In 2000 , 2001 only
- Today
- New search...