Hi, it does not appear possible to add an X-Envelope-To: header to messages to show the original envelope recipient at the point it arrives at the exchange server. i.e. it is not possible, in the mail flow rules, to obtain the envelope recipient.
Any ideas appreciated.
Hello,
I have a costumer that receives an email from a service that comes with no body or subject, only comes with an attachment,... this makes Exchange 2013 block the email and we never receive it, but i can see in the service webpage that the mails were sent.
How do i override this filter or rule that blocks this specific email address on exchange server 2013, because i need to receive this emails,... they bring orders in the attachment.
Thank you !
Dear all,
in my organisation we have 2 cas, 2 mbx servers.
2 cas servers are in nlb cluster, and use one unique ip adress.
Internal and public DNS and ASA firewall is setup to target/nat mail.ogranisation.com to nlb cluster unique ip adress.
And when I send mails to live or gmail service, mails goes to spam. In header of mail I saw that mails doesnt go trough mail.ogranisation.com fixed public ip adrees, mail goes trough public ip adrees for internet browsing.
I am managing an Exchange Server 2013 with out any 3rd party spam- and malware software and I am receiving alot of spam, between 20 and 30 emails very day.
I have configured antispam and antimalware on my Exchanger server by following guides like
http://www.msexchange.org/articles-tutorials/exchange-server-2013/security-message-hygiene/anti-spam-and-anti-malware-protection-exchange-2013-part1.html
and
https://technet.microsoft.com/en-us/library/bb201691(v=exchg.160).aspx
Most messages have the same subject text and some are different. Most messages come from different email addresses.
Most of the messages also have a .zip, .doc or .jpg file attached. I have configured malware agent to reject such files, to scan inside the files but they still end up in the mailboxes.
Any cloes to stop the spam and malware?
Hello community,
our Exchange2013-server can not handle opportunistic TLS and I really don’t know why…everything I’ve found so far seems to be fine.
Please help…thank you very much!
Exchange Version: 15.0 Build 1210.3
Our Firewall is configured as the Mailgateway.
Get-SendConnector * | Ft Identity,IgnoreSTARTTLS
gives one SendConnector back listed with FALSE.
Get-ExchangeCertificate | ft subject,services
Gives back two certificates for SMTP. One internal and our public wildcard-certificate – is it a problem that two certificates are enabled for SMTP?
The TLSCertificateName attribute was empty on Sendconnectors. I’ve changed this to the thumbprint of our public certificate - but
no change.
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpSend:
... 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,10,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-STARTTLS, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,11,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-X-ANONYMOUSTLS, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,12,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-AUTH NTLM, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,13,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-X-EXPS GSSAPI NTLM, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,14,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-8BITMIME, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,15,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-BINARYMIME, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,16,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-CHUNKING, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,17,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-XEXCH50, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,18,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-XRDST, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,19,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250 XSHADOWREQUEST, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,20,*InternalExchIP*:26966,*InternalExchIP*:2525,>,X-ANONYMOUSTLS, 2016-12-21T00:00:08.487Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,21,*InternalExchIP*:26966,*InternalExchIP*:2525,<,220 2.0.0 SMTP server ready, 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,22,*InternalExchIP*:26966,*InternalExchIP*:2525,*,,Remote certificate 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,23,*InternalExchIP*:26966,*InternalExchIP*:2525,*,"CN=*.company.xx, O=company AG, OU=IT, L=nirvana, S=neverland, C=xx",Certificate subject 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,24,*InternalExchIP*:26966,*InternalExchIP*:2525,*,"CN=XXX CA - SHA256 - G2, O=CertAuth nv-sa, C=BE",Certificate issuer name 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,25,*InternalExchIP*:26966,*InternalExchIP*:2525,*,179765A42F6A43A80097A459,Certificate serial number 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,26,*InternalExchIP*:26966,*InternalExchIP*:2525,*,2DBA3C3C149C146A6DXXXXXXXX92187A0954,Certificate thumbprint 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,27,*InternalExchIP*:26966,*InternalExchIP*:2525,*,*.company.xx;autodiscover.company.xx;mail.company.xx;owa.company.xx;company.xx,Certificate alternate names 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,28,*InternalExchIP*:26966,*InternalExchIP*:2525,*,,"TLS protocol SP_PROT_TLS1_2_CLIENT negotiation succeeded using bulk encryption algorithm CALG_AES_256 with strength 256 bits, MAC hash algorithm CALG_SHA_384 with strength 384 bits and key exchange algorithm CALG_ECDHE with strength 384 bits" 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,29,*InternalExchIP*:26966,*InternalExchIP*:2525,*,,Received certificate 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,30,*InternalExchIP*:26966,*InternalExchIP*:2525,*,2DBA3C3C149C146A6DXXXXXXXX92187A0954,Certificate thumbprint 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,31,*InternalExchIP*:26966,*InternalExchIP*:2525,>,EHLO *internalExchDNS*, 2016-12-21T00:00:08.518Z,Inbound Proxy Internal Send Connector,08D4143AB830A2B0,32,*InternalExchIP*:26966,*InternalExchIP*:2525,<,250-*internalExchDNS* Hello [*InternalExchIP*],....
The Output of "Get-AuthConfig | Format-List " gives me a "CurrentCertificateThumbprint" I can't identify,
so I guess it does not exist anymore.
I was not able to change it to the current internal certificate as it is said:
"has a private key that is not exporable". -not sure if this is a problem.
Maybe I did more I can't remember right now...but I think this is all mentionable so far.
Hi,
One of our customer asked for TLS encryption for email transmission.
I've followed the link : https://technet.microsoft.com/EN-US/library/jj657514(v=exchg.150).aspx
Unfortunately, it seems that email are sent without any TLS encryption. Or not using the newly setup Send Connector.
The email is well received by the customer.
Could you please help ?
Thank you and best regards,
Hello Technet Forms,
I have a requirement to block messages that are being sent to one or more domains on the same message. So as an example someone is trying to email mcdonalds.com but the message was accidently also addressed to a burgerking.com email. So DLP should block the message from sending. So far playing around with the DLP settings within Exchange 2013 it does not seem like this is possible at all. But I figured I would ask in case anyone else has tired this and gotten it to work.
Hi Everyone,
I have a Hyper-V Host, inside is one VM (Exchange2013) as planned we are planning to use DAG on our exchange.
So I created the VM, with 2 NIC port (MAPI - xx.xxx.xx.13 / Replication - xx.xxx.xx.11)
Outgoing email is not working on the CAS, so I set my send connector to use smart host, which is our antispam, that is connected to our IBM Notes smtp.. So we now have outgoing email using exchange.
But upon checking the header, Exchange Server to Anti-Spam to Lotus SMTP to Recipient.
How can I solve this? what data should I provide to have the answer on this problem.
Thanks,
Mikey
Hi all;
By default, I am using the default send connector to route all email from Exchange 2013 to all email recipients via internet. Due to business requirement, I have a site to site vpn link with a 3rd parties company for some kind of resources exchange. Let's say my 3rd parties business partner email domain is mail.3rdpartner.com, instead of sending the email over internet, I am thinking how possible to route the email to this email domain by a second Send Connector, in this case; all email for them is sent via the VPN link, not instead.
Subject to my information, my business partner is using Exchange 2010. My thinking is, I need the MX record of their exchange server and put it into my DNS server, this is the first step to do. And configure the Send Connector to look up this DNS entry if email is for this email domain.
Please let me know if this is correct if anyone know how to do or you have same experience before, and what other setup need consider in my plan?
thanks!
KW - CNE,MCSE,VCP5
User sent a calendar event to 5 recipients in the same Exchange organization. 1 of the recipients says he didn't receive the event. Message tracking log shows 4 of them with last event "DELIVER". But 1 one didn't receive the event has last event "PROCESS".
What is PROCESS means?
Hi All,
We are using Exchange 2013 servers as 2 mailbox server's and 2 CAS servers.
We are using F5 load balancing for exchange, My security team introduced new F5 for F5 failover purpose.
My security Team configured new F5 with existing active F5 settings.
We are testing F5 IP address using client host file for outlook and owa connectivity
My question is How to check F5 IP or client IP address in exchange to confirm New F5 functioning properly.
I have checked IIS logs under path C:\inetpub\logs\LogFiles\W3SVC1 but there is not showing New F5 or client IP address.
Please help out on this.
Thanks & Regards, Kumar N
I have installed Exchange 2013 in the Exchange 2010 environment and created some test users and didn't notice any issues.
After initial testing I have moved some of the production mailboxes from Exchange 2010 to Exchange 2013, intermittently i see that emails from Exchange 2010 users for Exchange 2013 users are stuck on Exchange 2010 HUB servers in a Unreachable Queue.
Initially it was showing DNS error , SMTP SEND error in the Last Error, but now it doesn't show anything and the emails sit in Unreachable Domain.
I checked different DNS options etc, it only works when I bounce the AD Topology Service on the HUB Server.
After bouncing the service if i check, then i can see the "Hub Version 15" queue showing and the emails are delivered to the Exchange 2013 mailboxes.
Not sure what is causing the problem as I checked both the Exchange 2010 and Exchange 2013 servers are in the same subnet and also they are in Same AD Site.
Can anyone helpme with this, i cannot proceed with the migration before I resolve this issue.
mdimthyas
Could you please help to understand the TLS Function is Send/Receive connector in exchange
and what would be the impact if enable in our organization exchange
Hello,
I have received "550 5.1.1 User unknown" error when I send mail from external mail (such as gmail) to my one of users. (user1@contoso.com)
This problem exists only in one user. Everything is okay with other users.
After uncheck "Block messages sent to recipients that do not exist in the directory" on Recipient Filtering on the "Edge Transport Server" my problem is solved.
My Question is:
if the user (user1@contoso.com) exists in my AD then why I received "550 5.1.1 User unknown" error?
Why I should uncheck "Block messages sent to recipients that do not exist in the directory"?
I don't want to uncheck that settings.
My Environment:
Two Mailbox Server (Exchange 2013 CU13);
One Edge Transport Server (Exchange Server 2010);
I have installed Anti-spam and anti-malware on Mailbox servers.
Thank you for your help...
Exchange 2013 quit receiving in the mailbox after new ssl certificate. The emails get to the server as they are logged but are never seen by the user both on the owa or outlook. All the test were performed using the microsoft analyzer and all is good.
The users can send but when someone sends emails to them it bounces with the following:
me@domain.com
Remote Server at db01 (10.100.195.14) returned '400 4.4.7 Message delayed'
12/29/2016 12:45:21 AM - Remote Server at db01 (10.100.195.14) returned '441 4.4.1 Error encountered while communicating with primary target IP address:"Failed to connect. Winsock error code: 10061, Win32 error code: 10061." 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.100.195.14:475'
Any help on this? I've been trying and cannot find any issue... for sure I'm missing something!
Help!
TechGUy,System Administrator.
Hi Team,
We have 2 child domains on which Exchange 2013 is installed. We have issued a single SSL certificate from our internal ADCA server in Parent domain.
This certificate is installed on the exchange server in child domains.
THE SAN name has all the url's required for autodiscover and OWA access.
When we try to open OWA url for both the child domains we are getting the certificate error as the CN name on the certificate is not the same as FQDN of any of the CAS servers.
Do we need to generate 2 certificates from ADCA with different CN name (Same as FQDN used to access CAS server from outside network) to resolve this error?
Thanks,
Mitesh Jain
The is a delay of one domain when sending email.
The other domain already inspect the smtp log, and said that the delay is from my side.
what should i check to determine the delay.
Hop | Delay | From | By | Time (MST) |
1 | * | MAK 10.160.1.113 | exch.pstechno.com.my 10.160.100.1 | 11/09/2016 16:51 |
2 | 5 hour | mail.my2.shm.com 17.x.x.140 | relmlie1.idc. | 11/09/2016 21:56 |
3 | 24 seconds | relmlie1.idc. 1x.23x.4.65 | relmlac1.idc. | 11/09/2016 21:57 |
4 | 0 seconds | relmlac1.idc. 127.0.0.1 | relmlac1.idc. | 11/09/2016 21:57 |
5 | 0 seconds | userid | relmlac1.idc. | 11/09/2016 21:57 |
6 | 0 seconds | relmlac1.idc. 1x.23x.69.21 | relmlir1.idc. | 11/09/2016 21:57 |
7 | * | relmlir1.idc. 1x.23x.68.151 | SMSSMTP 4.0.0.59 | 11/09/2016 21:54 |
8 | 2 seconds | 172.28.2.130 | NECSEM-EXCHANGE.necsem.com.my | 11/09/2016 21:54 |
on the exchange queue, it showed 451 4.4.0 Primary target IP address responded with: "421 4.4.2 Unable to connect.
knizam