Re: Still screwing up References: (was Re: Job: I'm looking for one..)

2001-03-29 Thread Dave Cross

At Thu, 29 Mar 2001 11:08:44 +0100, [EMAIL PROTECTED] wrote:
 On Wed, 28 Mar 2001 08:02:39 -0500 (EST), Dave Cross wrote:
  At Wed, 28 Mar 2001 12:34:41 +0100, Simon Cozens [EMAIL PROTECTED]
  wrote:
   Message-ID: [EMAIL PROTECTED]
  
   On Wed, Mar 28, 2001 at 12:02:48PM +0100, alex wrote:
Message-ID: [EMAIL PROTECTED]
 
 But look at your headers:
  References: [EMAIL PROTECTED]
   [EMAIL PROTECTED] 
 
 Where's [EMAIL PROTECTED], Dave?

You're right, the referencing is a bit screwed up. I'll take a look at
it today.

Dave...
[who handily has his copy of "Programming Internet Email" on his desk]



Re: Still screwing up References: (was Re: Job: I'm looking for one..)

2001-03-29 Thread Mark Fowler

On Thu, 29 Mar 2001, Dave Cross wrote:

 You're right, the referencing is a bit screwed up. I'll take a look at
 it today.

Your webmail CC is screwed up too.  On my mails there's now new line after
the Cc: so I get a line that says 

Cc: X-Mailer: foo 

which my mail client (PINE) wants to reply to...

Later.

Mark.

-- 
print "\n",map{my$a="\n"if(length$_6);' 'x(36-length($_)/2)."$_\n$a"} (
   Name  = 'Mark Fowler',Title = 'Technology Developer'  ,
   Firm  = 'Profero Ltd',Web   = 'http://www.profero.com/'   ,
   Email = '[EMAIL PROTECTED]',   Phone = '+44 (0) 20 7700 9960'  )








Re: Still screwing up References: (was Re: Job: I'm looking for one..)

2001-03-29 Thread pmh

On Thu, 29 Mar 2001 11:17:17 +0100 (BST), Mark Fowler wrote:
 On Thu, 29 Mar 2001, Dave Cross wrote:
 
  You're right, the referencing is a bit screwed up. I'll take a look at
  it today.

Actually, that message was OK.


 Your webmail CC is screwed up too.  On my mails there's now new line after
 the Cc: so I get a line that says 
 
 Cc: X-Mailer: foo 
 
 which my mail client (PINE) wants to reply to...

That's a bug in PINE, then. There is actually a newline after Cc:, but like some other 
parsers (including an early version of mine), PINE can't cope with an empty field.

MIME::Parser does something strange, too: with empty fields, -get_all returns either 
('') or (undef) (I can't remember which), but with non-empty fields, -get_all returns 
the contents with newlines intact, confusing things immensely for formatting code.

-- 
Peter Haworth   [EMAIL PROTECTED]
"My own writing [...] is of such high quality that it's almost a new media in
 itself. There is writing, and there is My Writing. UltraWriting. Writing++.
 Object-orientated writing with full pre-emptive multi-tasking running at
 1000 rpm with a 20ms seek time, at a reasonable price (credit available)."
-- Ashley Pomeroy