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? Details: when I actually throw the switch, some mail will begin going to the new box fairly quickly while some mail from servers using a cached DNS entry for the domain will continue to send to the old box until the cached address expires, which could be a couple of days. Likewise, some users mail program will almost immediately start going to the new box while others may stay on the old box for a couple of days. So the question is is the right answer to just let whatever happens happen for a couple of days, and then when the dust settles reprocess any leftover mail on the old server to get it routed to the new server? The obvious problem with this is the potential for mail that wont be seen for couple of days. Is there a tried and true better way. Thanks. Jerry
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 Subject: Tracking each piece of mail through the system Ive got a situation where some legit mail is being categorized as spam. I run a few of the default spam blockers that come with James. But I cant figure out which one is causing a spam hit. Im familiar with all the various logs. But there doesnt appear to be a single routing log that tracks a note through all the processors/matchers/mailets. Am I missing something? Is there an easy way to enable some sort of tracking log? Thanks. Jerry
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? Thanks. Jerry -Original Message- *From:* J Malcolm [mailto:[EMAIL PROTECTED] *Sent:* Friday, March 19, 2004 3:20 PM *To:* James Users List *Subject:* Tracking each piece of mail through the system Ive got a situation where some legit mail is being categorized as spam. I run a few of the default spam blockers that come with James. But I cant figure out which one is causing a spam hit. Im familiar with all the various logs. But there doesnt appear to be a single routing log that tracks a note through all the processors/matchers/mailets. Am I missing something? Is there an easy way to enable some sort of tracking log? Thanks. Jerry -- Corey A. Johnson Creative Network Innovations http://www.cniweb.net/ 1-800-CNi-5547 ** 1-321-259-1984 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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? Also, for users who are stuck with a cached DNS entry for the old box, theyll continue to come to the old box for a couple of days and not see any of the mail that was forwarded to the new box during that time. Granted, theyll see it in a couple of days, but for time sensitive mail, thats not good. Is there a way around that? Jerry -Original Message- From: Chris Means [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:18 PM To: 'James Users List' Subject: RE: Migrating Server to Another Box/IP Can you redirect traffic from the old IP to the new IP? Seems like it would be the simplest solution. From: J Malcolm [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:14 PM To: James Users List Subject: 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? Details: when I actually throw the switch, some mail will begin going to the new box fairly quickly while some mail from servers using a cached DNS entry for the domain will continue to send to the old box until the cached address expires, which could be a couple of days. Likewise, some users mail program will almost immediately start going to the new box while others may stay on the old box for a couple of days. So the question is is the right answer to just let whatever happens happen for a couple of days, and then when the dust settles reprocess any leftover mail on the old server to get it routed to the new server? The obvious problem with this is the potential for mail that wont be seen for couple of days. Is there a tried and true better way. Thanks. Jerry
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 probably the simplest approach. -Chris From: J Malcolm [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:30 PM To: 'James Users List'; [EMAIL PROTECTED] Subject: 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, Won't it confuse the system? Also, for users who are stuck with a cached DNS entry for the old box, they'll continue to come to the old box for a couple of days and not see any of the mail that was forwarded to the new box during that time. Granted, they'll see it in a couple of days, but for time sensitive mail, that's not good. Is there a way around that? Jerry -Original Message- From: Chris Means [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:18 PM To: 'James Users List' Subject: RE: Migrating Server to Another Box/IP Can you redirect traffic from the old IP to the new IP? Seems like it would be the simplest solution. From: J Malcolm [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:14 PM To: James Users List Subject: Migrating Server to Another Box/IP I am planning to move my domains to another box and another IP address. I'm well aware of the propagation delays when a domain's 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? Details: when I actually throw the switch, some mail will begin going to the new box fairly quickly while some mail from servers using a cached DNS entry for the domain will continue to send to the old box until the cached address expires, which could be a couple of days. Likewise, some users' mail program will almost immediately start going to the new box while others may stay on the old box for a couple of days. So the question is. is the right answer to just let whatever happens happen for a couple of days, and then when the dust settles reprocess any leftover mail on the old server to get it routed to the new server? The obvious problem with this is the potential for mail that won't be seen for couple of days. Is there a tried and true better way. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 to accomplish this without writing a new matcher? thanks --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 is difficult. What I'd really like is a log with a single line per mail item: Date/Time From ToResult Details --- 4/1/04 16:04 [EMAIL PROTECTED][EMAIL PROTECTED]inbox:jwm 4/1/04 16:05 [EMAIL PROTECTED] [EMAIL PROTECTED]spam fail nabl mailet 4/1/04 16:05 [EMAIL PROTECTED] [EMAIL PROTECTED] sent external If something like this doesn't exist, I can write it. But I'd like a little info on where/how to install it. I guess the first question is whether this is even possible or if there are technical issues with the flow processing that would prevent it. (I'm a seasoned java programmer, but haven't dug too deeply into the James inards.) A few suggestions to get me started would be great. (Possibly Corey's code is close to what I need when I receive it). Jerry -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:41 PM To: James Users List Subject: RE: Tracking each piece of mail through the system there doesn't appear to be a single routing log that tracks a note through ll the processors/matchers/mailets. The spool manager log. Turn on DEBUG for it in environment.xml. --- Noel P.S. please don't send HTML e-mails. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 worked without a hitch for us for incoming and outgoiing mail. J Malcolm wrote: I am planning to move my domains to another box and another IP address. I'm well aware of the propagation delays when a domain's 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? Details: when I actually throw the switch, some mail will begin going to the new box fairly quickly while some mail from servers using a cached DNS entry for the domain will continue to send to the old box until the cached address expires, which could be a couple of days. Likewise, some users' mail program will almost immediately start going to the new box while others may stay on the old box for a couple of days. So the question is. is the right answer to just let whatever happens happen for a couple of days, and then when the dust settles reprocess any leftover mail on the old server to get it routed to the new server? The obvious problem with this is the potential for mail that won't be seen for couple of days. Is there a tried and true better way. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 from Computer Associates for $49 that says it'll run on Server 2003. But I'm not familiar with the product (I know CA, but not the product). Is there anything else better/cheaper? $49 is not a big deal if the product will do what I need it to. All I need it for is to pass mail through it and detect virus attachments. Recommendations/Experiences/Education? Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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] class=ToProcessor processor isGoodMail /processor /mailet !-- If condition 'SenderIs' is not met BUT condition 'SubjectIs' is met, send still to isGoodMail -- mailet match=SubjectIs=something class=ToProcessor processor isGoodMail /processor /mailet !-- else, do something (for instance, mark as spam) -- mailet match=All class=ToProcessor processor spam /processor /mailet /processor processor name=isGoodMail mailet match=All class=YourMailet condition yourCondition /condition /mailet !-- Remember to send to 'transport' processor afterwards if you want the mail to be delivered -- /processor --- 'AND' CONDITION --- processor name=root !-- If condition 'SenderIs' is met, send to processor 'isGoodSender' below -- mailet match=[EMAIL PROTECTED] class=ToProcessor processor isGoodSender /processor /mailet !-- else, do something (for instance, mark as spam) -- mailet match=All class=ToProcessor processor spam /processor /mailet /processor processor name=isGoodSender !-- If condition 'SenderIs' is met AND condition 'SubjectIs' is met, use YourMailet to do your specific processing. -- mailet match=SubjectIs=something class=YourMailet condition yourCondition /condition /mailet !-- Remember to send to 'transport' processor afterwards if you want the mail to be delivered -- !-- else, do something (for instance, mark as spam) -- mailet match=All class=ToProcessor processor spam /processor /mailet /processor --- END --- The 'AND' part can be simplified using 'IsNot' type of matchers instead of 'Is', but now you can work on this as you want to meet your expectations. Br, Isaac. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: jueves, 01 de abril de 2004 23:33 To: [EMAIL PROTECTED] Subject: 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 to accomplish this without writing a new matcher? thanks --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
