"Tim Streater" wrote |

| Content Disposition
| *can* be used to send creation/modification date.
| I've never actually seen it done. It's certainly not
| required.
|
| I never said it was required. I added it to my email client because I'd
| seen those fields arriving in some content-disposition headers.
|

That's very different from the idea that an email
client is "rubbish" if it doesn't do it. I have OE and
TBird here. Neither one sets to mod date. Not that
I'd mind if they did, but I can't say I'd ever noticed
one way or the other. If someone sends me a photo
of their new baby it's not particularly relevant to
me what day they took the photo.

| And sending creation date would make
| no sense. Your copy is created when you get it,
| just as a file copied across partitions has a creation
| date corresponding to when it was copied.
|
| No it doesn't. I just copied a file to my desktop from another Mac on
| the local LAN (by drag and drop), and the copy on my desktop has the
| same creation date as the original. Which is what I'd expect any
| sensible system to do.
|

And it's a copy, not a link? Maybe that's the
Mac standard. On Windows a copy has the same
modification date but a different creation date.

To give it the same creation time is to say that
both files are the same file; that there are no
actual copies and therefore the copy
was never actually created. Thus it's only an
alternate manifestation of the same, exact item.
Sounds like some pretty funky, existential hocus
pocus to me.