Now that DBMAIL is 2.0, I was hoping to revisit replacing auto incrementing unique_id's with GUID, global unique id's. We made a lot of progress on this topic when it came up in Sept.
The reason for this is it would allow DBMail to handle multiple servers setup for failover, without the danger of ever having duplicate ID's. In looking at the system, this is the last thing holding me back from setting up a solid mail system with hot failover using MySQL replication. As it stands now it would be possible for duplicate ID's if one box failed. This would be a huge win for DBMail.. there are no open solutions out there that I can find that support this sort of thing well. Including Cyrus. They all require crazy configuration for a real failover solution. With this change DBMail would be able to handle failover out of the box. The basic fact that is necessary for context is that the RFC does not require "increment-only" id's as defined in the current dbmail implemenation. The unique_id's detailed in the below "RFC Overview" but these *can* be guid's. The below are links to previous threads that will get us up to speed on this. STATEMENT ABOUT GUID's for Message ID's http://tinyurl.com/62luv RFC Overview for Message ID's http://tinyurl.com/3jjrm OLD THREAD ABOUT THIS [Dbmail] MySQL Load Balancing & Failover http://tinyurl.com/3m6mf EXAMPLE OF HOWTO GENERATE GUID http://tinyurl.com/4y696 START OF THREAD http://tinyurl.com/6mnu9 Thanks, Kevin Baker
