On Tue, Nov 18, 2003 at 12:46:30PM -0600, Gary Murphy wrote: > <snip> > For a more radical storage saving approach we could consider storing only > one copy of a message for all recipients within the database. This is the > approach Oracle uses for its email package. My users are insisting on this > so, I am already working to make it happen. However, the change will > require a large number of the base db_ methods be changed, one or two new > recipient delivery db_ methods created, one table added but physmessage can > be removed, and delivery code modified to store only one copy of the message > in messages and messagblks. Finally, dbmail-smtp needs to be called only > once with a list of all database recipients or a generic database-to address > and recipients contained within the header, which will have to be parsed.
If you're working on this, please allow multiple username/mailbox combinations, e.g. dbmail-smtp user1:/lists/somelist user2 user3:/spam user4:/INBOX Even better might be to allow the same message to be delivered to different users by separate invocations of dbmail-smtp and only storing a single copy of the message body based on Message-ID, but separate versions of headers for each user allowing headers such as Envelope-To without exposing bcc'd recipients. Even more ambitious would be to parse MIME and store only a single copy of unique MIME attachments so users who forward around 10MB files don't take up so much space. xn
