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

users send messages as ATT00001 with ATT00002.bin attachements with SMIME cant seem to change this

May 11, 2015, 9:54 am
$
0
0

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?

↧
Search

winmail.dat Attachments are received whether TNEF is disabled or not

January 8, 2014, 7:49 am
$
0
0

Hi,

we've got some issues when sending emails to some linux recipients, that attachments or s/mime signed emails are converted to the dreaded winmail.dat attachements. 

On Exchange 2010 i've just configured the corresponding remote domain (or the default one) to disable TNEF sending to this mail domain.

Apparently with Exchange 2013 this setting does not work anymore. With setting the parameter "TNEFenabled" to $false, the recipients still get winmail.dat attachments.

do you have any idea how to work this out?

Kind regards,

Peter



↧
↧

421 4.4.2 Connection dropped due to TimedOut.

August 30, 2016, 12:05 am
$
0
0

We are having Exchange 2013 and all emails are comin & going fine except 1 domain.

From this domain, we can receive the emails but when we send email to them we receive below notification.

Diagnostic information for administrators:<o:p></o:p>

Generating server:FQDN of my mail server
Receiving server: FQDN of far end server (IP address of far end server)

Recipeint email address
Remote Server at FQDN and IP of far end returned '400 4.4.7 Message delayed'
24-08-2016 07:07:58 - Remote Server at FQDN and IP of far end returned '441 4.4.1 Error encountered while communicating with primary target IP address: "421 4.4.2 Connection dropped due to TimedOut." 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 IP of far end:25'

All emails to other domains goes well.

Thanks, Rishi Pandit.

↧

Restore Exchange Server 2013 Database

August 30, 2016, 2:45 am
$
0
0
I backup exchange server .edb database file only without any logs thinking this is the only database required. Now I have made few searches and I need some help on restoring the database .EDB file only i have got to the new exchange server. Please help!
↧

Exchange 2013 DAG

August 30, 2016, 12:52 am
$
0
0

Hi team

Now if we shutdown Exchange 1 all the users are automatically redirected to Exchange 2.

DNS round robin seems to be working fine.

But when all the users were redirected to Exchange 2 i see that users cannot receive emails internally and externally.

Then we checked on Exchange 2 server, Queue viewer and found that Exchange 2 is relaying on exchange 1 mailbox for SMTP but Exchange 1 is  down and users cannot receive emails on their mailbox.

Can you say me what could be the issue is this related to DAG.

Also i think i should inform you that when DAG was created we have single nic, Later we created another nic and enabled replication on it.

Awaiting for your reply..


↧
↧

Problem with email sent with PGP encryption - plain text / tnef

August 30, 2016, 4:31 am
$
0
0


I have a small problem when sending email signed and encrypted with PGP, all recipients receive a att.00001 with nothing inside  and att00002.bin file that when opened with notepad shows the -----BEGIN PGP MESSAGE-----. Exchange just refuses to send in plain text format. TNEF enable is set to false, aslo I try and do disable, delete and recreate Front end connector , disabled all exchange spam filters. doesn't matter if the receiver uses Exchange or not , the email is delivered in the same way with attachments

When email is sent in clear with no encryption, it behaves just fine 

Using winserver2012 + Exchange 2013 + Blackberry Enterprise 12.

I have no more ideas.

[PS] C:\Windows>get-remotedomain | fl
RunspaceId                           : b68c71e0-7c14-4a41-9f58-0ec819205
DomainName                           : *
IsInternal                           : False
TargetDeliveryDomain                 : False
ByteEncoderTypeFor7BitCharsets       : Undefined
CharacterSet                         : iso-8859-1
NonMimeCharacterSet                  : iso-8859-1
AllowedOOFType                       : External
AutoReplyEnabled                     : False
AutoForwardEnabled                   : False
DeliveryReportEnabled                : True
NDREnabled                           : True
MeetingForwardNotificationEnabled    : False
ContentType                          : MimeHtmlText
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 Fo
                                       Organization,CN=Microsoft
                                       Exchange,CN=Services,CN=Configura
Identity                             : Default
Guid                                 : da633723-7b11-42cb-abad-bb403b21a
ObjectCategory                       : ad.corpdatatechmail.com/Configuration/Sc
ObjectClass                          : {top, msExchDomainContentConfig}
WhenChanged                          : 8/29/2016 9:02:07 PM
WhenCreated                          : 6/9/2016 2:04:08 AM
WhenChangedUTC                       : 8/29/2016 6:02:07 PM
WhenCreatedUTC                       : 6/8/2016 11:04:08 PM
OrganizationId                       :
OriginatingServer                    : win2.ad.corpdatatechmail.com
IsValid                              : True
ObjectState                          : Unchanged

↧

Inbound Proxy Probe Undeliverable (Health Mailbox)

January 25, 2016, 3:35 am
$
0
0

Hi, we've recently switched our anti spam filter to Mimecast and I've started noticing in the 'Bounce' section an email every couple of minutes being caught as undeliverable, shown below. This was most likely happening before, but our previous anti spam filter was useless!

I'm aware of the HealthMailboxes and from my understanding they should be receiving these emails, rather than attempting to send them externally. I've managed to catch one of these emails and it contains the following content:

Delivery has failed to these recipients or groups:
HealthMailbox3ac30e4d99434adaa06f83ce3062fb1f@OurDomain.co.uk
The email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk.


Diagnostic information for administrators:
Generating server: mailserver2.OurDomain.lan
HealthMailbox3ac30e4d99434adaa06f83ce3062fb1f@OurDomain.co.uk
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Original message headers:
Received: from mailserver2.OurDomain.lan (192.168.0.10) by
 mailserver2.OurDomain.lan (192.168.0.10) with Microsoft SMTP Server (TLS) id
 15.0.1130.7; Mon, 25 Jan 2016 11:15:44 +0000
Received: from InboundProxyProbe (127.0.0.1) by mailserver2.OurDomain.lan
 (127.0.0.1) with Microsoft SMTP Server id 15.0.1130.7 via Frontend Transport;
 Mon, 25 Jan 2016 11:15:44 +0000
X-MS-Exchange-ActiveMonitoringProbeName: OnPremisesInboundProxy_2
X-Exchange-Probe-Drop-Message: FrontEnd-CAT-250
Subject: Inbound proxy probe
Message-ID: <1125c87ee52942dea2fd46d60221eec2@mailserver2.OurDomain.lan>
From: <inboundproxy@contoso.com>
To: Undisclosed recipients:;
Return-Path: inboundproxy@contoso.com
Date: Mon, 25 Jan 2016 11:15:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

The listed mailbox does exist and contains the SMTP address. I've followed steps to rebuild the mailboxes and they are recreated as expected, but then within moments of them all being recreated the issue starts happening again.

Our system contains 3 mailbox servers all members of a DAG, each containing a copy of 4 databases. They are all running Exchange 2013 CU10.

Thanks for any help.

↧

Outlook Connectivity Failed with Exchange Server 2016

August 30, 2016, 2:42 pm
$
0
0
I am having issues with DNS autodiscover settings on my GoDaddy DNS portal I guess. I have recently installed new exchange server 2016 and the incoming/outgoing email flow seems to be working. The only issue is with the Outlook client as it won't connect with the Exchange server or won't find the server at all. I have tested through https://testconnectivity.microsoft.com and it fails there as well. Any guidance or help on this matter is appreciated. Thanks
↧
Search

Accept no_replay email from specific destination

August 30, 2016, 6:45 am
$
0
0
Hello,

As the title describe. When a custmer is using a no_replay@domain.com email to communicate some information. We do not receive those emails and the sender get a messga esaying that our domain is "suspects your message is spam and rejected it." I'm wondering if it's possible to accepte or allow no-replay emails to be forworded to theire destination like a normal message.

Thank you so much,
↧
↧

Send email from specific IP

August 30, 2016, 8:33 pm
$
0
0

Is it possible to have Exchange send via different IP addresses for different users, or domains?

We send email from our Exchange servers on behalf of several different clients. Several clients want their own IP address so the other clients don't send out spam and get black listed.

I can't find any documentation on if this is possible, or how you would manage it?

Simon Holman
Expeed Technology
Australian Web Hosting

↧

Receive strange emails internally from some non valid user on Exchange

August 31, 2016, 5:26 am
$
0
0

Dears,

Some Of users in our Exchange are receiving email With Attachments From (scott163@domain.com) And (socorro33@domain.com ) where domain.com represents our SMTP address. We have Exchange 2013. When we Search For those 2 mailboxes we find that they do not exist In Our Exchange (we Think It's A Virus), how can we solve this issue?

↧

Exchange 2013 mail flow problem

April 4, 2013, 12:32 am
$
0
0


Hello!

We have problem, could not send mails via Exchange 2013 server.

Symptoms:

-no messages in message queue
-if sending mail  to this domain, the message seems sent at Sender.
-if sending mail from this domain, the messages are in the mailboxes' DRAFT folder

Here are some SMTP logs:

2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,

 2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,

 2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,

2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,

2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,

2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical non matching options : Xrdst, . Failing over."

2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,

Software Enviroment:

-Windows Server 2012 Server Standard
-Exchange Server 2013
-fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.

Regards.

molni




↧

microsoft exchange mailbox transport submission service terminates unexpectedly

August 31, 2016, 9:11 am
$
0
0
Every few days Microsoft exchange mailbox transport submission service terminates unexpectedly. Do you know what could be the problem?
↧
↧

EventID HAREDIRECTFAIL

February 25, 2013, 1:20 am
$
0
0

Hi All,

I have been tracking a message within Exchange 2013 and I have noticed that the above EventID appears to be coming up for every message sent. I have tried a Google search but there are only 5 results, none of which really answer my question. I have seen the following thread here which shows that it is a failure to redirect (pretty obvious really) but I don't understand where this redirect error is coming from as mail is obviously being delivered to recipients.

Does anyone know where there is more info on this EventID, what redirect specifically it refers to, or any other information?

Thanks in advance for any help.

MP

Mike Parker MCTS http://www.tlptech.co.uk

↧

stuck messages

September 1, 2016, 3:29 am
$
0
0

Hello,

In our company we have Exchange server 2013. One of our partner says that when they try to send us messages they get stuck in their smtp server.
Can we check on our side if were any attempt of SMTP connection from them ?

could you suggest me any tools to work with this issue..

Thanks in advance,

↧
Search

Changing a DL to a Shared Mailbox

September 1, 2016, 9:12 am
$
0
0

We have an Exchange 2013 / Hybrid O365 deployment, with most of our mailboxes now on Exchange Online.

For a long time, our company has been using Distribution Lists that people outside the organization email to. This has led to a lot of emails being generated internally, to the mailboxes of the users on the DL.

We want to convert the DLs to Shared Mailboxes to reduce the amount of internal email generated.

Obviously we will need to create a mailbox and give the users permissions to it.

What is the best practice steps for converting a DL to a shared mailbox with minimal downtime?

↧

Users unable to send email to office365 users

September 1, 2016, 9:09 pm
$
0
0

Hi Team,

We are have Exchange 2013 with Cumulative update 14 in our environment. We have migrated few user to office365 by setting up Hybrid Environment. Now on-premises users are able to receive email from cloud user. But, on-premises users are unable to send mails to cloud users. we have added target address for that cloud user, still not receiving email.

Thanks in advance.

↧
↧

Exchange Server 2016 - All Incoming Emails to Junk

September 2, 2016, 3:09 am
$
0
0

I have recently installed Exchange Server 2016 and all incoming emails started going to Junk folder after installing Kaspersky Security 9.0 for Microsoft Exchange Servers

Any hint whether this can be controlled from Exchange settings or Kaspersky? 

↧

Database move 2010 to 2013

September 2, 2016, 5:44 am
$
0
0

Hey Guys;

There is a exchange 2010 and 2013 server on my environment  under the same domain.

i lost exchange 2010 server also no recovery option but i have a DB from 2010.

Can i mount it on 2013 server ? how ? thank you.

↧

Disable Read Receipts but allow Out of Office replies

September 2, 2016, 9:29 am
$
0
0

I have a single 2013 Exchange server setup.  I had a request to prevent internal users from being prompted to send read receipts on emails that originated from outside our organization.  After researching, I created a rule in Exchange that strips 'Disposition-Notification-To' from the message header if the email is received from outside the organization.  

I tested and confirmed with this rule in place, internal users are not prompted to send a read receive to an email they received from outside our organization.

However, what I just learned is this rule also prevents the outbound deliver of Out of Office replies.  So, if an internal user sets Out of Office in Outlook and receives an email from outside the organization, the sender never receives the Out of Office reply.  I can disable the Exchange rule and now Out of Office emails work correct.

I compared the message header line by line with the rule enabled and with the rule disabled and there is not a single instance of 'Disposition-Notification-To' on emails that do not request a read receipt, so why is the Exchange rule blocking outbound Out of Office reply messages?

Any help would be greatly appreciated.

Thanks,

↧
Viewing all 4249 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>