Exchange 2010 ET: 554 5.1.0 Sender denied,PerRecipientBlockedSender

Some senders get Sender Denied when sending to some recipents:
This is from the ET log: Sender Filter Agent,OnEndOfHeaders,RejectRecipients,554 5.1.0 Sender denied,PerRecipientBlockedSender
Any suggestions?

need a little more info. so some senders where are they located. and some recipients where are they located. are they on the domain. and they on the same exchange server. is this going to another company or different exchange server.
it looks like they are being blocked by the recipient block list.
Mitch Roberson |MCITP:Enterprise Server Admin, Messaging 2007, 2010 |MCTS:OCS with Voice Achievement |MCT |MCSE 2000\2003 |MCSE Messaging 2000\2003

Similar Messages

Exchange 2010 OWA : TMG Error 12302 The server denied the specified Uniform Resource Locator (URL).

Hello All,
We are using TMG2010 (SP2, rollup4) for publishing Exchange 2010 OWA sites. The issue is that after every 10-24 hrs , the TMG server stops logging in OWA sites and start giving below error. Then we have to restart the server one two times or the problem
solves by itself.
I have also install a new server and it is also giving same behavior. On TMG server the exchange edge server and Forefront Protection for exchange is also installed.
Please help to solve this issue.
Denied Connection
-TMG05 5/21/2014 11:44:39 PM
Log type:
Web Proxy (Reverse)
Status: 12302 The server denied the specified Uniform Resource Locator (URL). Contact the server administrator.
Rule:
PRC-OWA
Source:
119.157.175.238:56971
Destination:
111.68.105.121:443
Request:
GET http://mail.parc.gov.pk/owa
Filter information:
Req ID: 0e947d98; Compression: client=Yes, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=yes, valid=yes, updated=no, logged off=no, client type=public, user activity=yes
Protocol:
https
User:
anonymous
Additional information
Client agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Object source: (No source information is available.)
Cache info: 0x0
Processing time: 125 MIME type:

Hi,
A similar thread:
http://social.technet.microsoft.com/Forums/forefront/en-US/e8fdc1bd-f023-4804-ad02-67899d8c7347/the-server-denied-the-specified-uniform-resource-locator-errors12302-ashttp-error-code-of-500?forum=Forefrontedgegeneral
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to monitor particular individual Exchange 2010 mailbox

Hi
Is it possible to monitor a particular individual Exchange 2010 mailbox? If so please send me the script or steps to to accomplish this
Donald D'souza (http://donald-scom.blogspot.com/)

The Exchange 2010 MP has had some issues of late and is once again unavailable. Hopefully this should be rectified soon. Keep an eye on the Management Pack forum and someone should post there once it is back.
I appreciate the Exchange team are looking for ways to get extra monitoring from SCOM and I'm certainly not saying you can't do mailbox monitoring with SCOM. I'm just saying be careful. I have seen one enterprise write a discovery to discover the
mailboxes they wanted to monitor. The discovery captured data that changed every iteration that the discovery ran. They then wondered why SCOM stopped working, ignoring the fact that they had discovered thousands of objects whose properties changed every
time discovery ran, causing huge numbers of state change events and massive database growth.
If you are looking for in-depth exchange mailbox monitoring then SCOM is not the tool for it. Quest and Sirana do dedicated enterprise tools. If you take a look at the links and say that is what your team want then I'd suggest evaluating those
products. Developing SCOM to deliver that would not be cost efficient.
Hope you don't mind but I'll ask again - what specifically do you want to monitor? Mailbox Size? Number of emails sent \ received? size of message sent? destination? number of attachments? size of attachments? blocked messages? If you need deep detail
along the lines of the following then you really need to evaluate the following:
http://www.sirana.com/exchange/reporting
If you end up writing scripts to do all the above then you will likely severely impact performance of either SCOM or your Exchange server or possibly both.
Sadly (for budgeting) SCOM doesn't necessarily replace specialist tools - it just complements them. Likewise, if you want deep dive SQL then you'll still need Quest or Idera based tools. Probably fewer licenses and better targetted at servers with known
issues.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Exchange 2010 SP3 installation Problem

Im getting below error when upgrading with Exchange 2010 Sp3. Please assist.
Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
Below the complete error from Exchange Setup Logs
[02/16/2014 04:55:04.0515] [0] Setup will run the task 'uninstall-msipackage'
[02/16/2014 04:55:04.0515] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''
[02/16/2014 04:55:04.0515] [1] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'domain.local', Preferred Global Catalog: 'Domain.local', Preferred Domain Controllers: '{ domain.local
[02/16/2014 04:55:04.0515] [1] Beginning processing uninstall-msipackage -LogFile:'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode:'4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues:'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU'
[02/16/2014 04:55:04.0547] [1] Removing MSI package with code '4934d1ea-be46-48b1-8847-f1af20e892c1'.
[02/16/2014 04:55:06.0187] [1] [ERROR] Unexpected Error
[02/16/2014 04:55:06.0187] [1] [ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
[02/16/2014 04:55:06.0187] [1] [ERROR] Fatal error during installation
[02/16/2014 04:55:06.0234] [1] Ending processing uninstall-msipackage
[02/16/2014 05:03:04.0333] [0] End of Setup
[02/16/2014 05:03:04.0333] [0] **********************************************

Hi,
As you have found, the error is caused by that .msp installer files correlating to all the Update Rollups are not present in the c:\windows\installer folder.
Based on my research, there is no Microsoft article about the hotfix of KB2492690 (SP1 Update Rollup 3). Because our Exchange Team pulled the download due to issues with integration with Blackberry.
For more information, you can refer to the following article:
http://blogs.technet.com/b/exchange/archive/2011/03/14/exchange-2010-sp1-rollup-3-and-blackberrys-sending-duplicate-messages.aspx
Thus, to get more professional and faster help, I recommend you contact with our following support:
https://support.microsoft.com/common/international.aspx?RDPATH=%2foas%2fdefault.aspx%3fgprid%3d730
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

E72 not synching after move to Exchange 2010

My company has hundreds of E72 users that synchronize with Exchange 2007.
After we installed Exchange 2010 we had problems because the E72 phones would not get redirected to the legacy.domain.com URL.
We finally had to fix this with a workaround on our reverse proxy.
But now when we move the mailbox to Exchange 2010 the user is able to send out new emails and check the global address list, but new emails are not appearing in the mailbox on the phone.
Updating the firmware (if available), or recreating the Mail for Exchange profile will cause the phone to start syncing again, but this is not a very user friendly solution.
Does anyone know what is causing this? Or better yet, have a solution for this issue?
So far all iPhones, Windows Mobile and Android phones are syncing correctly after the migration.

Bad/Corrupt Rules can also cause migration failures so you might check that as well.
Depending on the # of mailboxes you have to work with another option would be to take an offline copy of the database (EDB/STM) and use a 3rd party utility like Lucid8's DigiScope to open the database offline. Once you have access to the data you
could dial-tone the DB, then execute the MB move which will go fast since the DB is pretty much empty. Once completed use DigiScope to inject/migrate the data directly from the offline 2003 database into the production Exchange Server.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Hi
We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
from happening.
We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
Thanks
Nauman.

Hello,
Why do you want to use the 'internal relay domain' authentication?
Thanks,
Simon Wu
TechNet Community Support

Exchange 2010 hub-transport server

i have 2 exchange 2010 hubtransport servers.
ideally when i send email my email should be load-balanced but emails send using hubcas1 goes fine and hubcas2 kepts in queues
suppose if i send at a time 5 mail
3 emails go through hubcas1
2 emails stucks in queue in hubcas2

Hi,
As you said you have added both the hub transport servers in the source server option of the send connector.Same time you have mentioned you don't have the smart host to deliver the emails to the internet and also the server hubcas2 can able to resolve the
external domain namespaces .Then do the following .
step 1 :Then please enable the protocol logging on the send connector to see the why the connections from the server hubcas2 is rejected to send emails to internet.
Step 2: Then do the outbound email test from EXRCA tool by using the ip address or name which is mapped on the MX record which belongs to the server hubcas2.
Please feel free to reply me if you have any queries .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Exchange 2010: Sender address rejected: Access denied

hi friends
i have been recently experiencing an issue with one of my customer which i send email i get bounce message while i can receive their emails with no issue. i have exchange 2010 installed and im using Anti spam device too. my domain is ok.com
i try to send from OWA as well but i get the same result.
Delivery has failed to these recipients or groups:
[email protected] A problem occurred during the delivery of this
message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: antispamServer.ok.com
[email protected] #< #5.0.0 X-Spam-&-Virus-Firewall; host mail.abc.com[22.22.22.12] said: 554
5.7.1 <btv1==14869c83b8f==[email protected]: Sender address rejected: Access denied (in reply to RCPT TO command)> #SMTP#
Original message headers:
any idea?
thanks

hi
when i disable the antispam device i get this error
smtp5.relay.iad3a.emailsrvr.com rejected your message to the following e-mail addresses:
[email protected]
smtp5.relay.iad3a.emailsrvr.com gave this error: <[email protected]>: Sender address rejected: Access denied
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another
restriction may be preventing delivery.

Exchange 2010 - #554 5.2.0 The Active Directory user wasn't found

We have migrated form Exchange 2003 to Exchange 2010 a year ago with no issues. All Exchange legacy servers uninstalled with no issues. We had an issue today were emails sent to mail-enabled public folder was returning NDRs. This happened on two or three
and then trickled down thorugh several public folders. This client has several public folders and uses them for business processes. There have been 100s of incidents now.
Symtoms:
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
#554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found. ObjectNotFoundException: The Active Directory user wasn't found. ##
We are getting the following Event log messages on Hub transport servers.
Log Name:      Application
Source:        MSExchange Store Driver
Date:          5/29/2014 2:45:53 PM
Event ID:      1020
Task Category: MSExchangeStoreDriver
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxx
Description:
The store driver couldn't deliver the public folder replication message "Backfill Request (xxxxxxx)" because the following error occurred: The Active Directory user wasn't found..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Store Driver" />
    <EventID Qualifiers="49156">1020</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-05-29T18:45:53.000000000Z" />
    <EventRecordID>168407</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxxx</Computer>
    <Security />
</System>
<EventData>
    <Data>"Backfill Request (xxxxxxx)"</Data>
    <Data>The Active Directory user wasn't found.</Data>
</EventData>
</Event>
Actions:
We have executed the following steps.
1. Start the ADSI Edit MMC Snap-in. Click Start, then Run, and type adsiedit.msc, and then click OK.
2.       Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand CN=Configuration,DC=DNSDomainName,DC=com.
3.       Expand CN=Services, and then CN=Microsoft Exchange, and then expand CN=YourOrganizationName.
4.       You will see an empty Administrative Group. Expand the CN=YourAdministrativeGroupName.
5.       Expand CN=Servers.
6.       Verify there are no server objects listed under the CN=Servers container.
7.       Right click on the empty CN=Servers container and choose Delete.
8.       Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
To no avail the issue still exists.
We have not rebooted the servers and plan to in the early morning.
We have dismounted/mounted public folder DBs
Does anyone have any other suggestions?
Danny Kennedy, MCSE, MCITP

I have already uninstalled legacy servers a year ago.
This was the solution:
I moved the public folder hierarchy to exchange 2010 using ADSIEdit.
                                  If you don't know adsiedit tool that much check this
http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c03067450-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.tpst=ba847bafb2a2d782fcbb0710b053ce01&sp4ts.oid=1840527&ac.admitted=1401455429281.876444892.492883150
Danny Kennedy, MCSE, MCITP

Unable to SEND mail using Activesync in Exchange 2010 server on iPhone or Windows Mobile 6.1

Hi All,
We've been setting up a new SBS 2011 server for a client this week. Everything is working, except the staff have 4 x iPhones to connect with Exchange ActiveSync.
There are 2 x iPhone 4's and 2 x iPhone 3Gs's. We can setup the Exchange accounts on each of the phones and they are all able to sync mail and calender etc with the server.
The problem we have is when any of them try to send mail from the phone, it gives an error : "Cannot Send Mail - An error occurred while delivering this message" and it sits in the outbox on the phone.
The newsgroups and forums are littered with people having issues with IOS4 and Exchange 2010 but most of these are from June-August 2010 when IOS4 version was around 4.00 or 4.01
A lot of these people had iPhone 3 handsets running with IOS 3.1.3 which worked with Exchange 2010 but when they upgraded to IOS 4, they had this problem sending mail.
It seems that for most of them, the fix came in the form of IOS version 4.1 which fixed the send issue for them.
We have a variety of Hansets and IOS versions (including an iPhone 3Gs running IOS 3.1.3) but are unable to send mail from any of them:
iPhone 3Gs    IOS 3.1.3
iPhone 3Gs    IOS 4.3.3
iPhone 4       IOS 4.3.3
iPhone 4       IOS 4.3.5
I was surprised that the iPhone 3Gs running 3.1.3 was unable to send either as nearly all the forums etc I read with this issue said the iPhone 3's worked with that IOS version.
Today we used a test iPhone 4 handset from our office to connect to an almost identical Small Business Server 2011 we setup two weeks ago for another client.
The test iPhone 4 was able to connect, Sync and Send email on that server but when set it to connect to this SBS 2011 server, it gets the "Cannot Send Mail" message the same as the others. So clearly the handset is working (on the other server at least),
it must be something misconfigured in this Exchange server right?
We ran the Exchange Remote Connectivity Analyser on the Exchange server and got green ticks across the board.
Outlook Web App and Outlook Anywhere both work normally. Everything we can test on the Exchange server works except sending from any iPhone.
Having said all that, I just setup a Windows Mobile 6.1 handset to sync with the Exchange 2010 server as a test, and it appears to have the same issue.
It will connect & Sync Mail, Contacts and Calendar but if trying to send an email from the phone, it will just sit in the outbox.
Does anyone have some insight into what the problem may be?

Further to this .. I found the solution on a MS Exchange 2010 support forum.
It was not a certificate or firewall issue, looks as thought the “Accepted Domains” in Exchange Mgmt Console –
Org Config – Hub Transport cannot have any spaces in the name field.
I had some spaces and the emails were not downloading fully and able to send. Once I removed the spaces from the Name field and
restarting the Exchange and IIS services emails were now being sent and received ok.
Check
out :
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmobility/thread/321eae51-9cbd-4a5e-85c1-68d8f7b523c3
This
is good one to add to your knowledge bank in case you come across it in the future.
Rgds Gerry

Exchange 2010 can't send or receive email with attachments.

Hello,
We have an Exchange 2010 server, running under Windows 2008R2. Both the server and Exchange are current for Windows and Exchange updates. Exchange is on SP3 installed about a month ago with no errors reported in the event logs.
The problem is that attachments over about 1 MB do not send or receive and no error message is returned. If I send an email message with a 3 MB attachment to myself, it reports as sent in Outlook. On the Exchange server the message queue shows nothing in
the queue. I try to use Exchange mail flow tracking tool and it hangs when selecting “messages received from” option. I gave up waiting after 5 minutes for the display to populate.
As the server is set attachments should be able to send and receive up to 20 MB.
I checked and verified all settings I could find related to this. I checked with the Exchange Management Console per the following article:
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-limits-exchange-server-2010-part1.html
I also checked using the Exchange Power Shell using the following article:
http://eightwone.com/2010/09/29/exchange-message-size-limits/
Both show that all settings are suitable. Details are below
I would appreciate feedback on this problem.
Thank you!
Details from the articles noted above:
First test was to attach a 3 mb text file in Outlook sent from my in house account to my in house account. After 5 minutes the test message was not received nor was there an error message returned.
Checked The Exchange server mail queue and there was nothing in the queue. Checked the Exchange mail flow tracking tool and it hung when selecting “messages received from” option.
Reviewed and verified settings per the following 2 articles:
Article #1
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-limits-exchange-server-2010-part1.html
Organization Configuration>Hub Transport>General Settings>Global Settings>Transport Settings set to max receive size (KB) = 20480
Settings set to max send size (KB) = 20480
Organization Configuration> Hub Transport> Send Connectors tab.
Maximum message size (KB) set to 20480
Exchange Management Console> Server Configuration> Hub Transport> and then on the right side, select the desired server.
A list of all Receive Connectors will be shown below
There are 3 receive Connectors
#1) named Client XXXXXXXXXX
Maximum message size (KB) set to 20480
#2) named Default XXXXXXXXXX
Maximum message size (KB) set to 20480
#3) named relay
Maximum message size (KB) set to 20480
Use Exchange Management Shell to check settings
#1) Get-ADSite
Returns:
Name                           HubSiteEnabled
Default-First-Site-Name        False
#2) Get-ADSiteLink
Name                      ADCost     ExchangeCost    Sites
DEFAULTIPSITELINK         100                        {xxxx.local/Configuration/Si...
#3) Get-ADSiteLink | select Max*
MaxMessageSize
unlimited
Exchange Management Console>Expand Organization Configuration>Click on Hub Transport item>Click on Transport Rules tab
No rules
Article #2
http://eightwone.com/2010/09/29/exchange-message-size-limits/
COMMAND: Get –TransportConfig
results:
ClearCategories                     : True
ConvertDisclaimerWrapperToEml       : False
DSNConversionMode                   : UseExchangeDSNs
ExternalDelayDsnEnabled             : True
ExternalDsnDefaultLanguage          :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
ExternalDsnReportingAuthority       :
ExternalDsnSendHtml                 : True
ExternalPostmasterAddress           :
GenerateCopyOfDSNFor                : {}
HygieneSuite                        : Standard
InternalDelayDsnEnabled             : True
InternalDsnDefaultLanguage          :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
InternalDsnReportingAuthority       :
InternalDsnSendHtml                 : True
InternalSMTPServers                 : {}
JournalingReportNdrTo               : <>
LegacyJournalingMigrationEnabled    : False
MaxDumpsterSizePerDatabase          : 18 MB (18,874,368 bytes)
MaxDumpsterTime                     : 7.00:00:00
MaxReceiveSize                      : 20 MB (20,971,520 bytes)
MaxRecipientEnvelopeLimit           : 500
MaxSendSize                         : 20 MB (20,971,520 bytes)
MigrationEnabled                    : False
OpenDomainRoutingEnabled            : False
Rfc2231EncodingEnabled              : False
ShadowHeartbeatRetryCount           : 12
ShadowHeartbeatTimeoutInterval      : 00:15:00
ShadowMessageAutoDiscardInterval    : 2.00:00:00
ShadowRedundancyEnabled             : True
SupervisionTags                     : {Reject, Allow}
TLSReceiveDomainSecureList          : {}
TLSSendDomainSecureList             : {}
VerifySecureSubmitEnabled           : False
VoicemailJournalingEnabled          : True
HeaderPromotionModeSetting          : NoCreate
Xexch50Enabled                      : True
COMMAND:
Set-TransportConfig –MaxReceiveSize 20MB –MaxSendSize 20MB
C:\Windows\system32>Set-TransportConfig -MaxReceiveSize 20MB -MaxSendSize 20MB
WARNING: The command completed successfully but no settings of 'Transport Settings' have been modified.
COMMAND:
Get-SendConnector
Identity                                AddressSpaces
Enabled
Internet                                {SMTP:*;1}
True
COMMAND:
Set-SendConnector -Identity Internet -MaxMessageSize 20MB
WARNING: The command completed successfully but no settings of 'Internet' have been modified.
COMMAND:
Get-ReceiveConnector
Identity                                Bindings                                Enabled
XXXXXXXXXX\Default XXXXXXXXXX           {0.0.0.0:25}
True
XXXXXXXXXX \Client XXXXXXXXXX     {:::587, 0.0.0.0:587}                   True
XXXXXXXXXX \relay                        {0.0.0.0:25}
True
COMMAND:
Get-ReceiveConnector | fl Identity,MaxMessageSize
Identity       : XXXXXXXXXX \Default XXXXXXXXXX
MaxMessageSize : 20 MB (20,971,520 bytes)
Identity       : XXXXXXXXXX \Client XXXXXXXXXX
MaxMessageSize : 20 MB (20,971,520 bytes)
Identity       : XXXXXXXXXX \relay
MaxMessageSize : 20 MB (20,971,520 bytes)
COMMAND:
Get-AdSiteLink | fl Name,*max*
Name           : DEFAULTIPSITELINK
MaxMessageSize : unlimited
COMMAND:
Get-RoutingGroupConnector <ConnectorID> | FL Name, *Max*
No routing group connectors are installed
Individual
Recipient Configuration > Mailbox>Properties of the User> Activate tab Mail Flow Settings> Properties>Message Size Restrictions settings:
Set to 20480 for send and receive for all.
Re-tested and had the same problem.
Post on Technet.

ExchangeITPro,
Thank you for your reply.
>what SP are you at?
As noted in the first paragraph: "We have an Exchange 2010 server, running under Windows 2008R2. Both
the server and Exchange are current for Windows and Exchange updates. Exchange is on SP3 installed about a month ago with no errors reported in the event logs."
>try restarting the transport services.
Done previously as well as the entire server. No change.

Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].

Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].
In a mixed client environment, mostly Outlook 2010 & 2013 clients. Only Outlook 2013 clients (about only 4 mailboxes) are receiving this error immediately after sending an email. My temp band-aid at the
moment is to: from the client, go into the "address book" & select a different address book like "Contacts" & then select the address again & select the Global Address List, which is the default. (it will have the users email
+ at the beginning of the field, it reads, Global Address List - (email of the user), then I close Outlook & open it back up, & the problem is solved. But on some mailboxes, not all, the issue comes back. From my research, I know that our individual
mailboxes do not send out over 500 emails in one day. Most users will send out maybe 20 or 30 in one day, so I don't think it's that.
But I'm not sure if this is related, but I have noticed that the log files for the Exchange 2010 seems to only hold logs with date stamps of only a couple of days. It used to hold log files indefinitely until they were archived, deleted, etc. So, this is
a new, unusual issue I have seen as well.
We have 2 .edb's, one active: 78 GB's and one disabled at 7 GB's. Exchange 2010 is running on Windows Server 2008 r2, Enterprise Ed. We have had Exchange 2010 running now for about almost 2 years now and this is the first time this particular issue has come
up.
Thanks.

Hi,
You can refer to the following steps to rebuild an Offline Address Book.
1. Open EMS. Update OAB using the Update-OfflineAddressbook "offline address book" cmdlet. Restart Background Intelligent Transfer Service on the Mailbox server.
2. Initiate OAB replication from mail box server to CAS server. Execute for each CAS server using the Update-FileDistributionService "CASServerName" cmdlet.
3. Start Outlook and download OAB.
What's more, here is an article for your reference.
How to Quickly Rebuild an Exchange 2010 Offline Address Book
http://social.technet.microsoft.com/wiki/contents/articles/7725.how-to-quickly-rebuild-an-exchange-2010-offline-address-book.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

When I send e-mail messages with file by using a POP3 in Exchange 2010 I received delivered message with file. How I can disable this functions that file do not include to delivery message. I use Exchange 2010 only local users.

When I send e-mail messages with file by using a POP3 in Exchange 2010 I received delivered message with file. How I can disable this functions that file do not include to delivery message. I use Exchange 2010 only local users.

I think there is not native rule for this, but you could try a transport rule which removes all attachments over a very small file size like 1KB.
http://blogs.technet.com/b/exchange/archive/2009/05/11/3407435.aspx
CRM Advisor

Exchange 2010 Receive Connector intermittently getting an SMTP RSET from sending SMTP servers causing missing user email

Users are receiving about 95% of their messages from sending SMTP servers. Intermittently, sending SMTP servers send the Exchange 2010 Server a SMTP RSET command for no apparent reason. The RSET Command (by SMTP specification) causes the Exchange 2010 Server
to drop the message. The sending SMTP servers then do not resend the message after asking the Exchange server to drop the message. This means the message is marked as Sent by the sending servers but the dropped messages never show up in the users' Outlook
inbox.
Exchange 2010 Version 14.3 (Build 123.4)
Roles: Hub Transport, Client Access, Mailbox
What is going on?
Exchange Receive Connector log showing a RSET example:
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,1,10.80.120.15:25,65.99.255.73:53479,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,2,10.80.120.15:25,65.99.255.73:53479,>,"220 vpn.a1expediting.com Microsoft ESMTP MAIL Service ready at Thu, 17 Jul 2014 08:47:06 -0400",
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,3,10.80.120.15:25,65.99.255.73:53479,<,EHLO inbound37.exchangedefender.com,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,4,10.80.120.15:25,65.99.255.73:53479,>,250-vpn.a1expediting.com Hello [65.99.255.73],
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,5,10.80.120.15:25,65.99.255.73:53479,>,250-SIZE 52428800,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,6,10.80.120.15:25,65.99.255.73:53479,>,250-PIPELINING,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,7,10.80.120.15:25,65.99.255.73:53479,>,250-DSN,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,8,10.80.120.15:25,65.99.255.73:53479,>,250-ENHANCEDSTATUSCODES,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,9,10.80.120.15:25,65.99.255.73:53479,>,250-AUTH,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,10,10.80.120.15:25,65.99.255.73:53479,>,250-8BITMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,11,10.80.120.15:25,65.99.255.73:53479,>,250-BINARYMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,12,10.80.120.15:25,65.99.255.73:53479,>,250 CHUNKING,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,13,10.80.120.15:25,65.99.255.73:53479,<,MAIL FROM:<[email protected]> SIZE=165270,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,14,10.80.120.15:25,65.99.255.73:53479,*,08D16FD38F3D3355;2014-07-17T12:47:07.370Z;1,receiving message
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,15,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.0 Sender OK,
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,16,10.80.120.15:25,65.99.255.73:53479,<,RCPT TO:<[email protected]> ORCPT=rfc822;[email protected],
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,17,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.5 Recipient OK,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,18,10.80.120.15:25,65.99.255.73:53479,<,RSET,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,19,10.80.120.15:25,65.99.255.73:53479,>,250 2.0.0 Resetting,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,20,10.80.120.15:25,65.99.255.73:53479,<,QUIT ,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,21,10.80.120.15:25,65.99.255.73:53479,>,221 2.0.0 Service closing transmission channel,
Daniel

Hi,
According to the receive connector log, your emails were failed to be deliverd with DNR. If I misudnerstand the meaning, please feel free to let me know. If yes, I'd like to confirm the detail information in the DNR to narrow down the
cause.
Additionally, based on my research, the RSET command performs an SMTP reset, and then aborts the message that is currently being sent. Thus, the log didn't provide more information for troubleshooting. Is there any other error in your event log? please check
the event log when the issue happens again.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 - Method to send e-mail when the WAN IP is dynamic

Hello,
I am writing due to the fact that I cannot send e-mail from my Exchange 2010 Server to my Yahoo! address for testing. When trying to do so, I get the following error message:
mta1106.mail.gq1.yahoo.com gave this error:
Mail from xxx.xxx.xxx.xxx not allowed - 5.7.1 [BL21] Connections not accepted from IP addresses on Spamhaus PBL; see
http://postmaster.yahoo.com/errors/550-bl21.html [550]
As one can see, because my IP address is residential, I cannot send e-mail to all addresses on the web. I really would like to use this as my primary contact, and thought of using a proxy. Can someone recommend a good proxy, or workaround for this? I am
sorry for posting in Exchange 2013, but I couldn't find the 2010 forum. Thank you to all who reply.
Mike

Thank you for your reply,
I have set up DynDNS, and I am currently using my own domain name. The problem was I needed to configure a smart SMTP host, or relay server on my send connector. I decided to go with SMTP2GO, as they are cheap, and allow you to send 20 e-mails a day for
free. When the money is right, I plan to upgrade.
Thank you for your help.
Mike

Exchange 2010 ET: 554 5.1.0 Sender denied,PerRecipientBlockedSender

Similar Messages

Maybe you are looking for