Hi,

I am attempting to get outbound address rewriting working for mailboxes in Office 365. Given that this functionality doesn't exist in O365, I have enabled centralized mailflow so all incoming and outgoing mail is directed through the on-premise Exchange servers (Mail/CAS) and Edge server, configured in hybrid mode. Mail is flowing properly, and routing through the edge server as it should.

I have ensured that the outbound address rewrite agent is enabled:

[PS] C:\Windows\system32>Get-TransportAgent "Address Rewriting Outbound Agent"

Identity                                           Enabled         Priority
--------                                           -------         --------
Address Rewriting Outbound Agent                   True            1

And I have tested outbound rewriting. It works for mail sent from on-premise mailboxes, however it does not work for mail send from an Office 365 mailbox.

So I know that the address rewrite agent works and is configured correctly, but I don't know why mail routed through the edge server does not get filtered by the transport agents on that edge when coming from Office 365. Is this something to do with the send/receive connectors related to the hybrid configuration? Do I need to disable TLS or something like that? The most important question is: can this even be done?

Hi,

     I am facing problem that, in my organization we are using Exchange  Server 2013. We are facing

problem that we are getting emails lately ( Delay ). While observing emails stuck in Queue & give  Exchange Server 2013: Failed to connect. Winsock error code: 10060 error. After 30 minuts it connects automatically. But again error occurs after some time. Please help me to solve this issue  

Kthxbai

Hello,

is it posible to have multiple ptr records for single IP on public DNS or multiple PTR records for single IP may fail some SMTP compliance checks.

Any help would be appreciated.

Running Exchange 2013 CU7 with Outlook 2007 utilizing standard settings:

IMAP Email from Outlook internal user or external user successful (usually) see below

From an application call by Security Information Systems product (Alarm Center)  It simply tries to send an attachment via a validated user, it is successful although quirky, sometimes it holds it a while then sends. Sometimes we get this error: "The server responded: 421 4.4.2 Message submission rate for this client has exceeded the configured limit" and actually I just got that while sending an internal email to myself. So realistically IMAP also has some things to concern 

SMTP Email from Outlook internal user or external user successful

From application sends to internal just fine, the other day we had it sending to external but dropping off an attachment that will go with it.  Now it does not send at all, and nothing is left at the server even on the internal success. As I recall I could at least look it up and see that it left the server.

According to their support they tried my SMTP settings on their localized system (Alarm Control0 and it functions.  So I am stuck.

RECAP: IMAP flaky send "usually" complains a lot from app call

            SMTP was sending w/o attachment and was reflecting in server, now send "internally with attachment" but not externally, records no record of anything in server.

Hi all,

i have the following problem.

we recently migrated from Lotus notes To office365.

all items, including Tasks were copies.

in one of the tasks, there was a mailing list.
it send a e-mail to all persons in that list, notifying that the task was updated.

Now, All those persons keep sending e-mails to all persons on that list.
this while the original task was deleted.

does anyone have a solution for this?

Dear All,

I am hoping someone could help me with this issue. 

I look after the exchange network for our organisation and I have received a call to state that when we send email meetings externally they are received as an .ics attachment containing the primary SMTP as the sender email address, whereas when sent externally they need to be changed to the external email secondary SMTP address.  In order to rectify this fault I have come up with a couple of options but I am unable to know how to rectify this, they are:

1.  Prefererence - To send the meeting externally as a meeting request where the external sender address has been converted to the external secondary SMTP address.  Would this be possible?

2.  To change the organizer of the meeting in the ics attachment to the external secondary SMTP address rather than staying as the Primary SMTP address.  Is this possible?

We use Exchange 2013 on Windows 2012 R2 Virtual Machines.

Regards,

Phil

For a short time we hosted another entities email on our Exchange 2013 Server as part of a migration strategy.  We have moved them to their own Exchange server. For the sake of explanation i'll call ours aus.com.au and theirs show.org.au

I removed (or so I thought) the config for the show.org.au, but when we attempt to send email to show.org.au our exchange server comes back with an NDR because it cant find the recipient in our server.  Interestingly if the Recipient didnt exist on our server, the email is sent to the show.com.au's server, so it only effects those addresses that were hosted for a time on our server.

Clearly the show.org.au domain is still recorded somewhere in the Exchange 2013 config, but I havent been able to find it.

Get-AcceptedDomains - returns aus.com.au and aus.local

Get-ReceiveConnector configs show no clues

We have an on-premises Exchange 2013 deployment that just went live after a big migration this past weekend. Plenty of the usual, and perhaps some not-so-usual, hiccups, but one that has me particularly stumped is that when my users mark a message as junk in OWA and select "Report" when they are prompted to report it to Microsoft, they eventually get their report bounced back to them with an NDR similar to the following:

Delivery has failed to these recipients or groups:
junk@senpluspluseop.onmicrosoft.com
A problem occurred during the delivery of this message. Please try to resend the message later.

The following organization rejected your message: BN3NAM01FT005.mail.protection.outlook.com.

Diagnostic information for administrators:
Generating server: BY2NAM01HT014.mail.protection.outlook.com
junk@senpluspluseop.onmicrosoft.com
BN3NAM01FT005.mail.protection.outlook.com
Remote Server returned '<BN3NAM01FT005.mail.protection.outlook.com #5.4.14 smtp;554 5.4.14 Hop count exceeded - possible mail loop ATTR1>'

I've been unable to determine why these reports would be being sent to an address that evidently doesn't work. Is this because we do not have Exchange Online Protection? Should we turn off the "Report" feature altogether as a result?

Hi

I know how to create Send Connectors in Exchange, but I am confused the mail flow "between SEND connector and recipient (let say gmail.com)". Consider if I have configured SEND Connector to use DNS....

I want to know which service will be used to contact DNS on internet to check MX.. In short I want to know, WHO will contact DNS?

Thanks in advance...

Hello,

we are using "Spamhaus ZEN" RBL for our Exchange.
There are a few IP-Adresses that I want to whitelist, this should work with "Add-IPAllowListEntry -IPAddress x.x.x.x"
The Command works successfully and returns the results with "Get-IPAllowListEntry"
Settings for IPAllowListConfig are "-Enabled True" and "-ExternalMail Enabled True"

My problem is that mails are being blocked even if they are on the whitelist.
Can someone tell me why that is happening?
I tried to restart TransportService and even whole Exchange server without success.

Regards

gugaua

Hello,

We have a monthly report emailed to a user mailbox setup to forward all email to global security group and until this month was working fine but will no longer go through. If I disable forwarding I am able to see the email come through to the inbox. I have done a mail trace and am able to see it being sent to the DL. We are setup with a on premise AD using dirsync to O365. I have triple checked all rules and settings everywhere and am at a loss. I cannot figure out why its not forwarding to our "all" DL anymore.

Hi,

I'm trying to configure a mailbox to have email sent to an internal email address (e.g. example@organisation<dot>com) to an external address (e.g. example@externaldomain<dot>com).

I have followed the instructions available here: https://technet<dot>microsoft<dot>com/en-AU/library/dd351134(v=exchg<dot>150)<dot>aspx

These instructions direct me to create a contact for the external user and I have done that and followed all applicable steps.

These instructions are supposed to be applicable to exchange online and exchange 2013, however there are discrepancies in some steps as some options are unavailable.

The steps listed are as below:

"

1. In the Exchange Admin Center, navigate to Recipients > Mailboxes.

2. In the list of user mailboxes, click or tap the mailbox that you want to configure mail forwarding for, and then click or tapEdit .

3. On the mailbox properties page, click Mailbox Features.

4. Under Mail Flow, select View details to view or change the setting for forwarding email messages.

   On this page, you can set the maximum number of recipients that the user can send a message to. For on-premises Exchange organizations, the recipient limit is unlimited. For Exchange Online organizations, the limit is 500 recipients.

5. Check the Enable forwarding check box, and then click or tap Browse.

6. On the Select Recipient page, select a user you want to forward all email to. Select the Deliver message to both forwarding address and mailbox check box if you want both the recipient and the forwarding email address to get copies of the emails sent. Click or tap OK, and then click or tap Save.

What if you want to forward mail to an address outside your organization? Or forward mail to multiple recipients? You can do that, too!

• External addressesCreate a mail contact and then, in the steps above, select the mail contact on the Select Recipientpage. Need to know how to create a mail contact? Check out Manage mail contacts.

• Multiple recipientsCreate a distribution group, add recipients to it, and then in the steps above, select the mail contact on the Select Recipient page. Need to know how to create a mail contact? Check out Manage Distribution Groups.

"

In Step 5, when I click browse and look for the contact it is not listed. Only user mailboxes are listed.

Can someone please guide me here as I can't see where i'm going wrong?

Regards,

Manning

Hi ,

I have Exchange 2013 server configured as a multirole (cas+mbx) that is rejecting messages .

I started the verbose logging of the receive connector and notice that sometimes the response from the server was

452 4.3.1 Insufficient system resources.

I don't have back pressure events and my Transport Database has a lot of free space.

Any ideas ?

Exchange 2013 CU7

Error from managed availability

Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.
      This could indicate that the mailbox submissions are taking too long or not progressing at all.
      SequenceNumber: 635708989783012831

      Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
      FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
      ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635708989783012831. First Run? = False. Previous mail submission to store was successful. Results -  # of previous results: 0.  Could Not Find stages that ran.  Previous SendMail failure -  Mail submitted to Store during the previous run never reached SendAsCheck.
                        This may indicate a latency from Store to Submission Service. Investigating.  Found lower SA latency. Indicates an issue in Submission service.
                            Investigate. In SendMail -  NotificationID=00000050-0000-0000-0000-00004489f5df Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail failure.
      CheckPreviousRunMail exception details:
      Current SendMail exception details:

      MailWasSentInLastRun (0(no)/1(yes)): 1
      CheckMailSuccess(0(no)/1(yes)): 0
      SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1

      PreviousMailLatencies: <2816a467fc6e4df58602517b149c0d3d@ex01.cosanostra-bg.com>,,2015-06-29T19:24:24.120Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=0.515|SA=0.031|MTSSDPL=0.011|MTSSDSS=0.013;;<c553276a7fdc48bb971696959d0d2e12@ex01.cosanostra-bg.com>,,2015-06-29T19:19:24.074Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=0.312|SA=0.031|MTSSDPL=0.011|MTSSDSS=0.012;;<555848d05c0e4141a7c441ff0fdb294b@ex01.cosanostra-bg.com>,,2015-06-29T19:14:23.902Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=5.593|SA=5.249|MTSSDPL=0.006|MTSSDSS=0.014;;
      GetPreviousMailLatencyFailures:

      (The following are applicable if the mail was actually sent)
      MailSentAt: 29.6.2015 19:29:24
      TimeInSendingToStore: 125,0239
      Sent Mail Result Details:
        (InternetMessageId:<3fd1eb6e77e74b78a40ebd213ca3dbd9@ex01.cosanostra-bg.com>;
        ItemEntryId:0 0 0 0 B2 A1 18 B5 9C ED 46 4E 9A BE D6 7B 72 A 16 42 7 0 F6 1E 9B BD D4 78 81 4E 82 A BD AE 4 39 B5 43 0 0 0 0 1 B 0 0 F6 1E 9B BD D4 78 81 4E 82 A BD AE 4 39 B5 43 0 0 44 C5 DF 36 0 0 )
        Properties of Sending mail
        (Subject:00000050-0000-0000-0000-00004489f5df-MapiSubmitLAMProbe;
        Sender:HealthMailboxad7d1178cd2f4d89a176adf4adfcd908@cosanostra-bg.com;
        MbxGuid:b3d5201b-e40b-4987-b335-385fb733c354;
        MdbGuid:2a1cd6fa-6435-4ab1-82b2-8b9654e4ee94;
        Recipient:HealthMailboxad7d1178cd2f4d89a176adf4adfcd908@cosanostra-bg.com;
        Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
        DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException, Exception currentRunException, DateTime timeMessageSentToStore)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
   at System.Threading.Tasks.Task.Execute()'
Probe Result Name: 'Mapi.Submit.Probe'
Probe Result Type: 'Failed'
Monitor Total Value: '0'
Monitor Total Sample Count: '12'
Monitor Total Failed Count: '12'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '26.6.2015 7:17:58'

Hi,

We received an email feedback report from AOL, we started yesterday receiving a lot of these emails that are coming from AOL. It's indicating to us that we either sending a SPAM email from our exchange servers to an AOL user, or we are used as a mail relay (this won't be the case since we close our mail relay to only known servers)

Here is a header of one example if anybody can make any sense of this , it will be very helpful:

Return-Path: <hxinlet@chunghocomnet.com>
Received: from vm-bosta2k3edge.coganltd.priv (smtp.cogan.com [38.127.66.23])
 by mtaiw-aaf01.mx.aol.com (Internet Inbound) with ESMTP id C7ADF70925941 for
 <redacted>; Tue, 30 Jun 2015 13:01:31 -0400 (EDT)
Received: from BOSTA2013-CT-2.coganltd.priv (10.0.0.32) by
 vm-bosta2k3edge.coganltd.priv (10.0.4.6) with Microsoft SMTP Server (TLS) id
 15.0.847.32; Tue, 30 Jun 2015 12:54:55 -0400
Received: from Pickup by BOSTA2013-CT-2.coganltd.priv with Microsoft SMTP
 Server id 15.0.847.32; Tue, 30 Jun 2015 16:54:49 +0000
X-GFI-METKTSID: 39d8131e-45e7-471e-a39c-e00a5d207cca
X-GFI-METKTSIG: Yhsm6/GnBynbvswW3Gdl7t90542j6dps6GhSEp2m7EjtM6HqO11A0+zWJKufXjHuSi6HyMNHtXa2L+YKl8PyCCtTBAL73bJtkZFpploVc75O2aH4qXzEGG1UPNfBc/4hbgbg9UMS79Nep5zFdn9jnS23RxOtcoJ0IW91F4KQobY=
X-GFI-ALK: 28e1eb4d-c825-4dec-97ef-cb27812c0666
Received: from BOSTA2013-CT-2.coganltd.priv (10.0.0.32) by
 BOSTA2013-CT-2.coganltd.priv (10.0.0.32) with Microsoft SMTP Server (TLS) id
 15.0.847.32; Tue, 30 Jun 2015 12:54:47 -0400
Received: from vm-bosta2k3edge.coganltd.priv (10.0.4.6) by
 BOSTA2013-CT-2.coganltd.priv (10.0.0.32) with Microsoft SMTP Server (TLS) id
 15.0.847.32 via Frontend Transport; Tue, 30 Jun 2015 12:54:47 -0400
Received: from chunghocomnet.com (186.91.126.88) by
 vm-bosta2k3edge.coganltd.priv (10.0.4.6) with Microsoft SMTP Server id
 15.0.847.32; Tue, 30 Jun 2015 12:54:17 -0400
Received: from sOt.Uc.NVJVf933SE.com (sOt.Uc.NVJVf933SE.com [97.12.103.181])by
 redacted@ecogan.com
Received: from [12.111.137.160] by 7075334444.qZmEJC.com (via HTTP)
Subject: Alert from financial department
From: hxinlet <hxinlet@chunghocomnet.com>
To: <redacted@ecogan.com>
MIME-Version: 1.0
Message-ID: <8728b5cf-011e-45df-b57b-ba65a99f7c39@chunghocomnet.com>
Date: Tue, 30 Jun 2015 12:25:28 -0400
Content-Type: multipart/alternative;
 boundary="=_------------050905020505060503050808"
Received-SPF: Fail (vm-bosta2k3edge.coganltd.priv: domain of hxinlet@chunghocomnet.com does not
 designate 186.91.126.88 as permitted sender) receiver=vm-bosta2k3edge.coganltd.priv;
 client-ip=186.91.126.88; helo=chunghocomnet.com;
X-GFI-SMTP-Submission: 1
X-GFI-SMTP-Submission: 1
X-GFI-SMTP-HelloDomain: vm-bosta2k3edge.coganltd.priv
X-GFI-SMTP-RemoteIP: 10.0.4.6
X-GFIME-MASPAM: SPAM
X-GFI-MOVETOJUNK: 1
Old-Message-ID: <5592CA00.D015B94D@chunghocomnet.com>
x-aol-global-dis
Authentication-Results: mx.aol.com;
 spf=temperror (aol.com: while processing the SPF record for chunghocomnet.com we encountered a temporary error.) smtp.mailfrom=chunghocomnet.com;
x-aol-sid: 3039ac1a7f5b5592cb6a5945
X-AOL-IP: 38.127.66.23
X-AOL-SPF: domain : chunghocomnet.com SPF : temperror

-Mehdi