Migrating Server to Another Box/IP

I am planning to move my domains to another box and another IP address. Im well aware of the propagation delays when a domains IP address changes. I need to minimize the disruption to my users and obviously not lose any mail in the process. Is there any best practices for how to do this?

FW: Tracking each piece of mail through the system

Never got a response on this one. Justing bumping it back to the top of stack. Anybody got any suggestions on how to track end to end? Thanks. Jerry -Original Message- From: J Malcolm [mailto:[EMAIL PROTECTED] Sent: Friday, March 19, 2004 3:20 PM To: James Users List

Re: FW: Tracking each piece of mail through the system

I created a Mailet that logs info about any rejection to a MySQL DB. Was pretty straight forward. I can send you the source if you like. Cj J Malcolm wrote: Never got a response on this one. Justing bumping it back to the top of stack. Anybody got any suggestions on how to track end to end?

RE: Migrating Server to Another Box/IP

Do you mean go into every mailbox and set up forwarding? Or is there some way to do it at TCPIP level? If I forward mailboxes individually, what I am going to forward to? My old box is currently configured to be xyz.com. If I say to forward to xyz.com, Wont it confuse the system?

RE: Migrating Server to Another Box/IP

I mean at the TCP/IP level. If both your servers are behind a firewall/NAT device, then you should be able to use that device to forward all traffic destined for one IP to another. It depends upon the hardware/software you're using for the firewall/NAT device but I think it's possible...and

Chaining Matchers

Hi Is it possible to chain a couple of matchers and direct the result in the end to a single mailet? For example, i want to identify the messages from a particular sender with a specific subject and take action on it. So using the built in SenderIs and the SubjectIs matchers, is it possible

RE: Tracking each piece of mail through the system

I've tried looking at the spoolmanager log. It references everything by that long email key requiring backtracking through other logs to find out who it was from and to. And it intermixes many threads of mail as would be expected in a realtime log. But getting the kind of info I need out of it

Re: Migrating Server to Another Box/IP

I've done what you've described for several hundred users when we migrated hosting centers for our Linux servers. What we did is run James on both the old and new servers (in separate JVMs, of course) but using the same backend database (MySQL; over a secure tunnel). Maybe not preferred but it

AntiVirus for Windows Server 2003?

 Slightly off topic... but I need to get an antivirus package to plug into James via the mailet. Norton's cheapest product that'll run on Windows Server 2003 is $269 for 5 licenses (which I don't need). I have a single server. Just currently stuck with Server 2003. I found eTrust antivirus

RE: Chaining Matchers

Hi Srini, I guess you cannot chain matchers as such, but you can accomplish the same with the following in config.xml: --- START --- --- 'OR' CONDITION --- processor name=root !-- If condition 'SenderIs' is met, send to isGoodMail -- mailet match=[EMAIL PROTECTED]