My problem is with mail flow. If I go into the Exchange 2013 toolbox and open the queue viewer I can see over a hundred messages stacking up. What do I do to stop these errors?
In the Queues tab under Last Error I see the following error; majority of these errors in the "From Address" is<>
"[{LRT=(date\time);{LED=44
Win2012/Ex2013 sp1
PennyM
Hello,
I have recently ran into a problem with my Exchange 2010 server. I can not receive emails from certain domains. There is only 2 domain names in particular (only one user from each domain has tried sending emails to our domain).
thanks in advance
We have a customer with about 4000 Exchange 2013 Mailboxes onprem. He also posess an Office365 E1 Plan with Exchange Online Plan 1 included.
The customer whishes not to have an Exchange Hybrid Configuration, instead he will stay onprem but using Exchange Online Protection as an mailgateway with antimalware / antispam function.
Can we use Exchange Online Protection with this license, poiniting our mx Record to Exchange Online Protection, which send us the verified mail to our onprem Exchange 2013 Servers?
Can we also send the outgoing mail traffice to Exchange Online first for verification?
Do we have all the function of EOP with the Office365 E1 Plan?
Do we need first to establish dirsync for replication the user to Office365?
Best Regards - Bueschu
Bueschu
We are having sporadic issues with internal email delayed delivery.
This is the topology:
Single Exchange 2013 (Version 15.0 Build 995.29) running on Windows 2012R2
Here is a message tracking log example of the problem:
**This is the STOREDRIVER RECEIVE**
RunspaceId : ef020c77-b0f5-470d-85c4-1de5df3a78ed
Timestamp : 1/4/2016 8:21:26 AM
ClientIp : fe80::d974:571a:8e74:dca6
ClientHostname : RXMAIL.rxbenefits.local
ServerIp : fe80::d974:571a:8e74:dca6%12
ServerHostname : RXMAIL
SourceContext : 08D2F4D6F76C2B95
ConnectorId :
Source : STOREDRIVER
EventId : RECEIVE
InternalMessageId : 0
MessageId : <e02a50e8518649eb8a36316731d1be38@RXMAIL.rxbenefits.local>
Recipients : {kmcdanal@rxbenefits.com, lisa@rxbenefits.com}
RecipientStatus : {To, To}
TotalBytes : 49512
RecipientCount : 2
RelatedRecipientAddress :
Reference :
MessageSubject : RE: BCBS/Rx Benefits and ID's
Sender : tressa@rxbenefits.com
ReturnPath : Rx4AMs@rxbenefits.com
Directionality : Originating
TenantId :
OriginalClientIp : 192.168.50.67
MessageInfo : 04I:
MessageLatency :
MessageLatencyType : None
EventData : {[MailboxDatabaseGuid, a20269a8-f110-4887-8434-00acd1e6d988], [ItemEntryId, 00-00-00-00-2A-A8
-DB-69-13-CB-F1-43-B6-E2-D8-10-29-07-FE-F0-07-00-53-06-B1-2C-1B-01-E1-4A-A5-EF-E2-41-F7-39-5B
-58-00-00-00-80-0F-88-00-00-F2-46-95-A2-41-7B-FC-4D-A4-74-3B-03-B3-87-BF-A2-00-01-00-DD-3F-A7
-00-00], [DeliveryPriority, Normal], [PurportedSender, Rx4AMs@rxbenefits.com]}
**This is when it finally got submitted 35 minutes later**
RunspaceId : ef020c77-b0f5-470d-85c4-1de5df3a78ed
Timestamp : 1/4/2016 8:56:34 AM
ClientIp : fe80::d974:571a:8e74:dca6%12
ClientHostname : RXMAIL
ServerIp :
ServerHostname : RXMAIL.rxbenefits.local
SourceContext : MDB:a20269a8-f110-4887-8434-00acd1e6d988, Mailbox:cc57c1d6-6755-442a-921d-82cccd31498a,
Event:197459615, MessageClass:IPM.Note, CreationTime:2016-01-04T14:21:25.534Z,
ClientType:MOMT
ConnectorId :
Source : STOREDRIVER
EventId : SUBMIT
InternalMessageId :
MessageId : <e02a50e8518649eb8a36316731d1be38@RXMAIL.rxbenefits.local>
Recipients : {kmcdanal@rxbenefits.com, lisa@rxbenefits.com}
RecipientStatus : {}
TotalBytes :
RecipientCount : 2
RelatedRecipientAddress :
Reference :
MessageSubject : RE: BCBS/Rx Benefits and ID's
Sender : tressa@rxbenefits.com
ReturnPath :
Directionality : Originating
TenantId :
OriginalClientIp : 192.168.50.67
MessageInfo : 2016-01-04T14:21:25.534Z;LSRV=RXMAIL.rxbenefits.local:TOTAL=2109.081|SA=2088.066|MTSSDC=0.047
|MTSSDMO=20.311|MTSSDPL=0.015|MTSSDSS=0.312|MTSSDS=0.656|MTSS=21.024
MessageLatency : 00:35:09.0810000
MessageLatencyType : LocalServer
EventData : {[ItemEntryId, 00-00-00-00-2A-A8-DB-69-13-CB-F1-43-B6-E2-D8-10-29-07-FE-F0-07-00-53-06-B1-2C-
1B-01-E1-4A-A5-EF-E2-41-F7-39-5B-58-00-00-00-80-0F-88-00-00-F2-46-95-A2-41-7B-FC-4D-A4-74-3B-
03-B3-87-BF-A2-00-01-00-DD-3F-A7-00-00], [PurportedSender, Rx4AMs@rxbenefits.com]}
Note the MessageInfo SA value is 2088 seconds. I cannot find a reference to what this value refers to.
If I export the logs to HTML the logs indicate the following:
8:21AM STOREDRIVER RECEIVEI recently discovered that on a single multi-role server you must set the attachment size limit at the organization level and not on the receive/send connectors. With this limitation is there a way to configure the following?
1. Set max send/receive message size to/from internal users to 10 MB.
2. Set Max send/receive message size to/from external users to 20 MB.
Any suggestions would be greatly appreciated. Thank you in advance
Jose
I wanted to enable mail address spoofing check on my receive connector. So I used:
Get-ReceiveConnector 'default frontend SRV-EX' | Remove-ADPermission -User 'NT AUTHORITY\ANONYMOUS LOGON' -ExtendedRights Ms-Exch-SMTP-Accept-Any-Sender
It write to me error: cannot remove ace on object because it is not present. But when I check extended right Ms-Exch-SMTP-Accept-Any-Sender permission is missing on connector.
After that I trying to use telnet and send message (f.e. MAIL FROM: asdasd@sdafsdf.com) and this message is successfully delivered to my mailbox. Then I check extended rights on connector again and see Ms-Exch-SMTP-Accept-Any-Sender permission appeared there.
How can I totally remove it? What cause this behaviour?
Hi All,
We have Exchange 2013 CU9 installed on Windows server 2012 R2 Standard. GoDaddy certificate installed on this server is about to expire in next 4 days but there is no event logging for this certificate expiry. When I check the other Exchange 2013 servers I found MSExchangeTransport event 12018 gets logged while a certificate is about to expire. any suggestions.
we have configured a hub tansport rule to bcc all the messages send to a group, rule works but the user receives that message for 10 times.
Couldnt figure out the issue , felt many number of databases but now i have reduced the databases to only 2 but still the rule does this.
Please adise what else to check.
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!
Hi guys.
We are dealing with RBL not working.
We have zen.spamhaus.org as one of the RBL's (priority 1).
This IP is reported as spam/blacklisted
http://mxtoolbox.com/SuperToolX.aspx?action=blacklist%3a38.68.18.194&run=toolpage
Is this result ok or not?
we also take a look that we don't have any DNS issues. We had exactly the same behavior as on this post "https://social.technet.microsoft.com/Forums/office/en-US/1252eb3d-949c-4cc3-a1d7-dc08f0bdd372/rbl-not-working-on-exchange-2013-edge-transport" but we have resolved this by changing forwarders on DNS and now it resolves just fine.
After that we have restarted transport service on Exchange 2013 EDGE.
Edge is on CU11.
Any other hints to check why RBL is not working ok?
With best regards
bostjanc
hi all ,
recently we have added new Exchange Server Node ( one CAS/HUB and one Mail box ) to our environment exchange 2013 .
we trying to send email to outside some emails are going and other are failed to deliver with below NDR :
Remote Server at [172.20.1.24] (172.20.1.24) returned '400 4.4.7 Message delayed' 1/10/2016 2:37:42 PM - Remote Server at [172.20.1.24] (172.20.1.24) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 172.20.1.24:25'
when shutdown the new add mailbox server all are working fine any idea ?
Hi there.
A user marked a folder properties that it should delete items older then 7 days, but those items still stays in that folder.
Any suggestion why this not working?
bostjanc
hi all ,
recently we have added new Exchange Server Node ( one CAS/HUB and one Mail box ) to our environment exchange 2013 .
we trying to send email to outside some emails are going and other are failed to deliver with below NDR :
Remote Server at [172.20.1.24] (172.20.1.24) returned '400 4.4.7 Message delayed' 1/10/2016 2:37:42 PM - Remote Server at [172.20.1.24] (172.20.1.24) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 172.20.1.24:25'
when shutdown the new add mailbox server all are working fine any idea ?
Hi, We are migrating some users from one forest/Exchange org to another. In the old forest they use S/MIME digital IDs (issued by an internal Enterprise root CA) for signing and encrypting email. In the new forest they will not need to sign and encrypt any new emails but they will need to be able to read encrypted emails migrated over from the old infrastructure.
I have played around with exporting a recipient's S/MIME certificate (inlcuding private key) from the certificate store of their old PC into the certificate store of their new PC and they are able to read migrated encrypted emails fine.
However, presumably when the certificate reaches its expiry date it will not be able to renew because the old CA will be unreachable. Will this cause the encrypted mail to be unreadable or will the recipient just get a warning message ?
We do already have an existing Enterprise root CA in the target forest so I wonder is there a way to export/import the relevant S/MIME digital IDs over to that somehow ?
Thanks for any help on this...
Edit: I just set the clock forward, on the test user's PC, past the cert expiry date and am still able to read the encrypted emails (since the expired cert is still in the cert store of the PC). So I think this is a workable solution. ( I suppose if we did
ever need S/MIME encryption on new emails, post-migration, then we just get users to enroll a new cert off the new CA...)
Using Exchange 2013 CU11 on Windows Server 2008 R2. Upgraded from CU9 and issues didn't seem to happen then -- this is a testing environment before I deploy the server.
Outlook 2010 connects fine, can compose email and send but it never goes anywhere, doesn't show up in the Exchange Toolbox Queue. If I use OWA the mail stays in the Drafts folder when I click Send. When I try to send again it says "you do not have permission to perform this action" Finally, if I compose something in Outlook 2010 or OWA it will hit the Drafts folder if I "save" it so I know they are communicating correctly.
I have searched for the issue on the Internet and tried all DNS, host file, Exchange fixes I can find but still no luck. My MX record is correct and the Receive Connectors are all default. This server is not internet connected at the moment and I am just trying to route mail internally from a few mailboxes I have created. AD, DNS are on the same machine as we only have one server at the moment. I was fine with CU9 but then did Windows Updates and CU11 update and this happened. Also, we use POP3 and I tried via that method and it won't accept any authentication so there are definitely a few things going on.
Hello,
The test exchange server I'm trying to deploy passes all connectivity tests but is having trouble sending anything outbound. it can receive from the outside just fine. We've already processed our reverse delegation DNS request through our ISP and it's up and running.
Mail just gets stuck in queue and keeps trying to retry with the 451.4.4.0 error encountered while communicating with primary target IP addresses then ends up failing to send with the header #550 4.4.7 QUEUE.Expired; message expired ##
Hello,
I have a multi domain exchange 2013. One of the domains was migrated to office 365 and mailboxes and domain was removed from the exchange.
The synchronization is filtered down to the OU where the migrated users are. They only have proxy address and mail attribute.
Now users that are still on the on-prem exchange are unable to send mail to the domain that was migrated to Office 365 with the following error:
Remote Server returned '420 4.2.0 Recipient deferred because there is no Mdb'
I tried setting the migrated domain back into the exchange server as an external relay domain but that did not work. The on-prem exchange is still looking for the mailboxes in its DB.
The exchange is not in hybrid mode.
Any ideas on how I can sidestep this?
Thanks in advance,
Haukur
Hi, I have installed and configured MS Exchange 2013 server with SP1 and CU9 on MS Windows 2012 R2 server. The server is an additional domain controller (There are two more domain controllers including one DC) and has local DNS as well. Exchange server holds both the roles in single box. DNS lookup is configured with local DNS and SmarthHost is being used for outbound emails.The POP3 and IMAP clients are fine but having following two issues...
1. OWA clients are not able to send email. The email stuck in DRAFT folder. Got error message that "You do not have appropriate permissions to perform this task".
2. MS Outlook 2010 Exchange clients also have sending emails but their emails do not go in draft. The email exists from outlook and vanished. Means emails do not reach to recipients neither they queue up in system.
I shall be grateful for and earliest possible solution.
I have an exchange 2010 environment where 2013 was introduced for migration and upgradation. Both the servers are in the same subnet. While testing the mail flow between the environment:
- Mails from 2013 mailbox are getting delivered to 2010 mailbox and to external email(gmail etc..)
-Mails sent to 2013 mailbox(irrespective of the source mailbox-2010 or external) are NOT getting delivered to the inbox.
While troubleshooting and tracking i found following things:
1. The mails with 2013 mailbox as their destination are stuck in the retry queue of 2010 hub server(i.e the mails are reaching in the environment)
2. message tracking logs show message as received whereas it is not.
3. i checked the anonymous user in the default receive connector of 2013, but it did not help
4. dns settings and nslookup are all fine.
what could be the possible reason for such a behaviour on exchange 2013 or 2010.