Its the rbl lookup on Exchange's anti-spam feature that for some reason is taking insanely long, the minute I disable RBL lookups, messages come in immediately. Just don't know why it suddenly started , I have been using the same RBLs for years
Jean-Paul Natola From: [email protected] Date: Sun, 21 Jul 2013 14:59:30 -0700 Subject: Re: [NTSysADM] RE: Week long shutdown- HELP To: [email protected] This sounds like greylisting. Is the delay per-domain, and does it go away after the initial delay? -- Espi On Sun, Jul 21, 2013 at 11:52 AM, J- P <[email protected]> wrote: ok routing is working, but now I have a consistent delay (5 min) from sent time to received, and I have verified the hang on the recipient lookup from the time I type RCPT TO: [email protected] it takes exactly 5 minutes before it returns Recipient OK Not sure why a ISP change would affect that as it is my understanding the recipient lookup is an internal function, and I did check that exchange is using the correct GC and all DC's are running , so I am bit stumped Any other pointers would be greatly appreciated Jean-Paul Natola From: [email protected] To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown- HELP Date: Sun, 21 Jul 2013 09:25:00 +0000 Ramp up the logging on your SMTP receive connectors. I'd use Powershell - play with Get- and Set-EventLogLevel on your HT servers. Have any of your IP addresses changed? New firewall rules? Do you get an NDR if you just send an email from Google or whatever instead of using the RCA? If so what does it say? What happens if you try to submit an email after manually telnetting to port 25: EHLO yourhost MAIL FROM: your.email@address RCPT TO: your.email@address Subject: Test Data . (Hopefully you're familiar with SMTP commands and this makes sense). Good luck! From: [email protected] [[email protected]] on behalf of J- P [[email protected]] Sent: 21 July 2013 04:53 To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown- HELP So everything went well (sort of) but for some reason, exchange (2010) will not accept mail from outside- here's the smtp connectivity test results; Delivery of the test email message failed. Additional Details The server returned status code -1 - The operation has timed out. Exception details: Message: The operation has timed out. Type: System.Net.Mail.SmtpException Stack trace: at System.Net.Mail.SmtpClient.Send(MailMessage message) at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally() but yet I can telnet into port 25 and exchange is waiting and ready- not sure what is going on Jean-Paul Natola From: [email protected] To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. Date: Sat, 20 Jul 2013 16:22:22 -0700 A friend of mine had to assist with moving a data center. They opened up every system and blew out all the dust. It does add some to the time but just a thought. Steven Peck http://www.blkmtn.org From: [email protected] [mailto:[email protected]] On Behalf Of Webster Sent: Friday, July 19, 2013 10:45 AM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. Don’t they make pads and ointments to help with minions? Thanks Webster From: [email protected] [mailto:[email protected]] On Behalf Of John Cook Sent: Friday, July 19, 2013 12:04 PM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. That’s why I have minions. John W. Cook Network Operations Manager Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Office (352) 244-1610 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, Security+ VSP4, VTSP4 From: [email protected] [mailto:[email protected]] On Behalf Of Webster Sent: Friday, July 19, 2013 12:46 PM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. The entire datacenter by yourself? WOW!!! Even superman –sc wouldn’t attempt that by himself. J Thanks Webster From: [email protected] [mailto:[email protected]] On Behalf Of John Cook Sent: Friday, July 19, 2013 11:32 AM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. You don’t say! Actually this has been a good discussion as I’m moving a Datacenter myself in a month. John W. Cook Network Operations Manager Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Office (352) 244-1610 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, Security+ VSP4, VTSP4 From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Friday, July 19, 2013 12:17 PM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. Jean-Paul Natola From: [email protected] To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. Date: Fri, 19 Jul 2013 13:15:15 +0000 The issue is that everything cools down after being run for so long. Bearings freeze up, electronic connectors contract, etc. And it’s not necessarily just hard drives. Cooling fans, power supplies, etc. Removing them from the chassis won’t change anything and might even make things worse. If you have to move a server, I’d keep everything in place. Again, have good backups and have a few spares handy. -Paul From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, July 18, 2013 8:34 PM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. Maybe a better approach would be to removes the drives from all servers, and drive them down myself? Jean-Paul Natola From: [email protected] Date: Thu, 18 Jul 2013 15:16:04 -0700 Subject: Re: [NTSysADM] RE: Week long shutdown. To: [email protected] I strongly agree regarding the spare drives (or at least preparations for fast acquisition). If a drive is going to fail, its during/after a large physical move. I've seen this happen many times. -- Espi On Thu, Jul 18, 2013 at 12:46 PM, Maglinger, Paul <[email protected]> wrote: Make sure your backups are current. Wouldn’t hurt to have some spare hard drives. We moved our corporate 7 years ago. Only lost 2 drives on separate systems. No data loss. From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, July 18, 2013 11:30 AM To: [email protected] Subject: RE: [NTSysADM] RE: Week long shutdown. That is scary, we are moving to our new office tonight/tomorrow and although its only 1 mile away - now I'm getting nervous... :( Jean-Paul Natola From: [email protected] To: [email protected] Date: Thu, 18 Jul 2013 11:16:28 -0500 Subject: [NTSysADM] RE: Week long shutdown. When we moved into our new data center in 2010 we had several drives in a few older servers and an older SAN that did not spin back up after being shut down to be moved. The equipment was only down for a couple of hours while it was moved between buildings. Those drives had been spinning continuously for several years before the move. Luckily the failed drives were in separate RAID arrays so we didn’t lose any data. Dave From: [email protected] [mailto:[email protected]] On Behalf Of Maglinger, Paul Sent: Thursday, July 18, 2013 11:03 AM To: [email protected] Subject: [NTSysADM] RE: Week long shutdown. The first concern that comes to mind doesn’t involve AD, but rather that sometimes hard drives that have been spinning continuously don’t want to spin back up after they’ve cooled down. -Paul From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Thursday, July 18, 2013 10:37 AM To: [email protected] Subject: [NTSysADM] Week long shutdown. We are shutting our data center down for 7 days to repair the HAVAC/Electrical systems. Long story but it needs to be done this way. Since we are a school district and it is summer we are just going to pull the plug on the network and let that summer staff fend for themselves. I have a secondary MX up with a hold and forward. There are 4 offsite DC’s that could be left running, but they will not be able to talk to each other, their connectivity is via the data center. I am thinking shut them down too. Any issues or concerns that come to mind for a week long downtime for AD? CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to.
