A relatively new installation (3 weeks) of EX2013 and for the last 2 days, every 4-5 hours or so, inbound mail stops. I have checked the event logs and nothing, no errors show. A test through testexchangeconnectivity.com give the error 421 4.3.2 Service not available.
Whilst a simple restart of the transport service rectifies the issue, I am not sure how to establish what is causing the problem.
Any suggestions?
Question:
User A replies to an Email from User B.
User A gets the email rejected and the error message
"You can't send a message on behalf of this user unless you have permission to do so."
The FORM field has been changed to User B and thus rejected.
I have examined the transaction logs and all appears that user A is trying to send an email on an account that he does not have sufficient rights. Next I check the message itself and sure enough the sender is User. Exchange appears to be behaving normally.
Users both are using Outlook 2010.
What could cause Outlook to change the field? Could it be an issue with the X400LegacyExchangeDN settings for the users?
Cache has been cleared and problem is intermittent. Not all emails replied to from A to B are rejected. Most go through. User doesn't have issue with other users.
Turning off cache resolves issue.
Hi all,
I've added an Exchange 2013 server to an existing domain containing an Exchange 2007 server. All went well and mail flows fine back and forth between 2007 and 2013. I am also able to send an email to an external address from 2013 and it is received. however when i try to reply it never comes back into 2013.
The mailbox i am emailing resides on the 2013 server. What confuses me is that when i send out of 2013 i can see that it uses the send connector on the 2007 server and so flows through it, but it seems as if the 2007 server wont allow itself to relay the return email back through to 2013.
Where should i check in order to get more info? What could the issue be? I dont get any bouncebacks at all. Thanks
Hi Guys
We're using Exchange 2013 and we're having a problem where we're completely unable to send any mails to 1 specific domain. We get bounce backs saying unable to deliver but will keep trying, and eventually get:
Received: from REMOVED by REMOVED(10.0.0.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Dec 201514:33:14 +0000Received: from REMOVED ([::1]) by REMOVED ([::1])with mapi id 15.00.1104.000; Wed, 9 Dec 2015 14:33:14 +0000From: SenderTo: RecipientSubject: RE: BlockingThread-Topic: BlockingThread-Index: AdEyjlFXWf+hfTFkR16j7SdFhr2+0AAADMhQDate: Wed, 9 Dec 2015 14:33:13 +0000Message-ID: REMOVEDReferences: REMOVEDIn-Reply-To: REMOVEDAccept-Language: en-GB, en-USContent-Language: en-USX-MS-Has-Attach: yesX-MS-TNEF-Correlator:x-ms-exchange-transport-fromentityheader: Hostedx-originating-ip: [10.0.1.113]Content-Type: multipart/related; boundary=REMOVED type="multipart/alternative"MIME-Version: 1.0
When checking Exchange Queue Viewer the message in the queue has the error
Last Error: 451 4.7.0 Recipient rejected (R20)
I've removed any identify data from the above.
Have been in touch with the IT guys of the company we're trying to contact and they assure us that they can't see any issues on their side. We don't have any issues sending mail to any other domains.
Do you have any ideas on what may be causing this issue, let me know what other info you need and i will try to provide it.
Thanks
Hi,
I have a PowerShell script which sends some reports to external user. Script is running on the Exchange 2013 server.
There is a Relay connector, which is working fine, I can send emails from scanners, etc. to external recipients.
The problem is, I cannot send e-mail messages to external recipients directly form Exchange server, I get this error:
"Mailbox unavailable. The server response was: 5.7.1 Unable to relay"
I see that when message is sent from the script it uses "Default FrontEnd" connector.
How can I change this behavior and send e-mail messages from script on the Exchange 2013 server successfuly?
Thanks.
Exchange 2013 installed on Server 2012r2. We use POPcon to retrieve our messages from our host.
The problem we have is receiving messages 2mb or larger. All other messages are received without any problems.
I have updated the receive connecter(s) limit to 500mb and each mailbox to 100mb.
Grateful for any help.
I'm trying to get routing working for my subdomain. Everything works internally but when users send from outside they get a bounce back. I'm trying to route public email addresses to my SharePoint site.
I'm getting "#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##rfc822;".
In sharepoint all my items get created with a subdomain. Ex: contact@sharepoint.domain.com. In order to route some email I added a @domain.com address as well, but the primary is sharepoint.domain.com.
So I thought that if contact@domain.com were emailed it would find it and route tocontact@sharepoint.domain.com.
David Jenkins
We are in a Office365-Exchange 2013 Hybrid environment today, slowing migrating users to the cloud.
We seem to receive a lot of spoofed emails and was looking for some tips/tricks to get a better hold of this. Usually these are emails that are sent to internal folks from senior publicly noticed figures such as the CEO, CFO etc.
The emails look legit, even have the correct alias@contoso.com addresses displayed unless you actually dig into the headers to see different.
All our email is scanned by Microsoft EOP as they are our MX record holders then passed thru to our On-Premises mail users.
Is it possible to tighten security by setting the on-premises and MSOL servers to never accept or block email sent from the outside when being sent from alias1@contoso.comto alias2@contoso.com?
Thanks in advance.
Hey there,
We have our Exchange environment configured to deliver all mail through a send connector that authenticates with our ISP's reputable mail server for mail delivery, in order to avoid having to deal with trust and blacklisting ourselves directly. We discovered the other day, that while we have an agreement with them to not cap our daily message sending (where their average user is), we are still subject to a 200 message/30min limit, after which subsequent message are rejected/bounced with the below error:
Remote Server returned '550 User has exceeded outgoing limit G_SPAM_USER_MAX or send_limit(200)
and if our server continues to try to send mail, we eventually start getting:
451 4.4.0 SMTPSEND.SuspicousRemoteServerError; remote server disconnected abruptly; retry will be delayed
I started looking at send connector configuration options, as well as Message throttlinghttps://technet.microsoft.com/en-us/library/bb232205(v=exchg.150).aspx
but I'm not sure the best way (if there is any) to accommodate for this. I was hoping for configuration options that would allow me to setup the existing send connector to work around this limitation by queuing, either before the limit is reached, or after by reacting differently to the 550 send limit response, but so far I'm not seeing anything like that.
I get the feeling from the Message Throttling article that I should be looking at this more from a per-user standpoint, and throttling message sending for each user, which would likely resolve the issue as the limit is only an issue of someone tries to send an excessive mass email, but I'm not sure.
Can anybody give me a swift kick in the right direction on this? Or maybe a couple different directions if there are options on how to address this? Thanks!
User Email account added to the distribution list by the owner but user cannot be seen in the Distribution List and not receiving the email. However, when expanding the DL on the outlook then only the user email gets display.Issue is happening on Exchange
Server 2010 Environment.
Hi All
We have a lot of transport rules and one of them with predicate:
Name : AttachmentProcessingLimitExceeded
LinkedDisplayText : when an attachment processing limit is exceeded<a id="AttachmentProcessingLimitExceeded"></a>
How co configure Limits for This Predicate or Transport for processing? ( We have a lot of messages with false positive )
P.S Exchange 2013 CU10
Best Wishes, Andrew Golubenkoff
Good afternoon!
I just ran across an interesting thing: I had some messages to a known good server hang up in my Edge Transport servers. I created a new Send Connector in ECP for the destination and mail now flows freely (except for the greylisting done at the destination server).
If I wanted to retrieve the messages stuck in the Edge Transport queue and re-queue them on the Hub Transport servers that have the new send connector, how would I do it? I don't see anything obvious in either Exchange Toolbox, ECP or PowerShell.
Any thoughts?
Thanks!
Gregg
Exchange 2013 mailbox Queue in one DB of MBX server has been increasing over 1000, and a couple of hours pass, it can't not be reduced. other DB of MBX server is ok.
Can i have urgent assist to find the cause of root and solve?
I have a production environment that I've inherited- Exchange 2013 CU7. 4 multirole servers on a stretched DAG load balanced by a pair of F5 LTM's.
I have little knowledge of F5's but I do know that we are offloading SSL for Exchange to these NLB's. However the "Allow SSL Offloading" check box under Outlook Anywhere in EAC has been cleared.
I'm chasing down an issue with External Outlook Anywhere and I suspect this setting may be my last hurdle. However I can't work out what impact I may create when I enable this function. Internal users are working fine.
So my question is- am I risking an Outage if I enable this feature?
TIA
Tony
I have an f5 load balanced 4 node exchange 2013 installation that has all facilities working- except outlook anywhere.
The exchange testconnectivity test fails for both Outlook connectivity and Autodiscover connectivity.
I have verified that the urls are published correctly and exist on the certificate. Using the connectivity test I am getting a 401 error: (yes the credentials work internally)
An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to
log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
HTTP Response Headers:
request-id: 36c2a29b-4f18-49ee-a8dc-747e3fcbfde8
Set-Cookie: ClientId=UCXAVARP0ELHULUFLNQ; expires=Wed, 15-Feb-2017 23:16:31 GMT; path=/; HttpOnly,LastMRH_Session=2a64f5f1;path=/;secure,MRHSession=16a55c5fdb2054d1761b8a722a64f5f1;path=/;secure
Server: Microsoft-IIS/8.5
WWW-Authenticate: Negotiate YHgGCSqGSIb3EgECAgMAfmkwZ6ADAgEFoQMCAR6kERgPMjAxNjAyMTYyMzE2MzFapQQCAlEbpgMCATypEBsOUkZTLk5TVy5HT1YuQVWqGDAWoAMCAQGhDzANGwtzdmItZXhjaDAyJKwRBA8wDaEDAgEBogYEBGoAAMA=,NTLM,Basic
realm="autodiscover.company.com"
X-Powered-By: ASP.NET
X-FEServer: (one of our exchange servers)
Date: Tue, 16 Feb 2016 23:16:30 GMT
Content-Length: 0
Expires: Thu, 01 Dec 1994 16:00:00 GMT
The F5's I think are configured correctly as they are showing the kerberos ticket passed through to AD. IIS
Outlook Anywhere Authentication types are set to
ExternalClientAuthenticationMethod : NtlmI have tried logging on to our external autodiscover site- autodiscover.company.com/autodiscover/autodiscover.xml. It prompts for credentials but will not accept any credentials at all. Is this correct?
I cannot make this work. any guidance appreciated.
Exchange Server 2013. SQL Server Reporting Services 2014.
We have a subscription in SSRS that generates multiple reports sent to multiple people within and outside our organization. These reports are sent in MHTML format. SSRS sends the message to the recipients through our Exchange Server. In our test, we discovered that most of the reports get to the recipients. However, one report fails to arrive. Yet no error was reported to SSRS or to the user. Exchange simply failed the message. When we looked at the Exchange error logs we found the following:
{[{LRT=};{LED=554 5.3.4 Content conversion limit(s) exceeded;
STOREDRV.Deliver.Exception:ConversionFailedException; Failed to process message due to a
permanent exception with message The content conversion limit has been exceeded.
ConversionFailedException: The content conversion limit has been exceeded. [Stage:
CreateReplay]};{FQDN=};{IP=}]}
The report (the MIME file sent to Exchange) is under 1MB. The report is simple, containing text and some embedded images. But this is true of all the reports, the ones that went through and the one that failed.
WHAT might be causing this issue? Any suggestions at a fix? Thanks for any help.
Hi All
I plan to use a SMTP Arciving feature in my archiving solution (non Microsoft). I wish to send a BCC copy of every message to a particular SMTP server (installen on archiving software). In Exchange 2003 there was a BCC journaling feature that could be enabled in a registry. Is there any way to direct all messages, external and internal, to a third-party SMTP server on Exchange 2013/2016? On that separate SMTP server I have an archiving software that can capture and archive incomming messages. I'm not able to use standard Exchange Journaling, since I have no licenses to integrate my currect archiving solution (non Microsoft) with a Journal Mailbox.
Any ideas?
-- Konrad Puchala