Re: enormous DB Traffic using imapsync

On Wed, Dec 26, 2007, Jake Anderson <jakevapourforge.com> said:

>> This issue has been discussed fully and debated to
death several times.
>> This is a good idea for uniqueness, but it won't
work at all for IMAP
>> due to protocol restrictions and client behavior.
Please search the
>> mailing list archives for dbmail and dbmail-dev to
find discussion
>> threads (there are _many_!) on this topic if you
would like further
>> details.
>>
>> Cheers,
>> Aaron
>>   
> Just to check. Replication with offset will work
provided the client 
> only talks to one server yes?
> IE if i have 2 servers A and B and send all clients
with emails A-K to 
> server A and L-Z to server B all will be well? If the
server A goes down 
> then all the clients would be able to re-connect to
server B and 
> continue using their email.
> 
> 
> Its when the client bounces between multiple imap
daemons within the one 
> "session" that issues occur?

All of DBMail's access method, dbmail-smtp, lmtp, imap,
pop3, when they
write a message to a mailbox, they write an IMAP message
sequence number.

If you strictly enforce partitioning of users into a
database cluster,
then you might allow the clusters to cross-replicate safely
just by using
MySQL auto increment offsets. You would have to arrange for
an external
mechanism to do fail-over and continue to ensure that only
one server
handles all interactions with a given user at any given
moment.

I do not recommend this in a production environment. Paul
has an excellent
whitepaper on user partitioning up on dbmail.eu.

Aaron
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail