Receive Connector

June 30, 2014, 9:52 pm

≫ Next: SAN for accepted domain

≪ Previous: Microsoft Exchange Anti Spam Update

$

0

0

Hi,

I am running Exchange Server 2013 and after a reboot all works fine for an undetermined amount of time, then for some reason the receive connector stops working, well I presume it is the receive connector. Using the Microsoft Remote Connectivity Analyzer I get the following error (See Below). As far as I can tell only a reboot of the Server will resolve this error as I have tried stopping all the Exchange Server's services & restarting them and did not fix the problem. As you could imagine rebooting the server during the day is almost impossible but also not being able to receive emails is very painful. Any advice would be helpful as at this point I am fresh out of ideas except a re-install and hope it doesn't do it again (not really an option). I have also deleted the receive connector & re-created it.

Delivery of the test email message failed.
	Additional Details   The server returned status code -1 - The operation has timed out. Exception details: Message: The operation has timed out. Type: System.Net.Mail.SmtpException Stack trace:    at System.Net.Mail.SmtpClient.Send(MailMessage message)    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally() Elapsed Time: 100001 ms.

---

SAN for accepted domain

February 9, 2015, 7:17 pm

≫ Next: Anti-spam cfg. for zen.spamhaus.org but IPs on SBLCSS still getting through

≪ Previous: Receive Connector

$

0

0

I'm absorbing a company into our exchange and added them as an accepted domain.  There current certificate is pretty standard mail and autodiscover SAN names.  Currently RPC over http is not working correctly and that is to be expected since I pointed there DNS record for autodiscover to my server.  I don't have autodiscover.theircompany.com in my certificate, so it's trying to resolve a name that doesn't exist.  My question is should I add a SAN name for autodiscover.theircompany.com to get RPC over HTTP to work correctly?

My SAN names would then look like this: 

mail.mycompany.com

autodiscover.mycompany.com

legacy.mycompany.com

autodiscover.theircompany.com

Would this be accurate or is there a better method?

Thanks!

Anti-spam cfg. for zen.spamhaus.org but IPs on SBLCSS still getting through

February 13, 2015, 7:43 pm

≫ Next: User Monitoring / Mailbox Copy

≪ Previous: SAN for accepted domain

$

0

0

Hi:

I've cfg. an Exchange server to use IP Block List Provider zen.spamhaus.org but mail from IPs on the SBLCSS are still getting through.  From command prompt I've run nslookup x.x.x.x.zen.spamhaus.org and received proper 127.0.0.3 response so I know server can query Zen.  It's cfg. to 'Match any return code.'

Any ideas?

Thank you! 

---

Bob Herman IT Tropolis

User Monitoring / Mailbox Copy

February 1, 2015, 7:59 pm

≫ Next: Disclaimer footer text exemption for extenal email

≪ Previous: Anti-spam cfg. for zen.spamhaus.org but IPs on SBLCSS still getting through

$

0

0

Hi Everyone,

I'm looking for a way to keep a copy of users mailbox data even if/when items are deleted.

Basically, we need to monitor and keep records of all activity on a mailbox due to some potential fallout in the future. We need to be able to access mail sent and received (and if possible, calendar, contacts, tasks) - and be able to access the data even if the user deletes it (which is a high possibility) 

We're currently running Exchange Online P1 through O365, your help is greatly appreciated!

Cheers.

Disclaimer footer text exemption for extenal email

February 5, 2015, 3:52 am

≫ Next: Exchange SBS Server is not receiving emails

≪ Previous: User Monitoring / Mailbox Copy

$

0

0

Hi,

I am using my company email to send emails which has adding of disclaimer footer to email for external recipients.

I am just curious if there is a way to put an exemption for all emails i send to specific recipients. The email must not to be appended by our corporate disclaimer footer when sending them to external email/ email outside our organization?

The footer which is added to the email body sent to an external recipient looks like below.

************************************************************************

This email transmission is confidential and intended for the addressee only. It may contain privileged and confidential information. If you are not the person or organisation to whom it is addressed, you must not copy, distribute, or take any action in reliance upon it. If you have received this message in error, please notify the XXXXX@XXXXX.com and return it.

I believe that there is a transport rule happening every time I am sending email to external receipient. my email are having this kind of footer. What I want is to put exemption of this rule to all email I send to *@domain.com (all emails @domain.com)

Please advise what should be done.

Exchange SBS Server is not receiving emails

February 5, 2015, 3:54 pm

≫ Next: Queue Viewer - Exchange 2013

≪ Previous: Disclaimer footer text exemption for extenal email

$

0

0

We have a Exchange 2007 server that is not receiving emails but can send emails. The domain is

motsayandlay.com and the DNS records are hosted with Yahoo. It is a new client and the records there are very weird. I have checked all the normal settings on server but the SBS 2008 server will not receive the emails. Any help would be appreciated.

Queue Viewer - Exchange 2013

February 6, 2015, 2:31 pm

≫ Next: Junk folder

≪ Previous: Exchange SBS Server is not receiving emails

$

0

0

Hello Guys

I have an exchange 2013and working properly. We have been reviewing the mail queue and we detected many mail that are not sent to be spam and only are 3 domains.

Is there any way to block in Exchange Server the 3 domains listed in the message queue.

Thanks for your help

Regards

Sebastian

Junk folder

February 3, 2015, 10:32 pm

≫ Next: Receive Connector

≪ Previous: Queue Viewer - Exchange 2013

$

0

0

On the server Exchange EDGE I add recipient (user1@contoso.com) to the white list, now all spam gets to inbox foruser1@contoso.com.
Is it possible to further processing (on Backend or user Outlook) message to move in junk mail?

---

Receive Connector

June 30, 2014, 9:52 pm

≫ Next: SCL: 9 - Not all going to 'Junk Email' folder for all users

≪ Previous: Junk folder

$

0

0

Hi,

I am running Exchange Server 2013 and after a reboot all works fine for an undetermined amount of time, then for some reason the receive connector stops working, well I presume it is the receive connector. Using the Microsoft Remote Connectivity Analyzer I get the following error (See Below). As far as I can tell only a reboot of the Server will resolve this error as I have tried stopping all the Exchange Server's services & restarting them and did not fix the problem. As you could imagine rebooting the server during the day is almost impossible but also not being able to receive emails is very painful. Any advice would be helpful as at this point I am fresh out of ideas except a re-install and hope it doesn't do it again (not really an option). I have also deleted the receive connector & re-created it.

Delivery of the test email message failed.
	Additional Details   The server returned status code -1 - The operation has timed out. Exception details: Message: The operation has timed out. Type: System.Net.Mail.SmtpException Stack trace:    at System.Net.Mail.SmtpClient.Send(MailMessage message)    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally() Elapsed Time: 100001 ms.

SCL: 9 - Not all going to 'Junk Email' folder for all users

June 9, 2014, 10:04 am

≫ Next: Do any services require a restart after changing Message Retry Interval?

≪ Previous: Receive Connector

$

0

0

Some mail that has SCL: 9 are not all going to 'Junk Email' folder. Most are, but some slip through. There are several organizations on this exchange system, and this is happening to all users.

Get-OrganizationConfig for SCLJunkThreshold is '4'

SCLJunkEnabled for users is 'Yes'

Here is the header of a message that was marked as spam but went to the Inbox:

Received: from MBX1.domain.com (192.168.2.5) by MBX2.domain.com
 (10.1.1.7) with Microsoft SMTP Server (TLS) id 15.0.775.38 via Mailbox
 Transport; Mon, 9 Jun 2014 09:02:44 -0700
Received: from CAS2.domain.com (10.1.1.2) by MBX1.domain.com
 (192.168.2.5) with Microsoft SMTP Server (TLS) id 15.0.775.38; Mon, 9 Jun
 2014 09:01:20 -0700
Received: from smtp1.domain.com (10.1.1.3) by CAS2.domain.com
 (10.1.1.2) with Microsoft SMTP Server id 15.0.775.38 via Frontend Transport;
 Mon, 9 Jun 2014 09:02:43 -0700
Received: by smtp1.domain.com (Postfix, from userid 501)    id 2293BC033F;
 Mon,  9 Jun 2014 08:19:13 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    smtp1.domain.com
X-Spam-Level:
X-Spam-Status: No, score=1.0 required=3.0 tests=BAYES_00,DATE_IN_PAST_06_12,
    HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET shortcircuit=no autolearn=no version=3.3.1
Received: from web2.domain.com (web2.domain.com [1.2.3.4])    by
 smtp1.domain.com (Postfix) with ESMTP id 6D6D8C02E2;    Mon,  9 Jun 2014
 08:19:07 -0700 (PDT)
Received: from [198.0.89.233] (port=22316 helo=easthou-dc1.ehosm.com)    by
 web2.domain.com with esmtp (Exim 4.80.1)    (envelope-from
 <infiltratora2@raywhite.com>)    id 1Wu1wH-0006gx-GG; Mon, 09 Jun 2014 08:56:50
 -0700
Message-ID: <7J2N7PLH.6428091@raywhite.com>
Date: Mon, 9 Jun 2014 07:33:39 +0000
From: American Express Customer Service <AmericanExpress@welcome.aexp.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: <user@domain.com>
Content-Type: multipart/alternative;
    boundary="------------000101080607090805060900"
Subject: ***SPAM*** American Express - Safe Key
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - web2.domain.com
X-AntiAbuse: Original Domain - domain.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - raywhite.com
X-Get-Message-Sender-Via: web2.domain.com: mailgid no entry from get_relayhosts_entry
Return-Path: infiltratora2@raywhite.com
X-MS-Exchange-Organization-Network-Message-Id: 45f62fb3-2fdb-4efa-5a86-08d152133032
X-MS-Exchange-Organization-SCL: 9
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.5705.600;TIME:TimeBasedFeatures;OrigIP:unavailable
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: CAS2.domain.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-EsetId: 37303A291EC25A6B637562

Do any services require a restart after changing Message Retry Interval?

August 23, 2014, 12:01 pm

≫ Next: There's a problem with the recipient's mailbox. Please try resending this message.

≪ Previous: SCL: 9 - Not all going to 'Junk Email' folder for all users

$

0

0

I'm trying combat a "grey-list" issue by changing the Message Retry Interval to 15 min from 1 min. I did this change about 12 hours ago and I my test messages are still sitting in queue. I suspect a service restart is needed. Any ideas?

 

Set-TransportServer SAC79906MAILP01 -MessageRetryInterval 00:15:00

Thanks much! :-)

There's a problem with the recipient's mailbox. Please try resending this message.

September 5, 2014, 12:15 pm

≫ Next: Live exchange server

≪ Previous: Do any services require a restart after changing Message Retry Interval?

$

0

0

I have a user who cannot receive a message from a particular external sender. That senders assistant (same domain and server as the external sender with the issue) is able to forward the exact same message to my user and it arrives as it should. In message tracking, I can see the message came in through my smart host, through my front end and to the users mailbox server, where an NDR was generated.  We had the assistant forward us the NDR and it says:

There's a problem with the recipient's mailbox. Please try resending this message. If the problem continues, please contact your helpdesk.

From my 3rd party smart host/spam filter, I have a copy of the message in audit and when I forward it to myself, the same thing happens - it generates an NDR when it arrives at my Exchange mailbox server.  This makes me conclude that my end users mailbox isn't corrupt, rather it's something in the message header that our server doesn't like (I've seen this happen with other senders as well, but it is extremely rare and random).

Details/facts of my environment:
-Current production messaging system is Exchange 2003.
-Working on Exchange 2010 co-existence.
-This problem between this sender and us has been an issue before the introduction of Exchange 2010.
-I'm hoping to begin end user mailbox migrations to 2010 and will have the sender try again at that time, but I still have testing to do with our voice messaging system before I can begin moving end user mailboxes.

....Begin redacted NDR detail....
Remote Server returned '< #5.2.1>'
Original message headers:
Received: from fe.mydomain.com ([192.168.1.10]) by
 mailboxsrv.mydomain.com with Microsoft SMTPSVC(6.0.3790.4675);      Thu, 4 Sep
 2014 12:49:48 -0700
Received: from exc2010.mydomain.com ([192.168.1.50]) by
 fe.mydomain.com with Microsoft SMTPSVC(6.0.3790.4675);        Thu, 4 Sep
 2014 12:49:47 -0700
Received: from smtp.mydomain.com (192.168.1.49) by exch2010.mydomain.com
 (192.168.1.50) with Microsoft SMTP Server (TLS) id 14.3.210.2; Thu, 4 Sep 2014
 12:49:47 -0700
Received: from pps.filterd (PPMail.mydomain.com [127.0.0.1])   by
 PPMail.gsblaw.com (8.14.5/8.14.5) with SMTP id s84Jkb0n023682       for
 <myuser@mydomain.com>; Thu, 4 Sep 2014 12:49:47 -0700
Received: from na01-by2-obe.outbound.protection.outlook.com
 (mail-by2on0098.outbound.protection.outlook.com [TheirIP])    by
 PPMail.gsblaw.com with ESMTP id 1p6da7h0jw-1 (version=TLSv1/SSLv3
 cipher=AES256-SHA bits=256 verify=NOT)       for <Myuser@mydomain.com>; Thu, 04 Sep
 2014 12:49:42 -0700
Received: from Theirexchange.theirdomain.com (TheirinternalIP) by
 Theirexchange.theirdomain.com (TheirinternalIP) with Microsoft SMTP
 Server (TLS) id 15.0.1019.16; Thu, 4 Sep 2014 19:49:38 +0000
Received: from Theirexchange.theirdomain.com ([10.141.86.14]) by
 Theirexchange.theirdomain.com ([TheirinternalIP]) with mapi id
 15.00.1019.015; Thu, 4 Sep 2014 19:49:38 +0000
Content-Type: multipart/mixed;
        boundary="_000_9a166afd24964edda2d5439ba3dbe712DM2PR08MB445namprd08pro_"
From: Mr Sender <sender@theirdomain.com>
To: My User <myuser@mydomain.com>, "Another external recipient (someoneelse@anotherdomain.us)"
        <mike@vinco.us>
Subject: FW: A Subject
Thread-Topic: A Subject
Thread-Index: Ac/C2zn97ruwXQpoQtGNrjKOr1NckgFmNoeAAAEpQ2A=
Date: Thu, 4 Sep 2014 19:49:37 +0000
Message-ID: <9a166afd24964edda2d5439ba3dbe712@DM2PR08MB445.theirexchange.theirdomain.com>
References: <3340b0a848f04e3bbb488b4eda93d54e@DM2PR08MB445.theirexchange.theirdomain.com>
 <83FC8FC0E8B91C4594608EA214C0BBAD54BBB844@S1P5DAG8C.EXCHPROD.USA.NET>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <9a166afd24964edda2d5439ba3dbe712@DM2PR08MB445.theirexchange.theirdomain.com>
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [internetIP]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 0324C2C0E2
x-forefront-antispam-report: SFV:NSPM;SFS:(10009015)(6009001)(189002)(199003)(377454003)(164054003)(64706001)(66066001)(19609705001)(15202345003)(50986999)(19300405004)(19625215002)(90102001)(80022001)(20776003)(83322001)(101416001)(99936001)(76176999)(54356999)(81542001)(21056001)(19580395003)(86362001)(4396001)(92566001)(16236675004)(85852003)(551944002)(74502001)(83072002)(87936001)(74662001)(31966008)(107886001)(81342001)(76482001)(46102001)(85306004)(105586002)(33646002)(15975445006)(99396002)(76576001)(74316001)(77982001)(79102001)(95666004)(108616004)(2656002)(106356001)(99286002)(24736002);DIR:OUT;SFP:1101;SCL:1;SRVR:DM2PR08MB446;H:DM2PR08MB445.namprd08.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;MX:1;A:1;LANG:en;
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.27,0.0.0000
 definitions=2014-09-04_03:2014-09-04,2014-09-04,1970-01-01 signatures=0
X-Proofpoint-Spam-Reason: safe
Return-Path: sender@theirdomain.com
X-OriginalArrivalTime: 04 Sep 2014 19:49:47.0046 (UTC) FILETIME=[61900460:01CFC879]

Live exchange server

September 17, 2014, 11:53 pm

≫ Next: Duplication of messages sent to the same domain (site / network segment)

≪ Previous: There's a problem with the recipient's mailbox. Please try resending this message.

$

0

0

Hi

I have install exchange server 2013 and i have configure and able to send and received mail in local domain. Please provide step how to send and received mail all domain ( like yahoo, rediffmail). and how to make  2 or 3 domain in  my exchange server 2013 and each domain configure own user mail id.

Duplication of messages sent to the same domain (site / network segment)

February 25, 2015, 3:46 am

≫ Next: IRM + Mailbox Delegates

≪ Previous: Live exchange server

$

0

0

Hello all,

I am dealing with a strange case where sending messages from my personal account (office365) to multiple recipients inside the same organization (Exchange on-premise infrastructure) it seems that this message is split into multiple copies (different network-id).

Example

Sender: user@office365.com

Recipient: user1@domain.com ; user2@domain.com

The message comes inside the organization in two instances with two distinct network message id. Only thing I can think of is a UTM from Sophos controlling the mail flow in a way (building queues as far as I am aware) but could this be case?

Any ideas are welcome, thanks.

IRM + Mailbox Delegates

March 2, 2015, 3:14 am

≫ Next: Block emails sent to internal mailbox

≪ Previous: Duplication of messages sent to the same domain (site / network segment)

$

0

0

Hi,

Is it possible to block users that have full mailbox access from opening/reading IRM protected email in the mailbox they have access to?

---

Celtic

---

Block emails sent to internal mailbox

March 4, 2015, 5:02 am

≫ Next: Allocate a different IP for subdomain's connector

≪ Previous: IRM + Mailbox Delegates

$

0

0

Dear Exchange Server Expert,

I am being requested to create a rule that will only allow that specific internal mailbox to be able to receive email from certain external domain email addresses. For instance, my company is hhh.com and that specified email address istest@hhh.com. now I want to create a rule at exchange server that this mailbox is only able to receive email from jjj.com domain email addresses. what transport rule should I configured? I know it should be under the transport rule, but what conditions that should I configured.  Please advise.

FYI, our exchange server is actually Exchange Server 2010 SP1.

Thanks so much.

Regards,

H

Allocate a different IP for subdomain's connector

March 4, 2015, 11:49 pm

≫ Next: Duplicate Detection

≪ Previous: Block emails sent to internal mailbox

$

0

0

hi everyone,

We are running Exchange 2013 in a multi-tenant environment. I want to know if it is possible, for each tenant's domain, can I allocate a different IP (internal) for both send and receive connector that is different than the IP of Exchange server?

My plan is to allocate a public IP for each tenant, and NAT to different Internal IP, associate with the corresponded send and receive connector.

Is that even a possible option to do?

Thank everyone!

Hieu

Duplicate Detection

March 2, 2015, 3:02 pm

≫ Next: Live exchange server

≪ Previous: Allocate a different IP for subdomain's connector

$

0

0

Hi,

Is there any way to disable Duplicate Message Detection?

Live exchange server

September 17, 2014, 11:53 pm

≫ Next: Edge Transport Attachment stripping based upon an emails Subject line.

≪ Previous: Duplicate Detection

$

0

0

Hi

I have install exchange server 2013 and i have configure and able to send and received mail in local domain. Please provide step how to send and received mail all domain ( like yahoo, rediffmail). and how to make  2 or 3 domain in  my exchange server 2013 and each domain configure own user mail id.

Edge Transport Attachment stripping based upon an emails Subject line.

March 9, 2015, 8:07 am

≫ Next: There's a problem with the recipient's mailbox. Please try resending this message.

≪ Previous: Live exchange server

$

0

0

I am running Exchange 2010 on-prem with a 2013 Hybrid (including a 2013 Edge Transport server for message handling between on-prem and the o365 tenant) connecting to an o365 tenant. I use EMC's SourceOne for archiving running on-prem. The o365 tenant points to a mailbox on my on-prem Journaling server.

What I am seeing is that when o365 forwards emails as attachments from the cloud back to the on-prem Journaling server it is examining the subject line of the message and making a decision to strip the attachment based upon the very end of the subject line.

Example: A simple text message with a subject line of: "Check out the new web site at www.xyz.com"

The Edge transport server is seeing this as being a ".com" attachment and stripping it off before it gets to the Journaling server. So it does not appear to be looking inside the message to see what it actually is and figure out that it is not a ".com" file but a simple text message.

I have seen this with other file extension types as well. Such as ".exe" . It is also stripping off ".zip" attachments as well, but I understand that and not sure how to deal with it.

Has anyone else experienced this and how have you dealt with it? Microsoft wants me to take the Edge out of play and go directly to from the cloud to an on-prem Exchange server. But that is not an option as the on-prem servers are not exposed to the internet.

Thanks, Bob