3D instead of `='

3D instead of `='

[Harry Putnam]

Certain mail I get displays 3D instead of `='.  I recall something
about this being related to old fashioned mail encoding/decoding or
the like but have forgotten the particulars.

At any rate, it hasn't cropped up for a very long time.  But I get
some messages on a mail list, from a  specific poster that contain
them.

Apparently this is happening somewhere before it gets to me.  Can
anyone tell from the full headers and trimmed message why these
particular messages have this problem?

X-From-Line: beginners-return-28688-reader=newsguy.com@perl.org  Sat Jun 22 11:10:04 2002
Return-Path: <beginners-return-28688-reader=newsguy.com@perl.org>
Received: from localhost (localhost [127.0.0.1])
	by reader.local.lan (8.12.3/8.12.3) with ESMTP id g5MIA4wb005929
	for <reader@localhost>; Sat, 22 Jun 2002 11:10:04 -0700
Received: from pop.newsguy.com [216.148.53.72]
	by localhost with POP3 (fetchmail-5.9.0)
	for reader@localhost (single-drop); Sat, 22 Jun 2002 11:10:04 -0700 (PDT)
Received: from onion.perl.org (onion.valueclick.com [64.70.54.95])
	by newsguy.com (8.9.1a/8.9.1) with SMTP id LAA85968
	for <reader@newsguy.com>; Sat, 22 Jun 2002 11:08:04 -0700 (PDT)
Received: (qmail 8973 invoked by uid 1005); 22 Jun 2002 18:11:19 -0000
Mailing-List: contact beginners-help@perl.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:beginners@perl.org>
List-Help: <mailto:beginners-help@perl.org>
List-Unsubscribe: <mailto:beginners-unsubscribe@perl.org>
List-Subscribe: <mailto:beginners-subscribe@perl.org>
Delivered-To: mailing list beginners@perl.org
Received: (qmail 8958 invoked by uid 76); 22 Jun 2002 18:11:18 -0000
Received: from qmailr@zero.sector13.org (HELO zero.sector13.org) (199.105.121.241)
  by onion.perl.org (qpsmtpd/0.07b) with SMTP; Sat Jun 22 18:11:18 2002 -0000
Received: (qmail 2013 invoked by uid 2003); 22 Jun 2002 18:07:38 -0000
Date: Sat, 22 Jun 2002 13:07:38 -0500
From: David T-G <davidtg-perl-beginners@justpickone.org>
To: perl beginners <beginners@perl.org>
Cc: some address
Subject: Re: flatfile to hash
X-Gnus-Mail-Source: directory:/home/reader/spool/
Message-ID: <20020622180737.GK870@justpickone.org>
References: <h9d9hus1cj99n36bmjh9nq2nr5cfeu5ca7@4ax.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ogUXNSQj4OI1q3LQ"
Content-Disposition: inline
In-Reply-To: <h9d9hus1cj99n36bmjh9nq2nr5cfeu5ca7@4ax.com>
User-Agent: Mutt/1.4i
X-UIDL: 2ae8d80604708f685479e09faec02599
X-Spam-Status: No, hits=-2.8 required=5.0 tests=IN_REP_TO,PGP_SIGNATURE_2,PORN_3 version=2.21
X-Spam-Level: 
X-Spama-Scores: D:IN_REP_TO:-4.431 D:PORN_3:0.605 T:-3.826

[The 3D's appearing below are actually `=' in other posts on this
thread]

[...]
Is there a particular reason you suck the whole file into an array before
turning around and spitting the whole thing into a hash?


%20
% foreach (@vs){
% ($name,$value) 3D split(/3D/,$_);
% $sigs{$name}3D$value;}

If this is too slow (particularly if you can get rid of the array suck
step above), you might try manipulating the file itself, which is very
close to a hash declaration of

  %sigs 3D
  {
    $name 3D> $value
  }

Re: 3D instead of `='

[Simon Josefsson]

Harry Putnam <reader@newsguy.com> writes:

> Certain mail I get displays 3D instead of `='.  I recall something
> about this being related to old fashioned mail encoding/decoding or
> the like but have forgotten the particulars.

It is quoted-printable.  The message you forwarded was
multipart/signed, and the message part inside those must be in 7bit
format, so QP is often used.

> Apparently this is happening somewhere before it gets to me.  Can
> anyone tell from the full headers and trimmed message why these
> particular messages have this problem?

Did the MIME body header include the proper Content-Transfer-Encoding:
quoted-printable?

Re: 3D instead of `='

[Harry Putnam]

Simon Josefsson <jas@extundo.com> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> Certain mail I get displays 3D instead of `='.  I recall something
>> about this being related to old fashioned mail encoding/decoding or
>> the like but have forgotten the particulars.
>
> It is quoted-printable.  The message you forwarded was
> multipart/signed, and the message part inside those must be in 7bit
> format, so QP is often used.
>
>> Apparently this is happening somewhere before it gets to me.  Can
>> anyone tell from the full headers and trimmed message why these
>> particular messages have this problem?
>
> Did the MIME body header include the proper Content-Transfer-Encoding:
> quoted-printable?

INcluded below is full headers and body.  Interesting that a `t' on
this message doesn't show the part you asked about. Only C-u g does.
But it looks as if the Transfer Encoding is correct:


X-From-Line: beginners-return-28688-reader=newsguy.com@perl.org  Sat Jun 22 11:10:04 2002
Return-Path: <beginners-return-28688-reader=newsguy.com@perl.org>
Received: from localhost (localhost [127.0.0.1])
	by reader.local.lan (8.12.3/8.12.3) with ESMTP id g5MIA4wb005929
	for <reader@localhost>; Sat, 22 Jun 2002 11:10:04 -0700
Received: from pop.newsguy.com [216.148.53.72]
	by localhost with POP3 (fetchmail-5.9.0)
	for reader@localhost (single-drop); Sat, 22 Jun 2002 11:10:04 -0700 (PDT)
Received: from onion.perl.org (onion.valueclick.com [64.70.54.95])
	by newsguy.com (8.9.1a/8.9.1) with SMTP id LAA85968
	for <reader@newsguy.com>; Sat, 22 Jun 2002 11:08:04 -0700 (PDT)
Received: (qmail 8973 invoked by uid 1005); 22 Jun 2002 18:11:19 -0000
Mailing-List: contact beginners-help@perl.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:beginners@perl.org>
List-Help: <mailto:beginners-help@perl.org>
List-Unsubscribe: <mailto:beginners-unsubscribe@perl.org>
List-Subscribe: <mailto:beginners-subscribe@perl.org>
Delivered-To: mailing list beginners@perl.org
Received: (qmail 8958 invoked by uid 76); 22 Jun 2002 18:11:18 -0000
Received: from qmailr@zero.sector13.org (HELO zero.sector13.org) (199.105.121.241)
  by onion.perl.org (qpsmtpd/0.07b) with SMTP; Sat Jun 22 18:11:18 2002 -0000
Received: (qmail 2013 invoked by uid 2003); 22 Jun 2002 18:07:38 -0000
Date: Sat, 22 Jun 2002 13:07:38 -0500
From: David T-G <davidtg-perl-beginners@justpickone.org>
To: perl beginners <beginners@perl.org>
Cc: zentara <zentara@highstream.net>
Subject: Re: flatfile to hash
X-Gnus-Mail-Source: directory:/home/reader/spool/
Message-ID: <20020622180737.GK870@justpickone.org>
References: <h9d9hus1cj99n36bmjh9nq2nr5cfeu5ca7@4ax.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ogUXNSQj4OI1q3LQ"
Content-Disposition: inline
In-Reply-To: <h9d9hus1cj99n36bmjh9nq2nr5cfeu5ca7@4ax.com>
User-Agent: Mutt/1.4i
X-UIDL: 2ae8d80604708f685479e09faec02599
X-Spam-Status: No, hits=-2.8 required=5.0
	tests=IN_REP_TO,PGP_SIGNATURE_2,PORN_3
	version=2.21
X-Spam-Level: 
X-Spama-Scores: D:IN_REP_TO:-4.431 D:PORN_3:0.605 T:-3.826

--ogUXNSQj4OI1q3LQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

zentara --

2E..and then zentara said...
%20
% Hi,

Hello!


% I'm looking for some clever tricks to get a file
% into hash values.
%20
% The file looks like this.
%20
% 10 past 3 (B)3Dec020e1ff3a4b82125061fbab300cd21
% 10 past 3 (C)3Db840008ed8a11300b106d3e02d00088e
2E..
%20
% I've been using:
%20
% <code>
2E..
% open (VS,"< vs") or die "Cant open signature file", $!; 20
% @vs 3D <VS>;
% chomp @vs;
% close VS;

Is there a particular reason you suck the whole file into an array before
turning around and spitting the whole thing into a hash?


%20
% foreach (@vs){
% ($name,$value) 3D split(/3D/,$_);
% $sigs{$name}3D$value;}

If this is too slow (particularly if you can get rid of the array suck
step above), you might try manipulating the file itself, which is very
close to a hash declaration of

  %sigs 3D
  {
    $name 3D> $value
  }

already (hmmm... should those be () istead of {}?).  Anyway, you could
preprocess your sig file into a perl file that you "require" at scan
runtime and thus only pre-handle it when you get a new sig, or maybe
just suck it in and eval that transformation every time.


Just some thoughts from a novice...  HTH & HAND

:-D
--20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--ogUXNSQj4OI1q3LQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9FLzpGb7uCXufRwARAn/EAJ9csz8Cm7dYEtXHw2zVZY5xpRjCEgCg4e44
hKxwDHxgYZtjPtK8t2CoKCU=
=ItU/
-----END PGP SIGNATURE-----

--ogUXNSQj4OI1q3LQ--

Re: 3D instead of `='

[Raja R Harinath]

Simon Josefsson <jas@extundo.com> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> Certain mail I get displays 3D instead of `='.  I recall something
>> about this being related to old fashioned mail encoding/decoding or
>> the like but have forgotten the particulars.
>
> It is quoted-printable.  The message you forwarded was
> multipart/signed, and the message part inside those must be in 7bit
> format, so QP is often used.

Actually it isn't :-)  The QP mangled form of '=' is '=3D', not '3D'
which the message showed.

>> Apparently this is happening somewhere before it gets to me.  Can
>> anyone tell from the full headers and trimmed message why these
>> particular messages have this problem?
>
> Did the MIME body header include the proper Content-Transfer-Encoding:
> quoted-printable?

Looks like a terminally broken QP encoder.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu

Re: 3D instead of `='

[Harry Putnam]

Raja R Harinath <harinath@cs.umn.edu> writes:

> Actually it isn't :-)  The QP mangled form of '=' is '3D', not '3D'
> which the message showed.

Those two look indentical here..

Re: 3D instead of `='

[Kai Großjohann]

Harry Putnam <reader@newsguy.com> writes:

> Raja R Harinath <harinath@cs.umn.edu> writes:
>
>> Actually it isn't :-)  The QP mangled form of '=' is '3D', not '3D'
>> which the message showed.
>
> Those two look indentical here..

The right form is an equals sign, followed by a three, followed by a
capital d.  The wrong form is missing the equals sign.

Your Gnus seems to delete the equals signs...

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: 3D instead of `='

[Harry Putnam]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 632 bytes --]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> Raja R Harinath <harinath@cs.umn.edu> writes:
>>
>>> Actually it isn't :-)  The QP mangled form of '=' is '3D', not '3D'
>>> which the message showed.
>>
>> Those two look indentical here..
>
> The right form is an equals sign, followed by a three, followed by a
> capital d.  The wrong form is missing the equals sign.
>
> Your Gnus seems to delete the equals signs...

Viewing the above referenced message with C-u g doesn't help either.
I still see '=' is '3D, not '3D'

What might be causing this strange behavior? 

Re: 3D instead of `='

[Raja R Harinath]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> Raja R Harinath <harinath@cs.umn.edu> writes:
>>
>>> Actually it isn't :-)  The QP mangled form of '=' is '3D', not '3D'
>>> which the message showed.
>>
>> Those two look indentical here..
>
> The right form is an equals sign, followed by a three, followed by a
> capital d.  The wrong form is missing the equals sign.
>
> Your Gnus seems to delete the equals signs...

Mine seems to be deleting it too.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu