Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all 4249 articles
Browse latest View live

Auth Sender Spoofing email address?

$
0
0

Hi All,

I am facing this scenario on Exchange 2010 SP2:

domain\user1 that is a legitimate domain user is authenticating to Exchange Server and sending email using a spoofed email address (that doesn't exist on the system) to send spam (his account pwd has been compromised and they are working on it) in the meantime, how can I prevent the user from using a spoofed email address?

The SMTP transcript is as follows (I obfuscated it for obvius reasons)


EXSERVER\Default EXSERVER,08D276A95907A720,0,10.1.0.6:25,16.16.11.15:61880,+,,
EXSERVER\Default EXSERVER,08D276A95907A720,1,10.1.0.6:25,16.16.11.15:61880,*,SMTPSubmit SMTPAcceptAnySender AcceptRoutingHeaders,Set Session Permissions
EXSERVER\Default EXSERVER,08D276A95907A720,2,10.1.0.6:25,16.16.11.15:61880,>,220 mail.domain.com,
EXSERVER\Default EXSERVER,08D276A95907A720,3,10.1.0.6:25,16.16.11.15:61880,<,EHLO User,
EXSERVER\Default EXSERVER,08D276A95907A720,4,10.1.0.6:25,16.16.11.15:61880,>,250-EXSERVER.domain.net Hello [16.16.11.15],
EXSERVER\Default EXSERVER,08D276A95907A720,5,10.1.0.6:25,16.16.11.15:61880,>,250-SIZE,
EXSERVER\Default EXSERVER,08D276A95907A720,6,10.1.0.6:25,16.16.11.15:61880,>,250-PIPELINING,
EXSERVER\Default EXSERVER,08D276A95907A720,7,10.1.0.6:25,16.16.11.15:61880,>,250-DSN,
EXSERVER\Default EXSERVER,08D276A95907A720,8,10.1.0.6:25,16.16.11.15:61880,>,250-ENHANCEDSTATUSCODES,
EXSERVER\Default EXSERVER,08D276A95907A720,9,10.1.0.6:25,16.16.11.15:61880,>,250-STARTTLS,
EXSERVER\Default EXSERVER,08D276A95907A720,10,10.1.0.6:25,16.16.11.15:61880,>,250-X-ANONYMOUSTLS,
EXSERVER\Default EXSERVER,08D276A95907A720,11,10.1.0.6:25,16.16.11.15:61880,>,250-AUTH NTLM LOGIN,
EXSERVER\Default EXSERVER,08D276A95907A720,12,10.1.0.6:25,16.16.11.15:61880,>,250-X-EXPS GSSAPI NTLM,
EXSERVER\Default EXSERVER,08D276A95907A720,13,10.1.0.6:25,16.16.11.15:61880,>,250-8BITMIME,
EXSERVER\Default EXSERVER,08D276A95907A720,14,10.1.0.6:25,16.16.11.15:61880,>,250-BINARYMIME,
EXSERVER\Default EXSERVER,08D276A95907A720,15,10.1.0.6:25,16.16.11.15:61880,>,250-CHUNKING,
EXSERVER\Default EXSERVER,08D276A95907A720,16,10.1.0.6:25,16.16.11.15:61880,>,250-XEXCH50,
EXSERVER\Default EXSERVER,08D276A95907A720,17,10.1.0.6:25,16.16.11.15:61880,>,250-XRDST,
EXSERVER\Default EXSERVER,08D276A95907A720,18,10.1.0.6:25,16.16.11.15:61880,>,250 XSHADOW,
EXSERVER\Default EXSERVER,08D276A95907A720,19,10.1.0.6:25,16.16.11.15:61880,<,AUTH LOGIN,
EXSERVER\Default EXSERVER,08D276A95907A720,20,10.1.0.6:25,16.16.11.15:61880,>,334 <authentication response>,
EXSERVER\Default EXSERVER,08D276A95907A720,21,10.1.0.6:25,16.16.11.15:61880,>,334 <authentication response>,
EXSERVER\Default EXSERVER,08D276A95907A720,22,10.1.0.6:25,16.16.11.15:61880,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAuthoritativeDomainSender BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
EXSERVER\Default EXSERVER,08D276A95907A720,23,10.1.0.6:25,16.16.11.15:61880,*,domain\user1,authenticated
EXSERVER\Default EXSERVER,08D276A95907A720,24,10.1.0.6:25,16.16.11.15:61880,>,235 2.7.0 Authentication successful,
EXSERVER\Default EXSERVER,08D276A95907A720,25,10.1.0.6:25,16.16.11.15:61880,<,RSET,
EXSERVER\Default EXSERVER,08D276A95907A720,26,10.1.0.6:25,16.16.11.15:61880,>,250 2.0.0 Resetting,
EXSERVER\Default EXSERVER,08D276A95907A720,27,10.1.0.6:25,16.16.11.15:61880,<,MAIL FROM:<officialemail@domain.com>,
EXSERVER\Default EXSERVER,08D276A95907A720,28,10.1.0.6:25,16.16.11.15:61880,*,08D276A95907A720;2015-06-17T02:52:29.721Z;1,receiving message
EXSERVER\Default EXSERVER,08D276A95907A720,29,10.1.0.6:25,16.16.11.15:61880,>,250 2.1.0 Sender OK,
EXSERVER\Default EXSERVER,08D276A95907A720,30,10.1.0.6:25,16.16.11.15:61880,<,RCPT TO:<spammed@highveldmail.co.za>,
EXSERVER\Default EXSERVER,08D276A95907A720,31,10.1.0.6:25,16.16.11.15:61880,>,250 2.1.5 Recipient OK,
EXSERVER\Default EXSERVER,08D276A95907A720,130,10.1.0.6:25,16.16.11.15:61880,<,DATA,
EXSERVER\Default EXSERVER,08D276A95907A720,131,10.1.0.6:25,16.16.11.15:61880,>,354 Start mail input; end with <CRLF>.<CRLF>,
EXSERVER\Default EXSERVER,08D276A95907A720,132,10.1.0.6:25,16.16.11.15:61880,*,Tarpit for '0.00:00:00.828' due to 'DelayedAck',Skipped;QueueLength=914>=100;NextHopDomain=[10.8.0.101]
EXSERVER\Default EXSERVER,08D276A95907A720,133,10.1.0.6:25,16.16.11.15:61880,>,250 2.6.0 <8976f145-897e-4bca-8053-f3615e9db633@EXSERVER.domain.net> [InternalId=9797778] Queued mail for delivery,
EXSERVER\Default EXSERVER,08D276A95907A720,134,10.1.0.6:25,16.16.11.15:61880,<,QUIT,
EXSERVER\Default EXSERVER,08D276A95907A720,135,10.1.0.6:25,16.16.11.15:61880,>,221 2.0.0 Service closing transmission channel,
EXSERVER\Default EXSERVER,08D276A95907A720,136,10.1.0.6:25,16.16.11.15:61880,-,,Local

I checked with Get-AdPermission if NT AUTHORITY\AUTHENTICATED USERS is granted with ms-Exch-SMTP-Accept-Any-Sender on the receive connector but is not.

What am I missing?

Many thanks


Exchange 2013 TransportRoles\Data\Temp filling up disk

$
0
0

I have a single multi-role Exchange 2013 server and it would appear that it's not properly maintaining the temp files for the transport service.  I still have all those folder locations at their default and the problem folder is c:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp

I never had a problem with this in Exchange 2007 but I am used to running a PowerShell script nightly to clean up the IIS log files.  Do I need to do something similar for this temp folder?  Is there a setting I can adjust so that Exchange will limit the size of this folder itself?  If I stop the transport service and delete the files here will I lose anything?

Any suggestions or insight would be greatly appreciated.


SBS 2011 Exchange 2010 DNS MX and FQDN No Telnet from Outside = no external mail

$
0
0

Hi,

Thanks for looking at this.

SBS 2011 running Exchange 2010.

Issue: External mail stopped at 08:16 this morning!

I tried to Telnet from outside and instead of getting the exchange banner like it always did it now returns "press any key to continue...."

I had a check of the internet and couldn't find anything relevant so thought I would post here.

The MX records have always been set to mail.domain.co.uk pointing to the correct static IP of the SBS box. Previously when a telnet session was started to mail.domain.co.uk 25 it would return with the standard Exchange 2010 banner with the FQDN of remote.domain.co.uk and you could then test sending an email to an internal recipient.

There are other domains for which it is authorised and their MX records are set to mail.domain2.co.uk with the static IP of the SBS box. These also fail if you try to Telnet to them with the same "press any key to continue...."

I can telnet ok to remote.domain.co.uk and it logs in ok and I cam send a test mail.

I've rebooted the Server and applied updates it has found but it still refuses Telnet sessions and obviously other external email.

Internal mail is working OK.

Nothing had changed after 8:16 and I've checked the receive connectors and the look OK.

I've updated the main MX to remote.domain.co.uk and am waiting for that to propagate but would be interested to find out the underlying cause.

Thanks for your help.

Pete

Allow Automatic Reply Rules for Select Users, Groups, or Shared Mailboxes

$
0
0

I have a user request to allow automatic replies, in rules, for a shared mailbox in my org. They would like customers to receive a notification when they send a message to the box. I have found a couple of methods to do the forwarding, and prevent looping issues, by first forwarding messages to an Automatic-Reply mailbox/mail enabled folder which, in turn sends the reply.

I am stuck on allowing the Auto-Reply mailbox to create rules with reply-to actions. I know I can allow this at the Org level but, does anyone know of a way to allow this for a specific user, group, or shared mailbox? Also, limiting domains won't work as the incoming messages could be from anywhere. I really need to control who can set up AutoReply rules.

Thanks in advance for any ideas,

Will Perry


Will Perry

Communication Failure occured - Turn on SMTP Authentication - RNDS failed

$
0
0

Today we started having this problem with a external domain that has been working fine before.  This is not happening to all emails or all domains.  

Last week there was problem with a co.uk domain and that went away by itself (i know...)

I've done the tests with Mxtoolbox and exchange connectivity and they all pass. 

The Exchange 2013 server forwards to Smarthost (GFI) 

Server Exchange 2013

Clients: outlook 2010/2013

Diagnostic information for administrators:
Generating server: myserver.mydomain.com
user@externaldomain.com
Remote Server returned '< #5.5.0 smtp;550-Please turn on SMTP Authentication in your mail client. >'
Original message headers:
Received: from myserver.mydomain.com ([10.0.0.16] RDNS failed) by myserver.mydomain.com
 with Microsoft SMTPSVC(7.5.7601.17514); Wed, 17 Jun 2015 11:42:42 -0700
Received: from EMSRV.WL.local (10.0.0.16) by EMSRV.WL.local (10.0.0.16) with Microsoft SMTP
 Server (TLS) id 15.0.1044.25; Wed, 17 Jun 2015 11:38:34 -0700
Received: from EMSRV.WL.local ([fe80::4096:a0c:3cef:13c0]) by EMSRV.WL.local ([fe80::4096:a0c:3cef:13c0%15])
 with mapi id 15.00.1044.021; Wed, 17 Jun 2015 11:38:34 -0700
From: myUser
To: External user
Subject: K
Thread-Topic: K
Thread-Index: AdCpLMPIwf2IRxL0TEmNJMzqXdSUGg==
Date: Wed, 17 Jun 2015 18:38:34 +0000
Message-ID: <459b7995e3d243ad93a61a0f1da9ff73@EMSRV.WL.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.0.0.48]
Content-Type: multipart/related;
boundary="_007_459b7995e3d243ad93a61a0f1da9ff73EMSRVWLlocal_";
type="multipart/alternative"
MIME-Version: 1.0
Return-Path: MyUser@mydomain.com
X-OriginalArrivalTime: 17 Jun 2015 18:42:42.0971 (UTC) FILETIME=[652B66B0:01D0A92D]
<o:p></o:p>


forwarding setting from company mail to external address(like private address)

$
0
0

Exchange 2013 CU 6 Outlook 2013

I just want to set up rule to forbid like forwading from company mail to external for all users.

Are there any ways to do that?


Winsock error code: 10060

$
0
0

Hi everyone, 

I am using Exchange Server 2013 CU7

In the smtp send connector i can see these many logs, please guide me troublshoot

Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: 
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondX.X.X.X:25" X.X.X.X is public ip


Subject Alternative Names in the certificate purchasing

$
0
0
Hi all,

I have a question regarding the SAN and the domain names that will be included in certificate's SAN. The case is as follows:

Server is Exchange Server 2013. Accepted domains are domain111111.com and domain222222.com.

MX record points to mail.domain111111.com, on the public DNS I nave created CNAME record for Autodiscover

autodiscover.domain111111.com. All users have an email account, which is  set at @domain222222.com.

I need to create new certificate request and I wonder whether to include domain domain222222.com in the SAN or to create the

request only with mail.domain111111.com as a common name and autodiscover.domain111111.com as a SAN.



554 5.2.0 STOREDRV.Deliver.Exception:NotSupportedWithServerVersionException

$
0
0

Hi

Currently migrating Exchange 2010 to 2013. Randomly receiving this bounce message.

Remote Server returned '554 5.2.0 STOREDRV.Deliver.Exception:NotSupportedWithServerVersionException; Failed to process message due to a permanent exception with message The mailbox of user xxx@yyy.com that is located on a server that is running version 14 can't be opened on a server that is running version 15. 

Any idea what may be causing this?

Thanks

Irfan


Irfan Goolab SALES ENGINEER (Microsoft UC) MCP, MCSA, MCTS, MCITP, MCT

Track ConnectorID usage for FrontEnd Receive Connectors

$
0
0

Hi everyone,

In past versions of Exchange, message tracking would display the connector ID used for Inbound messages. However, in Exchange 2013, since custom receive connectors should be configured in the FrontEnd Transport service, and this is a stateless service, this information doesn't seem to be available anymore. Does anyone know if there is a way to have this information displayed? Thank you.

Exchange 2013, user is unable to send (goes into the drafts folder), but able to receive, all other users are fine.

$
0
0
Odd one, we had a situation where the exchange logs went crazy causing the DB to dismount, unfortunately this caused a corruption which resulted in repairing the DB to get it backup.

Email flow all happy for everyone except for one user, he is unable to send, but able to receive, his e-mails goes straights into the draft (owa/outlook), we did find a number of e-mail sitting in his outbox also, but since moved, checked the obvious, sent limit's is set to unlimited, verbose logging /message tracking does not picks up any activity, test-mailflow is happy, works when using telnet.... any pointers?

How to traced whether the email has been delivered to recipients mailbox successfully?

$
0
0

Dear Exchange Expert,

Our environment is using Microsoft Exchange Server 2010 SP1 and Outlook 2010 Clients. Sometimes, users have request to check whether the email has been delivered successfully or not. For external email, I think when we can only checked on the Exchange Tracking log explorer and when the event ID is deliver, we are quite ensure that the email has been sent out.

My question is how about internal exchange email? how do we ensure that the email has been delivered to recipients mailbox? Because sometimes some recipients might said they never receive the email. but, in fact the emails has been delivered and they might miss them.

Please advise.

Regards,

H

Send emails internally with problems

$
0
0
Hello, we had a serious problem with Exchange base and the same was lost, then export OST to PST each computer, remove all Exchange users and created again only placing them in a new database. Then on each computer and then import the PST popular the mailbox of each user, it takes work, but had no other way, because the company does not have Exchange backup.

Well, some users are complaining that emails sent to internal recipients are not enough, that is in the same domain.

Comes the message recipient does not exist.

How to solve this problem? Because I have no idea why the Exchange is unable to deliver messages between users of the same domain and that are present in Active Directory.

I look and thank you.

Ivanildo Teixeira Galvão

How to move default folder location of SMTP server to shared folder.

$
0
0
SMTP is installed in two of the WFEs.  Default location of SMTP folders is c:\inetpub\mailroot\. To achieve high availability, we are planning  to implement network shared folder as the default folders for both the SMTP in WFEs. Is it possible to implement? Please advise.

After Upgrade to CU9 is impossible to allow Authenticated Email from FSRM and WSUS

$
0
0

Hello,

the problem happens after you update to CU9 from CU8: authenticated emails from computer running WSUS and File Server Resource Manager (that autenticate using the computer account) are not running anymore. Before they was running.

This is the debug of the SMTP conversation AT THE CU8 -- RUNNING

2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,0,10.0.0.2:25,10.0.0.1:51258,+,,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,1,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,2,10.0.0.2:25,10.0.0.1:51258,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 08:11:38 +0200",
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,3,10.0.0.2:25,10.0.0.1:51258,<,EHLO ITMILDC999,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,4,10.0.0.2:25,10.0.0.1:51258,*,None,Set Session Permissions
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,5,10.0.0.2:25,10.0.0.1:51258,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,6,10.0.0.2:25,10.0.0.1:51258,>,250-SIZE,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,7,10.0.0.2:25,10.0.0.1:51258,>,250-PIPELINING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,8,10.0.0.2:25,10.0.0.1:51258,>,250-DSN,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,9,10.0.0.2:25,10.0.0.1:51258,>,250-ENHANCEDSTATUSCODES,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,10,10.0.0.2:25,10.0.0.1:51258,>,250-AUTH NTLM,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,11,10.0.0.2:25,10.0.0.1:51258,>,250-8BITMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,12,10.0.0.2:25,10.0.0.1:51258,>,250-BINARYMIME,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,13,10.0.0.2:25,10.0.0.1:51258,>,250 CHUNKING,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,14,10.0.0.2:25,10.0.0.1:51258,<,AUTH ntlm,
2015-06-23T06:11:39.435Z,ITMILEX999\Internal,08D27B82C2B20D7C,15,10.0.0.2:25,10.0.0.1:51258,>,334 <authentication response>,
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,16,10.0.0.2:25,10.0.0.1:51258,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T06:11:39.481Z,ITMILEX999\Internal,08D27B82C2B20D7C,17,10.0.0.2:25,10.0.0.1:51258,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,18,10.0.0.2:25,10.0.0.1:51258,*,,Proxy session was successfully set up. Outbound session will now be proxied
2015-06-23T06:11:39.513Z,ITMILEX999\Internal,08D27B82C2B20D7C,19,10.0.0.2:25,10.0.0.1:51258,>,235 2.7.0 Authentication successful,
2015-06-23T06:11:39.763Z,ITMILEX999\Internal,08D27B82C2B20D7C,20,10.0.0.2:25,10.0.0.1:51258,-,,Local

This is the debug after upgrading to CU9 -- BROKEN

2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,0,10.0.0.2:25,10.0.0.1:51489,+,,
2015-06-23T07:34:12.165Z,ITMILEX999\Internal,08D27B9E1BAF1B57,1,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.196Z,ITMILEX999\Internal,08D27B9E1BAF1B57,2,10.0.0.2:25,10.0.0.1:51489,>,"220 ITMILEX999.contoso.com Microsoft ESMTP MAIL Service ready at Tue, 23 Jun 2015 09:34:11 +0200",
2015-06-23T07:34:12.462Z,ITMILEX999\Internal,08D27B9E1BAF1B57,3,10.0.0.2:25,10.0.0.1:51489,<,EHLO ITMILDC999,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,4,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,5,10.0.0.2:25,10.0.0.1:51489,>,250-ITMILEX999.contoso.com Hello [10.0.0.1],
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,6,10.0.0.2:25,10.0.0.1:51489,>,250-SIZE,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,7,10.0.0.2:25,10.0.0.1:51489,>,250-PIPELINING,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,8,10.0.0.2:25,10.0.0.1:51489,>,250-DSN,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,9,10.0.0.2:25,10.0.0.1:51489,>,250-ENHANCEDSTATUSCODES,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,10,10.0.0.2:25,10.0.0.1:51489,>,250-AUTH NTLM,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,11,10.0.0.2:25,10.0.0.1:51489,>,250-8BITMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,12,10.0.0.2:25,10.0.0.1:51489,>,250-BINARYMIME,
2015-06-23T07:34:12.619Z,ITMILEX999\Internal,08D27B9E1BAF1B57,13,10.0.0.2:25,10.0.0.1:51489,>,250 CHUNKING,
2015-06-23T07:34:12.744Z,ITMILEX999\Internal,08D27B9E1BAF1B57,14,10.0.0.2:25,10.0.0.1:51489,<,AUTH ntlm,
2015-06-23T07:34:12.791Z,ITMILEX999\Internal,08D27B9E1BAF1B57,15,10.0.0.2:25,10.0.0.1:51489,>,334 <authentication response>,
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,16,10.0.0.2:25,10.0.0.1:51489,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-06-23T07:34:13.682Z,ITMILEX999\Internal,08D27B9E1BAF1B57,17,10.0.0.2:25,10.0.0.1:51489,*,CONTOSO\ITMILDC999$,authenticated
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,18,10.0.0.2:25,10.0.0.1:51489,*,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,19,10.0.0.2:25,10.0.0.1:51489,*,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user."" 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 10.0.0.2:465"
2015-06-23T07:34:26.949Z,ITMILEX999\Internal,08D27B9E1BAF1B57,20,10.0.0.2:25,10.0.0.1:51489,*,None,Set Session Permissions
2015-06-23T07:34:26.965Z,ITMILEX999\Internal,08D27B9E1BAF1B57,21,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user',
2015-06-23T07:34:32.282Z,ITMILEX999\Internal,08D27B9E1BAF1B57,22,10.0.0.2:25,10.0.0.1:51489,>,535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,23,10.0.0.2:25,10.0.0.1:51489,<MAIL FROM:<FSRM @ contoso.com>,
2015-06-23T07:34:32.314Z,ITMILEX999\Internal,08D27B9E1BAF1B57,24,10.0.0.2:25,10.0.0.1:51489,*,Tarpit for '0.00:00:05' due to '530 5.7.1 Client was not authenticated',
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,25,10.0.0.2:25,10.0.0.1:51489,>,530 5.7.1 Client was not authenticated,
2015-06-23T07:34:37.334Z,ITMILEX999\Internal,08D27B9E1BAF1B57,26,10.0.0.2:25,10.0.0.1:51489,-,,Local

Ciao,

Luca


Exchange Mail Flow Test Fails, But all appears normal and we have no problems?????

$
0
0

When I run a Mail Flow test on our Exchange Server it fails by just timing out. But as far as I can tell, all is working normally. What can I do to look further into this matter to see if something is actually wrong.

We are a small shop running 2 Exchange 2013 Servers in a DAG. Each server is in a different location.

All suggestions are appreciated......

Roy

Exchange 2013 Edge outgoing mail - Unable to get any delivery failure for incorrect email address

$
0
0

Hi,

Using exchange 2013 server using EDGE 2013 for outgoing email flow. We are not getting any delivery failure message notification when we sent an incorrect email address.

====== Edge server message tracking details====

ConnectorId             : EdgeSync - Default-First-Site-Name to Internet

Source                  : SMTP

EventId                 : FAIL

InternalMessageId       : 7683696492577

MessageId               : <1900e46b6fc246ce9305a3e9a235567b@servername.local>

Recipients              :{mraffi22222@xyz.com}

RecipientStatus         : {[{LRT=};{LED=550 #5.1.0 Address rejected.};{FQDN=};{IP=}]}

Any help? why no delivery failure for this incorrect email address?


MD


Fichier ConfigurationServer.lkg manquand - File ConfigurationServer.lkg missing

$
0
0

Hello,

I have a problem on an Echange Server 2013.

It's Unable to start Microsoft Exchange Transport and Microsoft Filtering Management Service (FMS) and it appears "File ConfigurationServer.lkg missing" in the Task Manager.

Have you got any idea ?

Thanks

Seb

Exchange Server 2010 receiving issue for a few users

$
0
0

We have Exchange 2010 running on a single server for about 50-60 users. Most of them send and receive mail just fine, however a couple of them cannot receive messages from anyone outside the company. They can send ok but no email from a user outside our domain makes it in. I have run the Remote Connectivity Analyzer and it fails the inbound SMTP test with the following error: Message: Mailbox unavailable. The server response was: 5.7.1 Recipient rejected (R4). I have searched and found some information about setting SMTP to deliver to the IP address of the Exchange server but that does not seem to have made a difference. Any suggestions would be welcome.

Thanks,

was deleted without being read on

$
0
0

Hello, guys.

I have an environment with Exchange Server 2013 and some users they are receiving the following error or report.

Subject: Not read: FW: Teste message

Date: June 22, 2015 at 10:15:21 GMT-3
To: Ricardo  <ricardo.@domain.com.br>

Your message

To:
Subject: FW: Teste message
Sent: Wednesday, June 19, 2013 9:02:06 PM (UTC-03:00) Brasilia

was deleted without being read on Monday, June 22, 2015 10:15:21 AM (UTC-03:00) Brasilia.



André Cangussu

Viewing all 4249 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>