Simon Cocking wrote: >>> >>>Has anyone contemplated modifying Courier to support the storage of >>>messages in SQL tables rather than Maildirs? >>> >>Why? Give me a logical reason other than "it sounds cool." > > Two words -- replication and redundancy. We already have systems in > place which make use of replicated MySQL databases for load-balancing and > redundancy.
I'll have to admit, it does sound cool. But I can't get much beyond that point. You can replicate the mail for redundacy to another system or folder or whatever using a .courier file and maildrop or procmail. It seems to me the ultimate goal is to replicate not just the mail, but the state of the mail back and forth. So your message may flow into server A and then get replicated to server B. Then, the user deletes half of the messages in a session with server B and those messages get deleted from server A (hopefully before the user carries out another session with server A). Does MySQL do all that for you? > If there's an easier way, I'm all ears :o) > >>Impossible. > > Hmm.. I like a challenge :o) Well, to get it into the database, you could just setup a .courier file to pipe the mail into your sql-loading app. The hard part would be getting the IMAP and POP servers to look there. And any other application. The think I like about Maildir is that mutt and other things also know how to read it. -andy _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
