Quick question. We are using both IMAP and POP#. Question : how can you avoid retrieving an e-mail that has been already retrieved? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism If you want to catch something, running after it isn't always the best way. -Lois McMaster Bujold
Am 10.02.2015 um 16:35 schrieb The Doctor:
Quick question.
We are using both IMAP and POP#.
Question : how can you avoid retrieving an e-mail that has been already retrieved?
by just rsync the complete data from the old to the new server
- first rsync hot while servicers running
- stop services
- second rsync only transfer the differences
- DNS and/or IP change
- start servcies on the new server
the client don't know anything about that
Reindls close, but he omitted the fact that if changing IP, you better shorten the TTL to about 5 mins - 24 hours before you do anything, assuming your default DNS TTL if 24 hrs as most are, if you use longer, than you need to wait that time.
then after a few hours after the change if everythings good, reset your TTL back to 86400 or 1D
On 2/11/15, Reindl Harald h.reindl@thelounge.net wrote:
Am 10.02.2015 um 16:35 schrieb The Doctor:
Quick question.
We are using both IMAP and POP#.
Question : how can you avoid retrieving an e-mail that has been already retrieved?
by just rsync the complete data from the old to the new server
- first rsync hot while servicers running
- stop services
- second rsync only transfer the differences
- DNS and/or IP change
- start servcies on the new server
the client don't know anything about that
participants (3)
-
Nick Edwards
-
Reindl Harald
-
The Doctor