RE: The true number of messages in a folder
Thanks. I'll just have to incorporate the current FAI's into my script for now. I don't fancy learning EWS at the moment :) From: bounce-9578404-8066...@lyris.sunbelt-software.com [mailto:bounce-9578404-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 29 January 2013 17:35 To: MS-Exchange Admin Issues Subject: RE: The true number of messages in a folder I think you will have to use EWS and exclude FAIs. Sent from my Windows Phone From: Sobey, Richard A Sent: 1/29/2013 12:31 PM To: MS-Exchange Admin Issues Subject: The true number of messages in a folder I've been asked to write a very simple script to monitor the number of items in the Inbox of a particular mailbox, and email an alert if this number goes above a threshold. Works perfectly. The problem is, using Outlook, the Inbox is empty. Using Get-MailboxFolderStatistics, there are 10 items in the mailbox. (Using my own mailbox as another example, Outlook says 8257, Powershell says 8340). I understand there could be hidden messages, or other things that may contribute to this, but is there any way I can query the number of actual messages that the user would see? Thanks Richard --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Been a long day today, but I won...
Good investigating skills :) I'm vulnerable to a quick restart of servers, but if it hasn't worked the first time, don't bother doing it again! Event logging and a clear head makes it much easier. -Original Message- From: bounce-9578542-8066...@lyris.sunbelt-software.com [mailto:bounce-9578542-8066...@lyris.sunbelt-software.com] On Behalf Of Kurt Buff Sent: 30 January 2013 06:42 To: MS-Exchange Admin Issues Subject: Been a long day today, but I won... So, it's month end, and our UK office is noticing that emails are not processing outbound from their office. All of their emails come through the US server, to be delivered wherever, and there are some big emails (4-8mbytes) with proposals and orders and such, and they're getting desperate. Lots of little emails are stuck in queue too, though if left alone they seem to trickle out, while the big messages go to retry status. It's already been a long day for me, having been woken up at 3am because they switched over to a new DSL provider, and couldn't log into the router to set up the PPOA configuration. (pay attention - that's a clue...) While I'm trying to troubleshoot this, the nominal IT manager above me is freaking out and deleting messages from the outbound queue on the UK Exchange server, restarting services multiple times, rebooting the UK server, and generally showing all of the patience and investigative skill of a 4yo. I leave the office at 18:00 to pick up my son at daycare, and arrive home and start ignoring everything else except the problem with Exchange. (I have a very good wife, and I deeply appreciate her patience with me!) I get frustrated, and turn up logging on a bunch of Exchange services, then bounce both the UK and US servers remotely, just so I have a clean starting point in the logs. Finally I notice a 4000 message from MSExchangeTransport on the US server (along with some 4006 messages from the same source on the UK server), and hit paydirt. EventID.net turns up reference to MTU sizes. I adjust the firewall in our UK office from 1500 to 1450, and transport of my test message with a 12mbyte text attachment flies through. I test once more with the same attachment, just to be sure. Success. I am now going to bed. Good night. Kurt PS - I'll turn down the logging tomorrow, when I have a few minutes to breathe at work. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Been a long day today, but I won...
Sweet. Congratulations Kurt! -Original Message- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Wednesday, January 30, 2013 12:42 AM To: MS-Exchange Admin Issues Subject: Been a long day today, but I won... So, it's month end, and our UK office is noticing that emails are not processing outbound from their office. All of their emails come through the US server, to be delivered wherever, and there are some big emails (4-8mbytes) with proposals and orders and such, and they're getting desperate. Lots of little emails are stuck in queue too, though if left alone they seem to trickle out, while the big messages go to retry status. It's already been a long day for me, having been woken up at 3am because they switched over to a new DSL provider, and couldn't log into the router to set up the PPOA configuration. (pay attention - that's a clue...) While I'm trying to troubleshoot this, the nominal IT manager above me is freaking out and deleting messages from the outbound queue on the UK Exchange server, restarting services multiple times, rebooting the UK server, and generally showing all of the patience and investigative skill of a 4yo. I leave the office at 18:00 to pick up my son at daycare, and arrive home and start ignoring everything else except the problem with Exchange. (I have a very good wife, and I deeply appreciate her patience with me!) I get frustrated, and turn up logging on a bunch of Exchange services, then bounce both the UK and US servers remotely, just so I have a clean starting point in the logs. Finally I notice a 4000 message from MSExchangeTransport on the US server (along with some 4006 messages from the same source on the UK server), and hit paydirt. EventID.net turns up reference to MTU sizes. I adjust the firewall in our UK office from 1500 to 1450, and transport of my test message with a 12mbyte text attachment flies through. I test once more with the same attachment, just to be sure. Success. I am now going to bed. Good night. Kurt PS - I'll turn down the logging tomorrow, when I have a few minutes to breathe at work. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Allow anonymous on default Receive Connector?
I enable anonymous on the default receive connector where appropriate If I'm creating an additional receive connector (e.g. anonymous relay) I don't usually use a different IP, I just specify the address ranges (though make sure that doesn't include other Exchange servers or hosts that should use the default receive connector. Steve From: Mayo, Bill [mailto:bill.m...@pittcountync.gov] Sent: 30 January 2013 14:04 To: MS-Exchange Admin Issues Subject: Allow anonymous on default Receive Connector? Moving from Exchange 2003 to 2010. We have an email appliance on the perimeter. I am at the stage where I need to change the mail flow to bypass the 2003 server(s). I have found several migration guides that indicate to simply check the box to allow Anonymous access on the default receive connector on the HT box(es). IIRC, the Exchange training I took had you create a separate receive connector for anonymous access, which would require a separate IP (unless I misunderstand something). The logic I see there would be that I could limit that connector to only accept traffic from desired IP's (e.g. the email appliance and designated internal devices). However, we are using NLB on these servers for CAS functions and it would make life interesting trying to maintain high availability for both. So, the question is, do most folks simply allow Anonymous on the default receive connector, or use a different connector? Bill Mayo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Allow anonymous on default Receive Connector?
You don't want to allow Anonymous on the Default Receive Connectors because they allow all IP's to connect. The better answer is to create a new connector, allow anonymous and specify only the IP's that you are allowing to send. Also, you don't need another IP, Exchange will select the proper connector. Assuming you have more than one HT server role: Be sure HT to HT SMTP is not load balanced, Exchange handles that already. Chuck Robinson ___ Sr. Solutions Architect Microsoft Certified Master: Exchange 2010 MCITP: EA Windows Server 2008 EMC Consulting Mobile: 973-865-0394 chuck.robin...@emc.commailto:chuck.robin...@emc.com www.emc.com/consultinghttp://www.emc.com/consulting Transforming Information Into Business Results From: Mayo, Bill [mailto:bill.m...@pittcountync.gov] Sent: Wednesday, January 30, 2013 9:04 AM To: MS-Exchange Admin Issues Subject: Allow anonymous on default Receive Connector? Moving from Exchange 2003 to 2010. We have an email appliance on the perimeter. I am at the stage where I need to change the mail flow to bypass the 2003 server(s). I have found several migration guides that indicate to simply check the box to allow Anonymous access on the default receive connector on the HT box(es). IIRC, the Exchange training I took had you create a separate receive connector for anonymous access, which would require a separate IP (unless I misunderstand something). The logic I see there would be that I could limit that connector to only accept traffic from desired IP's (e.g. the email appliance and designated internal devices). However, we are using NLB on these servers for CAS functions and it would make life interesting trying to maintain high availability for both. So, the question is, do most folks simply allow Anonymous on the default receive connector, or use a different connector? Bill Mayo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Allow anonymous on default Receive Connector?
Okay, I think my confusion about the different IP comes from the wizard. The wizard doesn't ask about remote IP's, so I will need to create it from PowerShell in order to get the unique combination of a local IP address, port bindings, and remote IP address ranges. From: Robinson, Chuck [mailto:chuck.robin...@emc.com] Sent: Wednesday, January 30, 2013 9:15 AM To: MS-Exchange Admin Issues Subject: RE: Allow anonymous on default Receive Connector? You don't want to allow Anonymous on the Default Receive Connectors because they allow all IP's to connect. The better answer is to create a new connector, allow anonymous and specify only the IP's that you are allowing to send. Also, you don't need another IP, Exchange will select the proper connector. Assuming you have more than one HT server role: Be sure HT to HT SMTP is not load balanced, Exchange handles that already. Chuck Robinson ___ Sr. Solutions Architect Microsoft Certified Master: Exchange 2010 MCITP: EA Windows Server 2008 EMC Consulting Mobile: 973-865-0394 chuck.robin...@emc.commailto:chuck.robin...@emc.com www.emc.com/consultinghttp://www.emc.com/consulting Transforming Information Into Business Results From: Mayo, Bill [mailto:bill.m...@pittcountync.gov] Sent: Wednesday, January 30, 2013 9:04 AM To: MS-Exchange Admin Issues Subject: Allow anonymous on default Receive Connector? Moving from Exchange 2003 to 2010. We have an email appliance on the perimeter. I am at the stage where I need to change the mail flow to bypass the 2003 server(s). I have found several migration guides that indicate to simply check the box to allow Anonymous access on the default receive connector on the HT box(es). IIRC, the Exchange training I took had you create a separate receive connector for anonymous access, which would require a separate IP (unless I misunderstand something). The logic I see there would be that I could limit that connector to only accept traffic from desired IP's (e.g. the email appliance and designated internal devices). However, we are using NLB on these servers for CAS functions and it would make life interesting trying to maintain high availability for both. So, the question is, do most folks simply allow Anonymous on the default receive connector, or use a different connector? Bill Mayo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Allow anonymous on default Receive Connector?
Do you have a firewall that limits incoming port 25 and outgoing port 25? If so, then checking the box is just fine. If not, you need to do as Chuck suggests. From: Mayo, Bill [mailto:bill.m...@pittcountync.gov] Sent: Wednesday, January 30, 2013 9:04 AM To: MS-Exchange Admin Issues Subject: Allow anonymous on default Receive Connector? Moving from Exchange 2003 to 2010. We have an email appliance on the perimeter. I am at the stage where I need to change the mail flow to bypass the 2003 server(s). I have found several migration guides that indicate to simply check the box to allow Anonymous access on the default receive connector on the HT box(es). IIRC, the Exchange training I took had you create a separate receive connector for anonymous access, which would require a separate IP (unless I misunderstand something). The logic I see there would be that I could limit that connector to only accept traffic from desired IP's (e.g. the email appliance and designated internal devices). However, we are using NLB on these servers for CAS functions and it would make life interesting trying to maintain high availability for both. So, the question is, do most folks simply allow Anonymous on the default receive connector, or use a different connector? Bill Mayo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Allow anonymous on default Receive Connector?
10-4 and thanks to all that responded. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, January 30, 2013 10:41 AM To: MS-Exchange Admin Issues Subject: RE: Allow anonymous on default Receive Connector? Do you have a firewall that limits incoming port 25 and outgoing port 25? If so, then checking the box is just fine. If not, you need to do as Chuck suggests. From: Mayo, Bill [mailto:bill.m...@pittcountync.gov] Sent: Wednesday, January 30, 2013 9:04 AM To: MS-Exchange Admin Issues Subject: Allow anonymous on default Receive Connector? Moving from Exchange 2003 to 2010. We have an email appliance on the perimeter. I am at the stage where I need to change the mail flow to bypass the 2003 server(s). I have found several migration guides that indicate to simply check the box to allow Anonymous access on the default receive connector on the HT box(es). IIRC, the Exchange training I took had you create a separate receive connector for anonymous access, which would require a separate IP (unless I misunderstand something). The logic I see there would be that I could limit that connector to only accept traffic from desired IP's (e.g. the email appliance and designated internal devices). However, we are using NLB on these servers for CAS functions and it would make life interesting trying to maintain high availability for both. So, the question is, do most folks simply allow Anonymous on the default receive connector, or use a different connector? Bill Mayo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: OT - Other IT support type lists?
Tammy, I have found the following to be good lists: Here is a good list for AD: http://www.activedir.org/ Here is a good list for Group Policy: http://gpoguy.com/ Greg On Wed, Jan 30, 2013 at 1:39 PM, Tammy George tammy.geo...@acadiau.cawrote: Hello. ** ** I like this list in that the messages arrive in my mailbox by experienced intelligent users. J ** ** Wondering if any of you have recommendations for other IT related lists – i.e. AD/Windows, Sharepoint, VMWare, etc. ** ** Thanks in advance. - Tammy ** ** ** ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: OT - Other IT support type lists?
Hi Tammy. This list has what I would call a sister list named NT Sys Admin - here are links: --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin Don K From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Wednesday, January 30, 2013 12:39 PM Subject: OT - Other IT support type lists? Hello. I like this list in that the messages arrive in my mailbox by experienced intelligent users. J Wondering if any of you have recommendations for other IT related lists – i.e. AD/Windows, Sharepoint, VMWare, etc. Thanks in advance. - Tammy --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
