20 messages in org.xml.lists.xml-devRe: [xml-dev] MarkMail: now archiving...
FromSent OnAttachments
Jason HunterNov 26, 2007 11:55 am 
Costello, Roger L.Nov 26, 2007 1:32 pm 
Len BullardNov 26, 2007 5:07 pm 
bryan rasmussenNov 27, 2007 12:59 am 
Elliotte HaroldNov 27, 2007 4:51 am 
Elliotte Rusty HaroldNov 27, 2007 5:00 am 
Len BullardNov 27, 2007 5:56 am 
Jason HunterNov 27, 2007 11:05 am 
Jason HunterNov 27, 2007 12:46 pm 
Elliotte Rusty HaroldNov 27, 2007 6:52 pm 
Edward C. ZimmermannNov 27, 2007 11:41 pm 
Jason HunterNov 28, 2007 12:48 am 
Andrew WelchNov 28, 2007 2:21 am 
Edward C. ZimmermannNov 28, 2007 3:45 am 
John SnelsonNov 28, 2007 4:51 am 
Jason HunterNov 28, 2007 11:34 am 
Edward C. ZimmermannNov 28, 2007 1:12 pm 
Jason HunterNov 28, 2007 3:09 pm 
Elliotte Rusty HaroldDec 7, 2007 4:39 am 
Jason HunterDec 7, 2007 9:38 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [xml-dev] MarkMail: now archiving xml-devActions...
From:Jason Hunter (jhun@acm.org)
Date:Nov 28, 2007 3:09:19 pm
List:org.xml.lists.xml-dev

Edward C. Zimmermann wrote:

Quoting Jason Hunter <jhun@acm.org>:

If you divide 60 Gigs by 4,000,000 emails that's 15k per email. That's bigger than I would have guessed an average email to be, but you have to take into account the full headers and the influence of the (relatively few) binary attachments.

Even with "full headers" I think 15k average message size (excluding attachments) is suspect.

Only on xml-dev could the results of "du -h" against scp'd files be taken into question. :)

A chunk of email headers could-- if one is bothering to clean things up-- be excluded as about the path of email transmission and not content. In a service its not really of interest to anyone how the mail arrived and got bounced around in one's own network--- and often we don't want to even publish such information.

On MarkMail we definitely don't need to show the world the full headers -- but we have found several situations where having the full headers has been useful. Example: Having full Received headers gives you insight to when people are (unintentionally) lying with their Date headers.

My philosophy is to try to tackle whatever representation model is thrown at me. Mail is a model. This way I can throw XML, mail and all kinds of other inputs into a big heap, search them (exploiting their structure), retrieve bits (exploiting their structure for unit of retrieval) and, should I desire, convert on the fly into other representations.. With a semantic crosswalk one can do some really really wacky things :-)

Sounds fun. Where can I see this in action? (Sorry, I don't know your background, so when you say "we can..." I don't know where to look.)

-jh-

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: xml-@lists.xml.org subscribe: xml-@lists.xml.org List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php