[courier-users] Question about storage architecture? Hardlinks for multiple deliveries?

permalink · #1 (**permalink**) 03-05-2005

This is a multi-part message in MIME format.

------=_NextPart_000_079B_01C52175.9384EEA0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

I did some googling - I thought this idea had come up before can't see it
though - we were reviewing the number of messages on our system with
multiple recipients and came up with more than a few - my understanding is
that Gmail uses a hardlink-like system to basically reference count messages
received - saves on storage demands and makes their marketing needs easier.

Could something similar be accomplished with courier (not the marketing -
just the storage savings!)

I'm not expecting an instant change - now or ever - just throwing out the
idea to consider the relative merits and difficulties.

In our case we have condense our maildrop processing into maildroprc - users
don't run custom scripts - conceivably a single message could be delivered
to ALL recipients instead of a copy for each. This would reduce processing
and storage demands drastically - I see a lot of difficulties to be overcome
just curious what people think.

Thanks!

m/

------=_NextPart_000_079B_01C52175.9384EEA0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-CA link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

I did some googling – I thought this =
idea had
come up before can’t see it though  – we were reviewing =
the
number of messages on our system with multiple recipients and came up =
with more
than a few – my understanding is that Gmail uses a hardlink-like =
system
to basically reference count messages received – saves on storage =
demands
and makes their marketing needs =
easier…<o:p></o:p>

<o:p> </o:p>

Could something similar be accomplished with =
courier
(not the marketing – just the storage =
savings!)<o:p></o:p>

<o:p> </o:p>

I’m not expecting an instant change =
– now
or ever – just throwing out the idea to consider the relative =
merits and
difficulties…<o:p></o:p>

<o:p> </o:p>

In our case we have condense our maildrop =
processing
into maildroprc – users don’t run custom scripts –
conceivably a single message could be delivered to ALL recipients =
instead of a
copy for each. This would reduce processing and storage demands =
drastically –
I see a lot of difficulties to be overcome just curious what people =
think.<o:p></o:p>

<o:p> </o:p>

Thanks!<o:p></o:p>

<o:p> </o:p>

m/<o:p></o:p>

</div>

</body>

</html>

------=_NextPart_000_079B_01C52175.9384EEA0--

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode