Setup Exchange to duplicate emails to my SMTP server.

November 10, 2014, 5:52 pm

≫ Next: Exchange 2013 Mail Flow Error

≪ Previous: Virtual directory misconfigured

$

0

0

Hello.

I am developing product to detect leakage of sensitive data from internal networks. Often comes out requirement to check company emails ruling by Exchange server. Already I have SMTP server which is integrated with main logic of analyze data and nothing more, so next step is to receive emails from Exchange server. But solution is much more complicated than I expect, maybe because I never had to work with Exchange before. So there is my issue:

There is a portable way, between different versions of Exchange servers and configurations, to setup them send duplicates of all (internal and maybe incoming) emails to this SMTP server?

---

Exchange 2013 Mail Flow Error

November 14, 2014, 4:22 am

≫ Next: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

≪ Previous: Setup Exchange to duplicate emails to my SMTP server.

$

0

0

Hi All,

I am facing a issue while test the Mail-flow of my DC DR Server using Exchange Shell. Please look into the attached log and suggest the possible reason behing this issue.

I am create a DAG and map 3 Data Base server with in it. When I try the same command for two of my DC Server it showing no error but when I try the same command pointing to DR server than only I get this error .... 

[PS] C:\Windows\system32>Test-Mailflow -AutoDiscoverTargetMailboxServer -Identity "ASMSPLCP-EXDR"
[Microsoft.Mapi.MapiExceptionSendAsDenied]: MapiExceptionSendAsDenied: Unable to submit message. (hr=0x80070005,
ec=1244)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=46]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=296][latency=78]
    Lid: 52176   ClientVersion: 15.0.913.22
    Lid: 50032   ServerVersion: 15.0.913.20
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropSubmitMessage [50]
    Lid: 17082   ROP Error: 0x4DC
    Lid: 27745
    Lid: 21921   StoreEc: 0x4DC
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 41232
    Lid: 60208
    Lid: 37136
    Lid: 34608
    Lid: 55056
    Lid: 42768
    Lid: 56112
    Lid: 29908   StoreEc: 0x4D9
    Lid: 33016   StoreEc: 0x4DC
    Lid: 63016   dwParam: 0x32
    Lid: 39640   StoreEc: 0x4DC
    Lid: 10786   dwParam: 0x0        Msg: 15.00.0913.000:ASMSPLCP-EXDR
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x4DC
    Lid: 60547   StoreEc: 0x4DC
    Lid: 21966
    Lid: 30158   StoreEc: 0x4DC
    + CategoryInfo          : InvalidData: (:) [Test-Mailflow], RecipientTaskException
    + FullyQualifiedErrorId : [Server=ASMSPL-MBX1,RequestId=72333031-3423-4fdb-bd2b-e14d6ce05c16,TimeStamp=11/14/2014
   12:11:56 PM] [FailureCategory=Cmdlet-RecipientTaskException] 35158E0F,Microsoft.Exchange.Monitoring.TestMailFlow
    + PSComputerName        : asmspl-mbx1.domain.com

---

Regards, Koustov Choudhury

Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

May 21, 2014, 11:49 am

≫ Next: Exch 2013 Forwarding Mail from local account to External SMTP user

≪ Previous: Exchange 2013 Mail Flow Error

$

0

0

Migration of Exchange 2010 to 2013 was carried out.  Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers.  Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery and shadow redundancy on the 2010 edge transport server.

How can these be removed?

Exch 2013 Forwarding Mail from local account to External SMTP user

November 21, 2012, 11:53 am

≫ Next: تجديث الويندوز

≪ Previous: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

$

0

0

New 2013 implementation... Two Servers (Front End and Back End) both running Exchange 2013.

I am having trouble sending a local AD Exchange mailbox mail to external SMTP address.  I have tried several options.. I have created an "contact" as was required in previous versions.  I have created new AD accounts with external SMTP addresses, I have also attempted to use the scriptlet:

Set-Mailbox -Identity "%AD-USER%" -DeliverToMailboxAndForward $true -ForwardingSMTPAddressexternaluser@mail.com  (%AD-USER% was actual AD Username/mailbox) andexternaluser@mail.com was actual receipient SMTP address (username@gmail.com)

Local AD Mailbox receives the mail appropriately however I have enabled forwarding everyway I know how and nothing seems to work.  If I send mail straight from my account to the destination SMTP address, they get it; just not if it is sent to the local AD account then forwarded via -DeliverToMailboxAndForward command...

Please help.. I have several users that I need to have their mail CC'd to an external SMTP address.. Previous versions of Exchange required a "Contact" to be created and then the mailbox forwarded to that contact, which had a SMPT mail address...

Im not adverse to implementing via powershell if I can just get it to work... Any suggestions are greatly appreciated and needed.

تجديث الويندوز

November 20, 2014, 5:30 pm

≫ Next: Exchange 2013 - Fresh installation--Why all of this spam all of a sudden?

≪ Previous: Exch 2013 Forwarding Mail from local account to External SMTP user

$

0

0

• توجد مشكلة عندى خاصة بى window update

Exchange 2013 - Fresh installation--Why all of this spam all of a sudden?

November 25, 2014, 8:38 am

≫ Next: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

≪ Previous: تجديث الويندوز

$

0

0

We are coming from an Exchange 2003 with SBS2003 environment so have no experience with versions other than that prior to using Exchange 2013. We have a new Exchange 2013 installation using the same email accounts we always used. We did setup an MX record for our domain (mail.domainname.com) with the Registrar (in this case, Network Solutions) for our domain when we moved to Exchange 2013.

We have had a very significant increase in SPAM ever since this new installation.  Why would that be?

Note with SBS2003/Exchange we had no 3rd party Antispam tools installed..we had very little Spam.

Thanks for any input.

Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

May 21, 2014, 11:49 am

≫ Next: Inbound mail timeout

≪ Previous: Exchange 2013 - Fresh installation--Why all of this spam all of a sudden?

$

0

0

Migration of Exchange 2010 to 2013 was carried out.  Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers.  Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery and shadow redundancy on the 2010 edge transport server.

How can these be removed?

Inbound mail timeout

November 25, 2014, 2:15 am

≫ Next: email route via new exchange 2013 server

≪ Previous: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

$

0

0

Hi

I please need some advise...

I have a hosted Exchange 2010 installation with quite a few tenants.

Here in South Africa there is a company that sends payslips through an accounting suite, and there are some of the companies in my Exchange that need these payslips, mail flow from that domain has stopped completely, in my message tracking logs there are nothing noted.

these mails typically gets sent in batches to the companies and I suspect that I am tar pitting those mails.

from the system that these mails are sent, the SMTP error that is generated is Queue Timeout.

I make use of PRTG for my monitoring in the data center and lately I have been seeing SMTP response times on my CAS servers of round 60000ms.

Can someone please steer me in the right direction troubleshooting this issue.

All other mail is perfectly fine.

MXToolbox reports 13 ms which is also not ideal.

Regards 

EDIT: SMTP code returned is 554 4.4.7

---

email route via new exchange 2013 server

November 29, 2014, 3:07 am

≫ Next: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

≪ Previous: Inbound mail timeout

$

0

0

HI guys, 

We have 2 Exchange 2013 Servers. CAS and Mailbox. We have enabled the "Proxy Through Client Access Server" on Send connector. 

we have installed new Exchange 2013 Multi-Role server in the same exchange Organization. After that some external emails trying to relay via new exchange 2013 Server even we did not add that server in to Source Servers on send connector. 

any idea ? 

Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

May 21, 2014, 11:49 am

≫ Next: Exch 2013 Forwarding Mail from local account to External SMTP user

≪ Previous: email route via new exchange 2013 server

$

0

0

Migration of Exchange 2010 to 2013 was carried out.  Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers.  Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery and shadow redundancy on the 2010 edge transport server.

How can these be removed?

Exch 2013 Forwarding Mail from local account to External SMTP user

November 21, 2012, 11:53 am

≫ Next: emkei.cz

≪ Previous: Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

$

0

0

New 2013 implementation... Two Servers (Front End and Back End) both running Exchange 2013.

I am having trouble sending a local AD Exchange mailbox mail to external SMTP address.  I have tried several options.. I have created an "contact" as was required in previous versions.  I have created new AD accounts with external SMTP addresses, I have also attempted to use the scriptlet:

Set-Mailbox -Identity "%AD-USER%" -DeliverToMailboxAndForward $true -ForwardingSMTPAddressexternaluser@mail.com  (%AD-USER% was actual AD Username/mailbox) andexternaluser@mail.com was actual receipient SMTP address (username@gmail.com)

Local AD Mailbox receives the mail appropriately however I have enabled forwarding everyway I know how and nothing seems to work.  If I send mail straight from my account to the destination SMTP address, they get it; just not if it is sent to the local AD account then forwarded via -DeliverToMailboxAndForward command...

Please help.. I have several users that I need to have their mail CC'd to an external SMTP address.. Previous versions of Exchange required a "Contact" to be created and then the mailbox forwarded to that contact, which had a SMPT mail address...

Im not adverse to implementing via powershell if I can just get it to work... Any suggestions are greatly appreciated and needed.

emkei.cz

December 5, 2014, 9:16 am

≫ Next: Default Disclaimer

≪ Previous: Exch 2013 Forwarding Mail from local account to External SMTP user

$

0

0

How can i stop sending mail from emkei.cz with unknown mail adresses to out domain user mail account.

Default Disclaimer

December 6, 2014, 11:35 am

≫ Next: How does Exchange 2013 Handle MX Priorities?

≪ Previous: emkei.cz

$

0

0

I just installed a new exchange 2013 in a new forest. I created a sendconnector to send mails to my existing legacy exchange 2003

Every mail I send to the 2003 server is appended with this disclaimer below, How do I remove this default disclaimer.

DISCLAIMER:
Sample Disclaimer added in a VBScript.

How does Exchange 2013 Handle MX Priorities?

December 8, 2014, 10:13 am

≫ Next: Remote Server returned '532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

≪ Previous: Default Disclaimer

$

0

0

Occasionally I will run into an issue where a user is trying to email someone at a specific domain, and every other email they send bounces back (usually with an error of '550 relay not permitted'). Now in every case of this I have tracked it down to the recipients domain having a mx record that routes to a mail server that isn't configured for their domain (if I telnet to the IP on port 25 returned by the mx record and attempt to 'RCPT TO: user@somedomain.com' where somedomain.com is the name in question, it will give the same error, where the other MX record will work fine). 

Now what baffles me about this is that usually when this happens, the MX record that doesn't work has a much lower priority than the one that does. In the most recent case the working MX record had a priority of 10, and the non-working one had a priority of 30, but for some reason Exchange seems to round robin between the two MX records when sending email to that domain, instead of using the one with the highest priority.

Is this normal behavior for exchange, it seems to go against RFC 2821? We just have a standard send connector setup, using 'MX associated with recipient domain' and 'Use External DNS lookup settings on servers with Transport Roles', no smart hosts or anything. 

(running Exchange 2013 CU3 on server 2008 R2)

Remote Server returned '532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

December 12, 2014, 10:19 pm

≫ Next: Exchange 2013 Mail Flow Error

≪ Previous: How does Exchange 2013 Handle MX Priorities?

$

0

0

Hello, we keep getting the "Remote Server returned '532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'" Error, we are currently running 2013 CU3 with 2 servers with no DAG's and this is only happening on one server. Any ideas?

---

Exchange 2013 Mail Flow Error

November 14, 2014, 4:22 am

≫ Next: rule for external mail flow

≪ Previous: Remote Server returned '532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

$

0

0

Hi All,

I am facing a issue while test the Mail-flow of my DC DR Server using Exchange Shell. Please look into the attached log and suggest the possible reason behing this issue.

I am create a DAG and map 3 Data Base server with in it. When I try the same command for two of my DC Server it showing no error but when I try the same command pointing to DR server than only I get this error .... 

[PS] C:\Windows\system32>Test-Mailflow -AutoDiscoverTargetMailboxServer -Identity "ASMSPLCP-EXDR"
[Microsoft.Mapi.MapiExceptionSendAsDenied]: MapiExceptionSendAsDenied: Unable to submit message. (hr=0x80070005,
ec=1244)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=46]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=296][latency=78]
    Lid: 52176   ClientVersion: 15.0.913.22
    Lid: 50032   ServerVersion: 15.0.913.20
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropSubmitMessage [50]
    Lid: 17082   ROP Error: 0x4DC
    Lid: 27745
    Lid: 21921   StoreEc: 0x4DC
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 41232
    Lid: 60208
    Lid: 37136
    Lid: 34608
    Lid: 55056
    Lid: 42768
    Lid: 56112
    Lid: 29908   StoreEc: 0x4D9
    Lid: 33016   StoreEc: 0x4DC
    Lid: 63016   dwParam: 0x32
    Lid: 39640   StoreEc: 0x4DC
    Lid: 10786   dwParam: 0x0        Msg: 15.00.0913.000:ASMSPLCP-EXDR
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x4DC
    Lid: 60547   StoreEc: 0x4DC
    Lid: 21966
    Lid: 30158   StoreEc: 0x4DC
    + CategoryInfo          : InvalidData: (:) [Test-Mailflow], RecipientTaskException
    + FullyQualifiedErrorId : [Server=ASMSPL-MBX1,RequestId=72333031-3423-4fdb-bd2b-e14d6ce05c16,TimeStamp=11/14/2014
   12:11:56 PM] [FailureCategory=Cmdlet-RecipientTaskException] 35158E0F,Microsoft.Exchange.Monitoring.TestMailFlow
    + PSComputerName        : asmspl-mbx1.domain.com

---

Regards, Koustov Choudhury

rule for external mail flow

December 10, 2014, 3:53 am

≫ Next: certain extensions blocked

≪ Previous: Exchange 2013 Mail Flow Error

$

0

0

1. Is is possible to set up a rule on exchange server 2013 sp1 that will forward all emails received from and sent to a particular domain (example dell.com) to a mailbox in exchange?.

  2.   Also is it possible to setup a rule that will monitor emails sent between that domain and  particular user inside the Exchange domain2013 sp1.         

    

certain extensions blocked

May 30, 2014, 9:18 am

≫ Next: HealthMailbox....... thousands of tranfers appearing in SPAM quarantine

≪ Previous: rule for external mail flow

$

0

0

The users regularly need to browse sites in the .uk   Also they email to the .uk extension.

I cannot figure out how to permanently allow such access and email usage.

I have added .uk to allow list but at first it worked and now it does not.

We are using Exchange 2010

Thanks,

Jay

---

Jay Doyle

HealthMailbox....... thousands of tranfers appearing in SPAM quarantine

November 19, 2012, 11:17 am

≫ Next: Edge 2010 server unable to relay internally

≪ Previous: certain extensions blocked

$

0

0

I've asked this question on another forum without an answer so I thought I would try here.

This relates to Exchange 2013.  During Friday through to Monday I am picking up thousands of spam items sent frominboundproxy@inboundproxy.com and up to five HealthMailboxes are involved.  The healthmailboxes have accounts in AD and appeared during the Exchange installation.

Here is and example -

Diagnostic information for administrators:

Generating server: EXCHANGE2.xxxxx.yyyyyyyy.yy.yy

HealthMailbox168a97e4814144848b101e39c3482fca@xxxxx.yyyyyyyy.yy.yy
#550 5.2.1 Content Filter agent quarantined this message ##

Original message headers:

Received: from EXCHANGE2.xxxxx.yyyyyyyy.yy.yy (192.168.0.72) by
 EXCHANGE2.xxxxx.yyyyyyyy.yy.yy (192.168.0.72) with Microsoft SMTP Server
 (TLS) id 15.0.516.32; Mon, 19 Nov 2012 19:20:48 +0000
Received: from InboundProxyProbe (::1) by EXCHANGE2.xxxxx.yyyyyyyy.yy.yy
 (::1) with Microsoft SMTP Server id 15.0.516.32 via Frontend Transport; Mon,
 19 Nov 2012 19:20:48 +0000
Subject: Inbound proxy probe
Message-ID: <2e1d9dd2-d71e-4c23-9b5a-b8e12c109e57@EXCHANGE2.xxxxx.yyyyyyyy.yy.yy>
From: <inboundproxy@inboundproxy.com>
To: Undisclosed recipients:;
Return-Path: inboundproxy@inboundproxy.com
Date: Mon, 19 Nov 2012 19:20:48 +0000
MIME-Version: 1.0
Content-Type: text/plain
Received-SPF: Fail (EXCHANGE2.xxxxx.yyyyyyyy.yy.yy: domain of
 inboundproxy@inboundproxy.com does not designate ::1 as permitted sender)
 receiver=EXCHANGE2.xxxxx.yyyyyyyy.yy.yy; client-ip=::1;
 helo=InboundProxyProbe;

 
Can anyone spread light on this, is it normal behaviour and if not how can I stop it?  The exchange installation is on a green field domain.  The exchange server is an OOTB installation on a single VM.

Edge 2010 server unable to relay internally

June 20, 2014, 2:30 am

≫ Next: Configure a Catch-All Mailbox in Exchange 2013

≪ Previous: HealthMailbox....... thousands of tranfers appearing in SPAM quarantine

$

0

0

Hi,

I have exchange 2010 environment; all the roles are running on individual servers. Recently I have setup an additional edge server and have completed with edge subscription as well. The outgoing email from the internal network have no issue. However the incoming emails are stuck at the new edge server and unable to relay to the hub server. The error message in the queue is “451 4.4 0 primary target ip address responded with 5.7.3 cannot achieve exchange server authentication”.

How can I resolve this?

---

Arun.T