We're looking into using dbmail in our existing web app (http://oprius.com). Because our app is a CRM type of thing, we want to associate emails with other rows in the database (think associating emails with contacts).
We're using Postgres as our backend. I've done a bunch of searching on the user and dev mailing list related to authentication as well as associating extra data to emails. I have a couple comments and a couple of questions. This is more of a brainstorm than anything else, so please feel free to pipe up. We use a different table setup for authentication. I know that I can write my own authentication functions and base them off of authsql.c to support this. We want to be able to archive all emails even if the user deletes them from the IMAP server, because we don't want the users to lose conversation history even if they're "deleters". It'd be nice if these emails were just stored in the same tables as existing emails and just never shown by the IMAP server. I've noticed that dbmail doesn't delete emails until the maintenance script is run. I don't know exactly how this works though, could someone explain it? We might be able to use that... My biggest concern is, if contacts and extra data is associated with an email, what happens when the email is moved into a different folder? I know that IMAP doesn't have a move command, so we lose the dbmail_message row/id. Because there's a slight possibility that two people using our system could get the same email, we can't depend on the dbmail_physmessage being unique per user. Has anyone thought of how dbmail should act if an app developer wants to add extra fields/data related to an email? Jason
signature.asc
Description: PGP signature
