Simon Cocking writes: > The beauty of using SQL as a message back-end would be that you could set > up an array of SMTP/POP/IMAP servers in a DNS round-robin arrangement, > and users could hit any one of them at any time and it would appear to > them to be the same server. Need more horsepower? Just add a new server > to the pool.
Fancy that? That's exactly how at least half a dozen ISPs I know of have their iron set up. And they don't need an SQL server to do that. > Need better availability? Distribute your servers over > multiple physical sites with different bandwidth providers. Want Just add more servers. You don't need a bloated SQL monster to do that. > centralised stats & reporting? It's all *already* in the database. Or, /var/log/messages. > Plus, user management is just an SQL query away. All without a central Or a mkdir/rmdir. > point of failure. Right. Words to live by: the more you overthink the plumbing, the easier it becomes to back up the drain. -- Sam _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
