Exchange Emails - Pending
-
I'm guessing you don't get an NDR back when it fails
-
@brianlittlejohn Nothing is generated. The user shows it as a sucessfully sent email. It's not until 48 hours later that they receive a failed to deliver to all recipients. Basically it gets pushed from the client to the server, then it just sits on the server.
-
@brianlittlejohn said:
I'm not sure. I'm running Exchange 2010, Outlook 2016 and Meeting Requests are sending like they should to distribution groups.
I'm running this same setup, but I can't accept meeting requests for conference rooms - can you?
*Edit - I am behind on Rollup patches.
-
@Dashrender On my room and resource mailboxes I had to enable auto accept meeting requests. This helps...
http://blogs.technet.com/b/exchange/archive/2009/02/26/3407028.aspx
Its exchange 2007, but I think the commands are the same.
-
@Dashrender Oddly enough, this is for a conference room. The resource has its own calendar. I took that out of the mix, if that helps you at all. I pulled everyone but me and her out of the distribution list. Trying it shortly...
-
Here is a better guide.
http://exchangeserverpro.com/exchange-server-2010-room-mailboxes-step-by-step-guide/
-
I don't want auto accept on my conference room. It's managed by the secretary.
-
@Dashrender We have a worthless secretary, so If it is open on the calendar it gets accepted. Is your secretary getting the meeting requests for the conference room?
-
@brianlittlejohn said:
@Dashrender We have a worthless secretary, so If it is open on the calendar it gets accepted. Is your secretary getting the meeting requests for the conference room?
yep, her and I both get them. I only deal with them when she it out of the office.
-
Our secretary is a really good one! Lives up to the title of old. She's our Secretary of State
-
What Service Pack and Rollup are you running?
-
@brianlittlejohn I've gone through Installed Updates but can't find any relevant information as to the Service Pack or Rollup. Any tips on finding that info?
-
@BBigford Its based on the build number.
https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx
-
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
-
@BBigford Look at the table on the link I gave... The build number should be longer and start 15.* It has the powershell command to run to get it on the page as well.
-
What I meant to say, is I went through the list in that link you sent. But Exchange 2013 all start with 15.x
-
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
-
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
-
@BBigford
Last Line in 2013 TableRelease to Manufacturing (RTM) version of Exchange Server 2013
December 3, 2012
15.00.0516.032 -
@brianlittlejohn said:
@BBigford
Last Line in 2013 TableRelease to Manufacturing (RTM) version of Exchange Server 2013
December 3, 2012
15.00.0516.032
Oh, I overlooked the last of the numbers. My fault. I was only looking at the first of them.
