snootalope
IS-IT--Management
We've been using Exchange 2007 as an Edge Transport/SPAM Filter now for a few weeks.
It's the Beta 2 version running on Windows 2003 SP2.
Last week, incoming emails weren't being delivered right away. In some cases they'd take up to two hours to be delivered to the users mailbox (on an Exchange 2003). While looking at the queues on the Edge server, we couldn't see any messages for the accepted-domain's queue. There were about 10 messages to other domains in there, junk domains, probably NDR's.
Anyway, we finally ended up rebooting the Edge server and all the emails that were hung up (somewhere) were delivered. I thought it was really strange that we couldn't see the messages in the queue though. But, obviously something on the 2007 Edge server had them backed up since the reboot cured it. All outgoing email was just fine, of course it bypasses the Edge server for outbound email though.
Anyone else experienced this? There isn't a setting to change the maximum number of connections is there? That's the only thing I could think of...
It's the Beta 2 version running on Windows 2003 SP2.
Last week, incoming emails weren't being delivered right away. In some cases they'd take up to two hours to be delivered to the users mailbox (on an Exchange 2003). While looking at the queues on the Edge server, we couldn't see any messages for the accepted-domain's queue. There were about 10 messages to other domains in there, junk domains, probably NDR's.
Anyway, we finally ended up rebooting the Edge server and all the emails that were hung up (somewhere) were delivered. I thought it was really strange that we couldn't see the messages in the queue though. But, obviously something on the 2007 Edge server had them backed up since the reboot cured it. All outgoing email was just fine, of course it bypasses the Edge server for outbound email though.
Anyone else experienced this? There isn't a setting to change the maximum number of connections is there? That's the only thing I could think of...