Jesse Norell wrote:
Hello,
<snip>
On the issue of unique_id in general, I think our whole problem was because we added constraints to guarantee that that field actually was unique - that is not necessary, and even arguably wrong. The rfc actually says that a client should be able to handle multiple messages with the same unique id if it's a duplicate message. This consideration may actually come into play if/when there are shared folders, if you can move messages from one folder to a shared folder so... just don't actually force unique_id to be unique. :)
I beleive Roel mentioned that he was changing the database structure in version 2.0, with links to a single message, for performance improvement. This way, there will still only be one message block.
I plan on making one function to generate uuid's (for unique_id or anywhere else, if someone needs them), and then make all the pop3 stuff use it everywhere it currently generates a unique_id (in multiple functions).
Is it the mail sender or the mail receiver that generates the UUID?
Also, with having an /etc/dbmail/ directory, should that be the default location for dbmail.conf? Debian packages already do that, and it's cleaner if there are multiple conf/etc. files.
How many are the configuration files? <snip> Magnus
