Bonus points for automagically stripping out one-party contracts
tagged on the end of e-mails.
Given predictable positioning and characteristic keywords this
probably isn't such an impossible task.
-Bill
___
gnhlug-discuss mailing list
On Tue, Oct 7, 2008 at 11:50 PM, [EMAIL PROTECTED] wrote:
some combination of procmail, base64(1), demoroniser, lynx -dump,
Is that a real program name, demoroniser? LOLI'm having fun
trying to imagine just what a program named demoroniser could do!
correct moronic and gratuitously
On Wed, Oct 8, 2008 at 1:03 AM, Ric Werme [EMAIL PROTECTED] wrote:
Who invented BASE64 anyway, when uuencoding work just fine already?
According to what I find on the web, BASE64 is portable across more
character sets.
On Tue, Oct 7, 2008 at 11:53 PM, Brian Chabot [EMAIL PROTECTED] wrote:
From: Ben Scott [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-2022-jp
Uhh, Ben, is there a reason you're using a Japanese character set here?
I wasn't, intentionally. I had cut-and-pasted the White Square
from
On Wed, Oct 08, 2008 at 03:09:47PM +, [EMAIL PROTECTED] wrote:
From: Ric Werme [EMAIL PROTECTED]
Date: Wed, 8 Oct 2008 01:03:01 -0400 (EDT)
Cc: Greater NH Linux User Group gnhlug-discuss@mail.gnhlug.org
Who invented BASE64 anyway, when uuencoding work just fine already?
How many
On Wed, Oct 8, 2008 at 11:09 AM, [EMAIL PROTECTED] wrote:
From: Ric Werme [EMAIL PROTECTED]
Date: Wed, 8 Oct 2008 01:03:01 -0400 (EDT)
Cc: Greater NH Linux User Group gnhlug-discuss@mail.gnhlug.org
[snip]
I went to a job interview at a high-tech firm in Durham, once. The
guy interviewing
On Wed, Oct 8, 2008 at 11:09 AM, [EMAIL PROTECTED] wrote:
From: Ric Werme [EMAIL PROTECTED]
Date: Wed, 8 Oct 2008 01:03:01 -0400 (EDT)
Cc: Greater NH Linux User Group gnhlug-discuss@mail.gnhlug.org
[snip]
I went to a job interview at a high-tech firm in Durham, once. The
guy interviewing
Hi list,
Recent discussion made me curious: Assume we have someone using a
very old version of an MUA (Mail User Agent, like /bin/mail or Pine)
-- one that is unaware of MIME, the BASE64, and quoted-printable
encodings, or HTML mail. Assume that, for whatever reason, they are
unwilling or
On Oct 7, 2008, at 12:08, Ben Scott wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
* Replace any common Unicode characters with ASCII equivilents
* Replace unhandled non-ASCII characters with an ASCII text
representation
* When a plain text body alternative is
On Tue, Oct 7, 2008 at 12:08 PM, Ben Scott [EMAIL PROTECTED] wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
This should be decode to 8-bit clean plain text.
* Replace any common Unicode characters with ASCII equivilents
* Replace unhandled non-ASCII characters with an
On Tue, Oct 7, 2008 at 3:10 PM, Roger H. Goun [EMAIL PROTECTED] wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
This should be decode to 8-bit clean plain text.
Nope. Not if you're talking strict RFC-821/822 compliance. The
specs say ASCII. ASCII is properly a 7-bit
2008/10/7 Ben Scott [EMAIL PROTECTED]:
On Tue, Oct 7, 2008 at 3:10 PM, Roger H. Goun [EMAIL PROTECTED] wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
This should be decode to 8-bit clean plain text.
Nope. Not if you're talking strict RFC-821/822 compliance. The
On Oct 7, 2008, at 12:08, Ben Scott wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
* Replace any common Unicode characters with ASCII equivilents
* Replace unhandled non-ASCII characters with an ASCII text
representation
* When a plain text body alternative is
On Tue, Oct 7, 2008 at 5:29 PM, Roger H. Goun [EMAIL PROTECTED] wrote:
No. In the general case, you have been handed a BASE64 or
quoted-printable encoding of random 8-bit data. ... The first
step is to remove the encoding, leaving unencoded 8-bit
data, not 7-bit data.
Ah, I see where our
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ben Scott
Sent: Tuesday, October 07, 2008 7:56 PM
To: Greater NH Linux User Group
Subject: Re: Converting HTML and MIME to plain text mail
* Handle MIME file attachments
Depending on the situation
Date: Tue, 7 Oct 2008 12:08:19 -0400
From: Ben Scott [EMAIL PROTECTED]
* When a plain text body alternative is provided, strip any other body
alternatives
* Render HTML to plain text, when only an HTML body is provided
* Strip any remaining MIME headers
Hm. Maybe:
* Convert to ASCII as
Ben Scott wrote:
From: Ben Scott [EMAIL PROTECTED]
To: Greater NH Linux User Group gnhlug-discuss@mail.gnhlug.org
Subject: Re: Converting HTML and MIME to plain text mail
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset=iso
2008/10/7 Ben Scott [EMAIL PROTECTED]:
On Tue, Oct 7, 2008 at 3:10 PM, Roger H. Goun [EMAIL PROTECTED] wrote:
* Decode BASE64 or quoted-printable to 7-bit clean plain text
This should be decode to 8-bit clean plain text.
Nope. Not if you're talking strict RFC-821/822 compliance.
...
18 matches
Mail list logo
