Mahmoud Hanefy MCITP: Windows Server 2003,2008 Enterprise Administrator | MCSE/MCSA
Remote Server returned '554 5.4.4
Redirect Rule - Delivery has failed to these recipients or groups
First of all my apology if this is wrong Forum. Please guide me to correct forum.
Scenario is that we need to send emails to AD Group using C# code or script.
First we tried C# code and it don't work, as per our finds, log in / password is required. Also, it was taking to much time because of protocol and we need to send 10 to 15 emails at same time.
We tried script and this time we created a mail box say, temp. We send emails to temp and added rules on bases of subjects of emails.
Now, issue is if we setup forward rule, temp is able to forward email to AD group. If we setup redirect rule, email is not send to AD Group and temp received failure delivery.
Your message can't be delivered because delivery to this address is restricted.
For more information about this issue see DSN code 5.7.1 in Exchange Online.
We even made temp owner of AD group.
Any help?
http://farhanfaiz.wordpress.com
Add Digital Signature to outgoing messages for all exchange users
Is it possible to add digital signature to outgoing messages for all exchange users? Currently we have add digital signature individually using Outlook.
Actual delivered Message size varies between two different exchange forests.
Hi All ,
In my current environment we have one exchange forest with exchange 2013 and another exchange forest with exchange 2010.
Lets say a mailbox user from exchange 2013 forest is sending an mail along with attachment of (1.7 MB) to one of the mailbox user in same exchange 2013 forest and also to one of the mailbox user in exchange 2010 forest .
So on such case the size of the delivered message to the both the mailbox users in the different forest varies.We have found that with the help of message tracking logs in both the forest.
I mean the mailbox user in the same forest (i.e exchange 2013) receives an message with a size around 1.7 MB and the mailbox user in the other exchange forest (i.e exchange 2010) receives an message with the a size around 2.25 MB .
Questions :
We would like to know that how the size of the delivered message varies between the mailbox users in the different exchange forest ?
Is this is the default mail delivery behavior in exchange between two exchange forest ?
Note : On my end i thought that the message from the exchange 2013 forest to exchange 2010 forest was processed two times by the categorizer (one time in exchange 2013 and one time in exchange 2010) because of that size is varied .But i am not sure on my end
.
All of your suggestions are much appreciated .
Thanks & Regards S.Nithyanandham
Exchange 2013 Malware Filter and ScanningProcess.exe
Hi all...
We have an Exchange 2013 environment with an external Mail Security Appliance (FortiMail), because of this our Malware Filter was disabled, but the process ScanningProcess.exe (Microsoft Filtering Server Scanning Process) are still running and sometimes hangs the CPU for several minutes scanning attachments.
Is there a method to disable the process and avoid the CPU high use?
(all servers have Exchange 2013 CU7)
Unable to send messages to specific hosts
Hello I'm opening a new thread for this as Ive got stuck again.
I have some users that try to send mails to about 5 domains that wont succeed. 99% of al mail is going out like it should but to these domains all messages get stuck in the queue. The NDR they get is :
Remote server at domain.com (x.x.x.x) returned '400 4.4.7 Message delayed'
Remote server at domain.com (x.x.x.x) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060."
Attempted failover to alternet host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. the last endpoint attempted was x.x.x.x:25
Most posts regarding this error suggest a DNS issues and it does look like this. but when I do an NS lookup on the server the correct MX records are being returned. I have also tried with the use External DNS option but no luck. other things Ive tried is to use a Send connector with TLS, use different ports but they wont go out. I've contacted the admin of the receiving domain and they say they have not blacklisted our IP's. So I'm really stuck here any input would be very welcome. FYI: I've check the blacklists and we're not on them, I have reverse DNS setup and SPF records and with the mxtoolbox all checks out fine.
how to block external email on exchange server 2013
Abp
Routing oubound email to various SAP instances.
Hi Experts ,
This may sound naïve ,however I am looking for your advise on the below queries.
We have scenario where we want certain emails to be routed to their respective SAP instances/boxes/client from exchange server .
For example ,
xyz @ crm . com to sap 1 system port 25000
abc @ crm .com to sap 2 system port 25001
We have multiple production systems and want emails to be routed as per the mail boxes they are catering to . Is this achievable ?
Also is there a limitation to number of SMTP send connectors that can be created ? My current understanding is every routing to respective sap instance will take one send connector ?
What is the roadmap for SMTP , as we have been informed that way forward is EWS ?
Thanks in advance.
X-Auto-Response-Suppress DR, OOF, AutoReply?
Helo Guys,
How can I get / change this settings (X-Auto-Response-Suppress DR, OOF, AutoReply)?
I see this from email header of an email sent to a DL. This setting looks suppressed OOO / auto reply message.
BR,
Uddan
Mail Exchange Server
Hi tech,
I have a problem, everytime my clients uses his ip 41.79.10.106 he gets the error message
The mail system
<>: host [65.55.37.88] said: 550 SC-001
(COL004-MC2F14) Unfortunately, messages from 41.79.10.106 weren't sent.
Please contact your Internet service provider since part of their network
is on our block list. You can also refer your provider to
. (in reply to MAIL
FROM command)
Kindly help me delist this from your network.
Mike
Technical Engineer.
Inbound authentication failed with error UnexpectedExchangeAuthBlob
New Exchange 2013 on Windows Server 2008 R2, in coexistence with Exchange 2007 on Windows Server 2003.
Except for one test mailbox, all mailboxes are still on Exchange 2007.
Virtual directories are redirected to Exchange 2013, with legacy dns name directed to Exchange 2007, and OWA/ActiveSync are working fine.
Mail flow from the internet is still directed to Exchange 2007 and is fine.
But mail flow is not working on Exchange 2013. Using OWA with the test mailbox, emails are stuck in the drafts folder. Emails from a mailbox on Exchange 2007 are received by the frontend transport service, but fails on the transport service with this error
(192.168.1.76 is the address of Exchange 2013 server, and HV-SRV-EXCH-02 is its name):
MSExchangeTransport - 1035 - SmtpReceive
Inbound authentication failed with error UnexpectedExchangeAuthBlob for Receive connector Default HV-SRV-EXCH-02. The authentication mechanism is ExchangeAuth. The source IP address of the client who tried to authenticate to Microsoft Exchange is [192.168.1.76].
Certificate is signed by an enterprise CA, and contains public domain names, with the NetBIOS and fqdn names :
CN=owa.example.com, OU=xxx.......",Certificate subject
"CN=vsg-HV-SRV-CA-02-CA, DC=vsg, DC=qc, DC=ca",Certificate issuer name
owa.example.com;hv-srv-exch-02.vsg.qc.ca;AutoDiscover.vsg.qc.ca;AutoDiscover.example.net;AutoDiscover.example.com;HV-SRV-EXCH-02,Certificate alternate names
Clocks are in sync (both Exchange servers, and domain controllers)
SPNs seem ok :
setspn -L hv-srv-exch-02 | find /I "smtp"
SmtpSvc/HV-SRV-EXCH-02.vsg.qc.ca
SmtpSvc/HV-SRV-EXCH-02
SMTP/HV-SRV-EXCH-02.vsg.qc.ca
SMTP/HV-SRV-EXCH-02
DNS servers are set manually in ECP, and on the TransportService and FrontEndTransportService. I also added the IP and hostnames (NetBIOS and fqdn) of both Exchange servers in the hosts file
I used Kerberos debug log to check for errors, and all I got is this, which seems fine :
A Kerberos Error Message was received:
on logon session VSG.QC.CA\hv-srv-exch-02$
Error Code: 0x19 KDC_ERR_PREAUTH_REQUIRED
Example logs for the same session, sending an email from a mailbox in Exchange 2007, to the test mailbox in Exchange 2013
From the FrontEnd receive log (hv-srv-exch-01 is the Exchange 2007 server) :
2015-05-06T12:25:40.535Z,HV-SRV-EXCH-02\Default Frontend HV-SRV-EXCH-02,08D2555C60FC73C7,46,192.168.1.76:25,192.168.1.23:15456,<,X-EXPS EXCHANGEAUTH,
2015-05-06T12:25:40.535Z,HV-SRV-EXCH-02\Default Frontend HV-SRV-EXCH-02,08D2555C60FC73C7,47,192.168.1.76:25,192.168.1.23:15456,*,SMTPSubmit SMTPSubmitForMLS SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender
BypassAntiSpam BypassMessageSizeLimit SMTPSendEXCH50 SMTPAcceptEXCH50 AcceptRoutingHeaders AcceptForestHeaders AcceptOrganizationHeaders SendRoutingHeaders SendForestHeaders SendOrganizationHeaders SendAs SMTPSendXShadow SMTPAcceptXShadow SMTPAcceptXProxyFrom
SMTPAcceptXSessionParams SMTPAcceptXMessageContextADRecipientCache SMTPAcceptXMessageContextExtendedProperties SMTPAcceptXMessageContextFastIndex SMTPAcceptXAttr SMTPAcceptXSysProbe,Set Session Permissions
2015-05-06T12:25:40.535Z,HV-SRV-EXCH-02\Default Frontend HV-SRV-EXCH-02,08D2555C60FC73C7,48,192.168.1.76:25,192.168.1.23:15456,*,VSTGEORGES\HV-SRV-EXCH-01$,authenticated
2015-05-06T12:25:40.535Z,HV-SRV-EXCH-02\Default Frontend HV-SRV-EXCH-02,08D2555C60FC73C7,49,192.168.1.76:25,192.168.1.23:15456,>,235 <authentication response>,
From the FrontEnd Send log :
2015-05-06T12:25:45.558Z,Inbound Proxy Internal Send Connector,08D2555C60FC73C8,51,192.168.1.76:42824,192.168.1.76:2525,>,X-EXPS EXCHANGEAUTH SHA256 ,
2015-05-06T12:25:45.558Z,Inbound Proxy Internal Send Connector,08D2555C60FC73C8,52,192.168.1.76:42824,192.168.1.76:2525,>,<Binary Data>,
2015-05-06T12:25:50.566Z,Inbound Proxy Internal Send Connector,08D2555C60FC73C8,53,192.168.1.76:42824,192.168.1.76:2525,<,454 4.7.0 Temporary authentication failure,
2015-05-06T12:25:50.566Z,Inbound Proxy Internal Send Connector,08D2555C60FC73C8,54,192.168.1.76:42824,192.168.1.76:2525,>,QUIT,
And from the Hub Receive log :
2015-05-06T12:25:45.558Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,51,192.168.1.76:2525,192.168.1.76:42824,<,X-EXPS EXCHANGEAUTH,
2015-05-06T12:25:45.558Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,52,192.168.1.76:2525,192.168.1.76:42824,*,,Inbound ExchangeAuth negotiation failed because of UnexpectedExchangeAuthBlob
2015-05-06T12:25:45.558Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,53,192.168.1.76:2525,192.168.1.76:42824,*,,User Name: NULL
2015-05-06T12:25:45.558Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,54,192.168.1.76:2525,192.168.1.76:42824,*,Tarpit for '0.00:00:05' due to '454 4.7.0 Temporary authentication failure',
2015-05-06T12:25:50.566Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,55,192.168.1.76:2525,192.168.1.76:42824,>,454 4.7.0 Temporary authentication failure,
2015-05-06T12:25:50.566Z,HV-SRV-EXCH-02\Default HV-SRV-EXCH-02,08D2555EA1F7C246,56,192.168.1.76:2525,192.168.1.76:42824,-,,Local
FrontendProxyEnabled Proxy all outbound SMTP traffic through CAS
Hello all
I am running Exchange 2013 CU8. I have two AD sites, and two DAG's. 5 mailbox servers in each DAG, and 4 CAS servers in each AD site. Environment looks similar below. The picture shows 4 CAS, however i have 8. What i want to know is it best practice to route smtp email through the CAS servers ? what is the advantage to using FrontendProxyEnabled ?
Bulls on Parade
Exchange 2013 - Unable to send email, Internally & Externally
Hi,
I have new testing lab to play around with which is starting to drive me insane. I have exchange 2013 and outlook 2013. I can receive emails from external domains but I am unable to send emails internally or externally!
Now I would know what to look at if I couldn't send externally, But not being able to send internally has completed confused me!
anyone got any tips where to start troubleshooting for not being able to send internal mail? Once internal mail works I should then be able to get external mail working as well....
Thanks
Suppress Exchange 2013 moderation notifications
Hello All,
I have an Exchange 2013 environment where I have just enabled message moderation. So far so good. However, I would like to suppress all notifications to the moderated recipients and the sender of messages to this recipient. I have created a transport rule that deletes all emails containing "Your message was rejected by a moderator for these recipients" which is what the system sends when a message is rejected by the moderator. However if the moderator doesn't approve or reject a notitication, another message is sent to the sender (and maybe the moderated receipent). I have found a good bit of MS reference material for the message (If the approver either deletes or ignores the approval message, an expiration message is sent to the sender. This happens after two days in Exchange Online, and after five days in Exchange Server 2013....# 3 in how the approval process workshttps://technet.microsoft.com/en-us/library/dd297936.aspx) I need to know exactly what the message says so I can create the transport rule to delete it and not bounce a message back to the sender.
I basically have 2 questions:
1. Is it possible to configure Exchange so it doesn't generate these notifications to begin with?
2. What are the contents of the various notifications sent by the system when moderating messages? I have one listed above but don't know what else gets sent. I need to create a transport rule to delete/redirect the message so that it's not sent to the sender, moderated recipient, etc.
I have only a few days to figure this out. Please help.
JPC0706
Disable unauthorized SMTP Relay within Domain
Hi All,
We have Exchange 2013 SP1 infrastructure on top of Windows Server 2012 R2. We have a DAG and CAS NLB clusters.
Anyone can relay Emails from my SMTP to all users within my domain without authentication.However no one can send emails outside my domain (external Emails without authentication).
All these emails are sent through Default Front end Receive Connector, and we cannot Disable Anonymous Users from connector security settings as by doing this we will not receive emails from External World. Please refer the attached snapshot.
Need your suggestion to implement SMTP security to restrict Unauthorized SMTP Relay.
Thanks
VN
The message is pending in the queue 'SERVER\Unreachable'. The last error was 'A matching connector cannot be found to route the external recipient'.
Hello all,
I am doing a lab at home... and i installed and partially configured Exchange 2013.
Now i have second problem when sending a e-mail:
"The message is pending in the queue 'SERVER\Unreachable'. The last error was 'A matching connector cannot be found to route the external recipient'."
I send message to my self ( localy on server... So basicly i send from email@domain.com to email@domain.com .
And it said that error in message trace...
Why does exchange trying to send External e-mail since i sent it internally? Is there any connections with networking or DNS / DHCP?
Thanks in advance for answers!
EmailAddressPolicy %1g%s@contoso.com not working ("Failed to generate proxy address. Additional information: General Error.")
For some strange reason we cannot use the EmailAddressPolicyTemplate %1g%s@contoso.com (jsmith@contoso.com) for a particular emaildomein on our Exchange 2013 server. If we create the address policy and apply it, it gives us the error:
"Failed to generate proxy address. Additional information: General Error."
The strange thing is, that any other domain works correctly with %1g%s@. Any other format for domain contoso.com works like it should.
Our environment has a forest trust with AD domain Contoso.com for a upcoming crossforest migration.
I already recreated the accepted domain (internal-relay) and the send connector for this domain.
Because of this error, the cross forest mailbox moverequests fail at finalizing, that they cannot update the mailbox in the target environment.
If we set the EmailAddressPolicyEnabled to $false, the moverequest completes, but the mailbox is not updated to the correct mail address. I tried to find extra logging for what is happening but can't find any options.
Last lines of the moverequest report:
5/7/2015 10:42:53 AM [DSMxxxx] Target mail user 'Testuser12' was loaded
from domain controller 'DSMxxxx.Constoso.com.
5/7/2015 10:42:53 AM [DSMxxxx] Fatal error
UpdateMovedMailboxPermanentException has occurred.
Why is only policy %1g%s@contoso.com not working?
%2g%s@contoso.com works
%1g%s@MSFTraders.com works
Help would be appreciated.
All inbound mail stuck in Submission Queue with a delivery type of Unknown and error A Local Loop was Detected
My email organization consists of two email servers: Exchange 2013, Oracle Messaging. The servers are in two different geographic locations.
The Oracle messaging is the primary email server (orc1.MyDomain.com)
The Exchange server (loc2-ex.MyDom2.local)
A routing rule on the Oracle messaging server forwards MyDom2 user email (changes the email address from @MyDomain.com to @loc2.MyDomain.com) to the remote Exchange server.
On the Exchange server, the domain MyDomain.com is set for internal relay. MyDom2.local and loc2.MyDomain.com are set at Authoritative.
Users on the Exchange server can send Internet bound email that is delivery as expected to outside domains. Email between exchange users and inbound internet email gets delivered to the Exchange server but is not posted to the user's email. Instead it remains in "Submission queue" (delivery type "undefined", status "ready") Each message's last error is "A local loop was detected" (SCL "-1", Queue ID "Loc2-EX\Submission", Message Source Name "SMTP: Client ProxyLoc2-EX")
How do I get Exchange to deliver emails?
Here are the settings for Accepted Domains, and the Send and Receive Connectors:
*************************************************************************************************************************
************* Accepted Domains
*************************************************************************************************************************
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDom2.local
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : True
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyDom2.local
DistinguishedName : CN=MyDom2.local,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyDom2.local
Guid : 1ae7e6e6-1747-4d7b-bfb1-d3998a34bc6f
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/10/2015 5:16:06 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/10/2015 9:16:06 PM
OrganizationId :
Id : MyDom2.local
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDomain.com
CatchAllRecipientID :
DomainType : InternalRelay
MatchSubDomains : False
AddressBookEnabled : False
Default : True
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay domain
DistinguishedName : CN=MyOrganization relay domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay domain
Guid : 35e58252-49fd-4048-abf6-4213f4eb0fa4
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/26/2015 3:29:13 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/26/2015 7:29:13 PM
OrganizationId :
Id : MyOrganization relay domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : loc2.MyDomain.com
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : False
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay sub-domain
DistinguishedName : CN=MyOrganization relay sub-domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay sub-domain
Guid : 867dc53e-574f-4324-916e-9853718568fc
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:19 PM
WhenCreated : 3/30/2015 11:10:38 AM
WhenChangedUTC : 5/6/2015 5:24:19 PM
WhenCreatedUTC : 3/30/2015 3:10:38 PM
OrganizationId :
Id : MyOrganization relay sub-domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
New Exchange 2013 Cluster messages getting bounced
We have an issue with a new Exchange 2013 cluster consisting of 2 CAS and 2 MBX servers running on Windows 2012 R2. The messages sent from this cluster are being bounced by more than 1 enterprise sized organizations using Edge servers without probable cause.. The only error it is giving back is: Remote Server returned '550 5.7.1 Message rejected due to content restrictions'
What was checked/changed sofar:
- Updated Exchange to CU8
- Blacklists
- Reverse DNS addresses
- Sending mail through a 3rd party smarthost
- Enabled header firewall to clean routing info from header
- Told the send connector use HELO instead of EHLO
- Told the send connector to ignore STARTTLS
- Changed RemoteDomain Characterset and NonMimeCharacterSet from ISO-8859-1 to UTF-8
- Changed RemoteDomain LineWrapSize to 78
- Changed RemoteDomain ContentType from MimeHtmlText to MimeText
Now, the following part may be important..
What we now found out is when we forwarded the NDR message to another 3rd party mail server, then forward the NDR from there to the original recipient it will also bounce? Even when we copy a small bit from that NDR or original message into a new email on the working environment the message will get bounced..
I'm getting desperate, please help!! Thanks in advance!
-Emile