Dear all,

I have users with 2nd mailbox attached to their Outlook, after movement the mailboxes to Exchange 2013 they're no longer able to send any e-mails from the 2nd mailbox

And they also get this ERROR:0x80070005-00000000-00000000 

If I attach the same mailbox to my Outlook, I have no problems with sending e-mails. 

Does anyone know what might that be?

Thank you

Hello,

I'm running an exchange 2013 system and we have an issue that if users sent Encrypted emails they show up on older versions of Outlook and mobile phones as ATT00001 and ATT00002.bin. It doens't matter from what client we sent it. And it is not an issue for Outlook 2013 and newer mobile phones like Vlackberry 10 or iOS8 devices, but on older devices it doesnt display correctley, and in OWA it is un readable (with S/MIME extention installed). When I look at the header it says|:

Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary

And this is weird as I have TNEF turned off :

RunspaceId                           : 9dce606b-5c50-45bb-ab6e-a092b3a97f37
DomainName                           : *
IsInternal                           : False
TargetDeliveryDomain                 : False
ByteEncoderTypeFor7BitCharsets       : Use7Bit
CharacterSet                         : iso-8859-1
NonMimeCharacterSet                  : iso-8859-1
AllowedOOFType                       : External
AutoReplyEnabled                     : False
AutoForwardEnabled                   : False
DeliveryReportEnabled                : True
NDREnabled                           : True
MeetingForwardNotificationEnabled    : False
ContentType                          : MimeText
DisplaySenderName                    : True
PreferredInternetCodePageForShiftJis : Undefined
RequiredCharsetCoverage              :
TNEFEnabled                          : False
LineWrapSize                         : Unlimited
TrustedMailOutboundEnabled           : False
TrustedMailInboundEnabled            : False
UseSimpleDisplayName                 : False
NDRDiagnosticInfoEnabled             : True
MessageCountThreshold                : 2147483647
AdminDisplayName                     :
ExchangeVersion                      : 0.1 (8.0.535.0)
Name                                 : Default
DistinguishedName                    : CN=Default,CN=Internet Message Formats,CN=Global Settings,CN=DOMAINCOM,CN=Mi
                                       crosoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity                             : Default
Guid                                 : 64165533-258a-4c3a-b167-153b48c04eeb
ObjectCategory                       : cdomain.com/Configuration/Schema/ms-Exch-Domain-Content-Config
ObjectClass                          : {top, msExchDomainContentConfig}
WhenChanged                          : 7-5-2015 11:38:29
WhenCreated                          : 29-4-2015 15:56:38
WhenChangedUTC                       : 7-5-2015 09:38:29
WhenCreatedUTC                       : 29-4-2015 13:56:38
OrganizationId                       :
OriginatingServer                    : dc.domain.com
IsValid                              : True
ObjectState                          : Unchanged

I've tryed changing the MIME types and message encoding options but keep getting the same result,

Is there maybe some setting that overrides the exchange conversion, that I'm overlooking?

Hi all, I'm trying to set up an auto reply message for a mailbox, but I'm unable to include the break lines.

I tryed several methods:

1. just pasting the text:

[PS] C:\Windows\system32>Set-MailboxAutoReplyConfiguration -identity testexchange -ExternalMessage "This is an auto reply message.
>> this is the second line"
>>

i receive a mail like this:

This is an auto reply message.this is the second line

2. with a variable in power shell and adding exchange 2013 snapin:

PS C:\> $reply = "first line
>> second line"
>>
PS C:\> Add-PSSnapin Microsoft-Exchange.Management.Powershell.snapin
PS C:\> Set-MailboxAutoReplyConfiguration -Identity testexchange -ExternalMessage $reply

Again, i receive a mail like: 

first linesecond line

3. I tried fetching the text from a file:

[PS] C:\>$reply=Get-Content reply.txt

[PS] C:\>Set-MailboxAutoReplyConfiguration -Identity testexchange -ExternalMessage $reply

4. I also tried with a powershell script:
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.snapin

$x = @"

this is the autoreply
second line
third line

"@

set-mailboxautoreplyconfiguration -identity testexchange -externalmessage $x

again, i receive a mail like: this is the autoreplysecond linethird line

Thank you all,

I need create a new rule in my Exchange 2013 system to resolve my company's demands

I checked this link but don't enough information to do that, anybody can help me ? Thank so much !

https://technet.microsoft.com/en-us/library/jj919236%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

I'm having a hard time getting Exchange relaying the mail from my applications to external domains.

I have setup a recieve connector as Hub Transport Custom connector.

• Externally secured (for example, with IPsec)
• Exchange Servers
• Anonymous Users

I have no clue what i did wrong.. I can send to internal Accepted domains but not outside of my company.

Thanks in advance,

Kevin

Has anyone else been getting hit with more than normal spam the past 2 weeks? I have checked all my FIPS updates are running as expected, but it's just non-stop.

I also wanted to create a rule to block certain top level domains like .ru or .ga  or .eu

Does anyone have any suggestions on how to do that? I haven't found a way to do a wildcard

thanks!

Hey Guys,

since we upgraded from Exchange 2010 to Exchange 2013 (SP1) any SMTP Receive Connector we create (including the default one) show the same strange behavior. When you send an email (no matter if internal or external) it sometimes takes up to 30 seconds for the exchange server to acknowledge the message. Using the SMTP log I see the following entries:

2014-08-08T08:58:29.053Z,                       MAIL FROM:<test@test.de>,

2014-08-08T08:58:29.053Z,                       SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2014-08-08T08:58:29.053Z,                       receiving message

2014-08-08T08:58:29.053Z,                       250 2.1.0 Sender OK,

2014-08-08T08:58:29.053Z,                       RCPT TO:<fake@mail.de>,

2014-08-08T08:58:29.053Z,                       250 2.1.5 Recipient OK,

2014-08-08T08:58:29.053Z,                       DATA,

2014-08-08T08:58:29.053Z,                       354 Start mail input; end with <CRLF>.<CRLF>,

2014-08-08T08:58:29.068Z,                       Proxy destination(s) obtained from OnProxyInboundMessage event

2014-08-08T08:58:40.960Z,                       "250 2.6.0 <5160cd2a-9160-4a35-9007-1f9c17761bc0@--------> [InternalId=17776869639170, Hostname=-----------] Queued mail for delivery",

As you can see there’s a delay between 08:58:29 and 08:58:40 where nothing happens. The sending smtp service waits for the server to acknowledge the message – at least that’s what I guess. Since we use this kind of connector a lot for internal mail traffic with non-Outlook clients it is essential to get rid of this issue. For example using Trac Ticket system or Subversion also leads to slow or delayed responses. Creating a ticket in Trac sometimes takes up to a Minute since several emails are created and sent in background processes. We didn’t have this issue with Exchange 2010 and I actually couldn’t find much using google. 

Since there's no error showing it's quite difficult to track down the issue. After I did some researching I tried configuring the receive connector to change this behavior but nothing helped. I tested the following options:

-         MaxAcknowledgementDelay 00:00:00

-         TarpitInterval 00:00:00

-         MessageRateSource None

-         MessageRateLimit unlimited

-         MaxInboundConnectionPercentagePerSource: 20

-         MaxInboundConnectionPerSource 100

 I Also took a look at the Throttling Policies with no luck either. 

Calling the Microsoft support simply led to the typical “we do not support 3^rd party issues”. In fact this is NOT a third party issue but arguing didn't help. I tested every possible solution I found and after weeks I simply dont' have the slightest idea any more, how to solve the problem.

Some information about our Exchange environment:

-         Exchange DAG with 2 servers

-         Windows Server 2012 (latest updates)

-         Exchange 2013 SP1 installed

Disabling DAG members also didn’t help and all the members show the same behavior no matter which connector I choose to use.  

Any hint or idea would be very much appreciated.

Thanks,

Christoph

Hi, I have four exchange servers, 2 mailbox servers in a dag and 2 CAS servers.

users are receiving multiple advertisement and junk emails.

I block one by one using set-senderfilteringconfig

how to eliminate unneeded emails from Exchange before it reach user mailboxes.

Mashhour Faraj

Dear all,

I have the issue with number of the users who can't connect to the mailbox after migration from 2010 to 2013 Exchange server. 

If I go to Exchange Proxy settings in Outlook it still points to old URL records, when I change URL to the Exchange 2013 it works ok, but after closing the Outlook the problem appears again.

Mailboxes are copied to Exchange 2013 without any problems

Please, help

Thank you in advance

Hello,

I have setup External Relay connector on the Exchange 2013 server, but cannot send anonymous messages.

External Relay connector configuration:

Role: Front End Transport
Type: Custom
Security: Anonymous Users
Scoping - Remote Network Settings: "servers, printers IP" which send anonymous messages
Scoping - Network adapter bindings: all available IPv4, 25 port.

Permissions for Relay Connector was set:

Get-ReceiveConnector -Id EX1\Relay-Connector | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Information from SMTP log:

2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,124,172.16.100.3:2525,172.16.100.3:48646,<,XPROXYFROM SID=08D2608379087E4A IP=192.168.2.10 PORT=3349 DOMAIN=dc2 SEQNUM=1 PERMS=1077 AUTHSRC=Anonymous,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,125,172.16.100.3:2525,172.16.100.3:48646,>,250 XProxyFrom accepted,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,126,172.16.100.3:2525,172.16.100.3:48646,<,MAIL FROM:<ServerLogs@internal.domain> SIZE=0 AUTH=<>,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,127,172.16.100.3:2525,172.16.100.3:48646,*,SMTPSubmit SMTPSubmitForMLS SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassMessageSizeLimit SMTPSendEXCH50 SMTPAcceptEXCH50 AcceptRoutingHeaders AcceptForestHeaders AcceptOrganizationHeaders SendRoutingHeaders SendForestHeaders SendOrganizationHeaders SendAs SMTPSendXShadow SMTPAcceptXShadow SMTPAcceptXProxyFrom SMTPAcceptXSessionParams SMTPAcceptXMessageContextADRecipientCache SMTPAcceptXMessageContextExtendedProperties SMTPAcceptXMessageContextFastIndex SMTPAcceptXAttr SMTPAcceptXSysProbe,Set Session Permissions
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,128,172.16.100.3:2525,172.16.100.3:48646,*,08D264DFE8DEA0BF;2015-05-25T10:52:27.466Z;6,receiving message
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,129,172.16.100.3:2525,172.16.100.3:48646,<,RCPT TO:<user@external.domain>,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,130,172.16.100.3:2525,172.16.100.3:48646,>,250 2.1.0 Sender OK,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,131,172.16.100.3:2525,172.16.100.3:48646,>,250 2.1.5 Recipient OK,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,132,172.16.100.3:2525,172.16.100.3:48646,<,DATA,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,133,172.16.100.3:2525,172.16.100.3:48646,>,354 Start mail input; end with <CRLF>.<CRLF>,
2015-05-25T10:55:01.929Z,EX1\Default EX1,08D264DFE8DEA0BF,134,172.16.100.3:2525,172.16.100.3:48646,*,,receiving message with InternetMessageId <156f07a15cf04657bc07983e9b722fec@EX1.internal.domain>
2015-05-25T10:55:02.133Z,EX1\Default EX1,08D264DFE8DEA0BF,135,172.16.100.3:2525,172.16.100.3:48646,>,"250 2.6.0 <156f07a15cf04657bc07983e9b722fec@EX1.internal.domain> [InternalId=721554505867, Hostname=EX1.internal.domain] Queued mail for delivery",
2015-05-25T10:55:28.178Z,EX1\Default EX1,08D264DFE8DEA0CA,0,172.16.100.3:2525,172.16.100.3:48951,+,,
2015-05-25T10:55:28.178Z,EX1\Default EX1,08D264DFE8DEA0CA,1,172.16.100.3:2525,172.16.100.3:48951,*,None,Set Session Permissions

or

2015-05-25T11:34:44.366Z,EX1\Default EX1,08D264F5AEFC2646,54,172.16.100.3:2525,172.16.100.3:52949,<,XPROXYFROM SID=08D2608379087ECB IP=192.168.2.10 PORT=3621 DOMAIN=dc2 SEQNUM=1 PERMS=1077 AUTHSRC=Anonymous,
2015-05-25T11:34:44.366Z,EX1\Default EX1,08D264F5AEFC2646,55,172.16.100.3:2525,172.16.100.3:52949,>,250 XProxyFrom accepted,
2015-05-25T11:34:44.366Z,EX1\Default EX1,08D264F5AEFC2646,56,172.16.100.3:2525,172.16.100.3:52949,<,MAIL FROM:<ServerLogs@internal.domain> SIZE=0 AUTH=<>,
2015-05-25T11:34:44.366Z,EX1\Default EX1,08D264F5AEFC2646,57,172.16.100.3:2525,172.16.100.3:52949,*,SMTPSubmit SMTPSubmitForMLS SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassMessageSizeLimit SMTPSendEXCH50 SMTPAcceptEXCH50 AcceptRoutingHeaders AcceptForestHeaders AcceptOrganizationHeaders SendRoutingHeaders SendForestHeaders SendOrganizationHeaders SendAs SMTPSendXShadow SMTPAcceptXShadow SMTPAcceptXProxyFrom SMTPAcceptXSessionParams SMTPAcceptXMessageContextADRecipientCache SMTPAcceptXMessageContextExtendedProperties SMTPAcceptXMessageContextFastIndex SMTPAcceptXAttr SMTPAcceptXSysProbe,Set Session Permissions
2015-05-25T11:34:44.381Z,EX1\Default EX1,08D264F5AEFC2646,58,172.16.100.3:2525,172.16.100.3:52949,*,08D264F5AEFC2646;2015-05-25T11:34:44.303Z;1,receiving message
2015-05-25T11:34:44.381Z,EX1\Default EX1,08D264F5AEFC2646,59,172.16.100.3:2525,172.16.100.3:52949,<,RCPT TO:<user@external.domain>,
2015-05-25T11:34:44.397Z,EX1\Default EX1,08D264F5AEFC2646,60,172.16.100.3:2525,172.16.100.3:52949,>,250 2.1.0 Sender OK,
2015-05-25T11:34:44.397Z,EX1\Default EX1,08D264F5AEFC2646,61,172.16.100.3:2525,172.16.100.3:52949,>,250 2.1.5 Recipient OK,
2015-05-25T11:34:44.397Z,EX1\Default EX1,08D264F5AEFC2646,62,172.16.100.3:2525,172.16.100.3:52949,<,DATA,
2015-05-25T11:34:44.397Z,EX1\Default EX1,08D264F5AEFC2646,63,172.16.100.3:2525,172.16.100.3:52949,>,354 Start mail input; end with <CRLF>.<CRLF>,
2015-05-25T11:34:44.397Z,EX1\Default EX1,08D264F5AEFC2646,64,172.16.100.3:2525,172.16.100.3:52949,*,,receiving message with InternetMessageId <51ee3540ba1a47bc95f924a065c4d2f9@EX1.internal.domain>
2015-05-25T11:34:45.006Z,EX1\Default EX1,08D264F5AEFC2646,65,172.16.100.3:2525,172.16.100.3:52949,>,"250 2.6.0 <51ee3540ba1a47bc95f924a065c4d2f9@EX1.internal.domain> [InternalId=725849473132, Hostname=EX1.internal.domain] Queued mail for delivery",
2015-05-25T11:34:53.069Z,EX1\Default EX1,08D264F5AEFC2646,66,172.16.100.3:2525,172.16.100.3:52949,<,RSET,
2015-05-25T11:34:53.084Z,EX1\Default EX1,08D264F5AEFC2646,67,172.16.100.3:2525,172.16.100.3:52949,>,250 2.0.0 Resetting,

I don't know if it could be related, but there is Exchange 2007 in other AD site, which works properly as Relay server.
Servers now in coexistence period and everything seems to work fine except Relay connector on the Exchange 2013 server.

Can someone help with this problem?

Hi,

Does Exchange 2013 support UTF-8 charset for IMAP Search?

Cheers,

Saaj

I want to:

• generate mailbox usage statistics
• convert it to pdf (if possible)
• send this file as attachment
• use windows scheduler to send mail

Can someone show me how to accomplish this?

I am using:

• Exchange 2013 
• Windows Server 2012

Thanks

This posting is provided AS-IS with no warranties/guarantees and confers no rights.

we have Exchange server 2013  4 mailbox servers and 4 CAS server in two sites there is between 10 to 20 Minutes delay in mail flow between internal users. 

hass

hi There,

My organization's CEO's email address was spoofed by an external source, due to which our CEO started receiving NDR's from whom the spoofer has sent the emails to. As I have identified the source IP from header(NDRs header), I would like to know how black list the source IP.

Many blogs and websites says to ignore the spoof or to modify the email address or to create rules to delete the NDR emails that are specifically coming from that recipient. but I'm little hesitate to say this to my management as the affected user is CEO.

Greetings,

We're trying to roll out TLS 1.2 in our test environment and can't seem to get Exchange to work with the protocol.

We've been using this method to enable TLS 1.2 (and disable the other protocols - TLS1.0, SSL2.0, SSL3.0, PCT1.0): http://www.adminhorror.com/2011/10/enable-tls-11-and-tls-12-on-windows_1853.html

We originally tried using Exchange 2010 on 2008 R2, but then I ran across this article saying that it is not supported: http://support.microsoft.com/kb/2709167/en-us

We've since tried to set it up with Exchange 2013 on Server 2012. Still no luck. The only time Exchange wants to work is when TLS1.0 is enabled.

I suspect that TLS1.1 and TLS 1.2 are also not supported on Exchange 2013, or that I'm changing the wrong registry keys, but I wanted to find confirmation. I've searched extensively and can't find any documentation leading me to believe one way or the other if it's supported.

Any help or insight would be greatly appreciated. Thanks!

--Aric

Hi

I'm using Exchange 2010, I just wanted to know is there any way to set a Auto Reply on distribution lists.

Please take it in consideration that i do not want to create or use any existing mailbox, i just want to use the Distribution Lists.

Regards

**************** Sincerely Yours Ziyaei Ali *****************

Dear All ,  

i have one exchange server 2013 and i lost the power for about 12 hours and after server getting up i found that emails not received at the time the exchange was down and email not their ?

any idea is this correct or if there is a way to get the emails during the time server is down ?

Hi, 

Done this once a few years back but for the life of me cannot remember the mailflow settings!

I have an Exchange server 2003 to upgrade to 2010 then onto O365, the E2010 has gone in with no issues and able to see all of the mailboxes that are in 'Legacy Mailbox' with the exception of the one mailbox that I have moved over to the 2010 server which shows as expected 'User Mailbox' 

From the OWA I am able to send out from this account but when replying I get a bouce back saying:

could not be delivered. The problem appears to be :

-- Recipient email address is possibly incorrect

Additional information follows :

-- 5.7.1 Recipient rejected (R4)

On the E2003 in Routing groups there is the "Routing Group Connector" and shows the 2010 server in the bridgeheads. 

In the Default SMTP Virtual Server, i have also set this to relay to the e2010 server

On the 2010 server I have set a new receive connector to accept mail from the e2003 server. 

I do not have the luxury of turning off the E2003 server as yet, I need the emails to route through the 2003 to the e2010 for a day or two.

Many thanks

Wayne