I'm confused about what you're trying to accomplish. I haven't used
dbmail yet, but I've read up on it and and about to implement a test
version.
When you talk about your "app," where in the mail delivery process are
you forwarding the messages? My understanding is that dbmail is an IMAP
server that implements the LMTP protocol to receive mail from a mail
transport agent like procmail or sendmail. Does your app work by
forwarding messages through an MTA or are you going to dup things in the
database backend? Or something else?
As for the alias/caching scheme you mention, it sounds very complex.
The simplest way of dealing with it would be if dbmail were to check
globally for exact copies of message bodies. It seems like it would be
very expensive in terms of processing time because presumably unindexed
message bodies would have to be checked against potentially millions of
other message bodies.
If you knew you were duping the message bodies, you could give each
large body a unique tag and reference that. However, I doubt that
dbmail does that, and I'm not sure if a plugin or something could be
easily made to do it. Duping the messages on the database would be
easy. The hard part would be hooking into dbmail's IMAP serving mechanism.
Just my take.
On 4/13/2014 10:49 AM, KT Walrus wrote:
I’m working on implementing a mailing list feature in my app. Each user has
their own mailing list with the mailing list recipient addresses stored in my
database. The user can send mail to the mailing list address and the message
would be delivered to each recipient address for the list.
I would like to change the To: header from the mailing list address to the
individual recipient address for each copy of the message delivered (and add a
Reply-To: header to use for replying to the message to the group). Basically,
I don’t want recipients to see the original mailing list address or other
recipient addresses in their email.
My question is:
If I change the To: header and use dbmail-deliver to deliver each changed
message, will all copies of the messages be efficiently stored (given that each
copy has a different To: header)?
Also, should I change the Message-Id: header in each copy of the message before
using dbmail-deliver to send a copy of the message to an individual recipient?
Does changing To: or Message-Id: affect storing of attachments? I only want
the attachment stored once regardless of the number of messages it is attached
to. I would like the message bodies and unchanged headers be stored only once
regardless of the number of copies for the message.
Or, would it be better to just change the To: header to “Undisclosed
Recipients:” and the message headers and body the same in all the
dbmail-deliver copies?
Kevin
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
