Hello All,

I have been installing and configuring Anti-Spam agents on my Exchange Servers. When testing with a GTUBE test mail, I see the mail is passed through and delivered to the end-user mailbox. The AgentLog shows:

2013-09-10T06:53:56.911Z,08D078FD1630A0BE,10.x.y.z:25,78.47.119.33:57650,78.47.119.33,emailsecuritycheck.net.3.dmPd6!rpDgG9NsTHLlzAIw==,securitycheck@emailsecuritycheck.net,securitycheck@emailsecuritycheck.net;,<testuser>@<domain>.com,1,Content Filter Agent,OnEndOfData,AcceptMessage,,SCL,2,,2407cb00-38da-4875-925d-08d07c09a7ad,,Undefined

So the message is scanned and marked as SCL 2! Why doesn't Exchange catagorize it as SCL 9?

Regards,

Stephan

You know you're an engineer when you have no life and can prove it mathematically

We've configure 2 different AD sites and both the site are configured with Ex2010 SP1 server with different MailboxDB. We are facing problem while trying to send/receive internal email between two sites also cant receive email from the external.

Site-1: CAS + HT + MB (Mailboxdb1)

Site-2: CAS + HT + MB (Mailboxdb2)

Site-1 : Can send and receive mail to the external as well as the Mailboxdb1 but cant send to the Mailboxdb2

Site-2 : Mailboxdb2 users cant send/receive mail to Mailboxdb1 users but can send mail to the external only.

ERROR: There is currently no route to the mailbox database.

Please advise

NA

Mikael

I have a 1000 mailboxes for retail employees, I want to make it to where these mailboxes can only send to a small selections of SMTP addresses (i.e. they will be able to emailstoresupport@contoso.com, but not each other).  I could do this by running a script to set 'Message Delivery Restrictions' on every mailbox but I would rather be able to do it via a policy or a group setting (i.e. members of this group can only send to these mailboxes). 

Hi

Gmail is rejecting mails because of ipv6 information in the mail header (exchange 2013). I have read some threads saying that I could do a reghack do disable ipv6. But I have also read that Exchange 2013 depends on IPv6 - so disabling IPv6 could cause other problems in mail routing. I have reverse PTR on ip4. I dont have the option to create SPF records.

So what can I do to prevent Exchange 2013 from adding IPV6 info to the mail header?

Regards

LS

Hi

When creating a custom receive connector for scan2email etc on exchange 2013, other connectors stops working after a couple of hours? I reboot and all connectors work again for a couple of hours and then stops working?

I have exchange 2013 cu2

Regards

LS

I have been reading about the differences between Standard and Enterprise User CALs for Exchange 2013 and I understand most of it.  However, I am having a hard time understanding what I can and cannot do regarding retention policies.  Below is my interpretation of the difference. Can someone correct, confirm, or provide a good reference for me so that I can properly understand & explain the real differences in retention policies to management.

1.       Retention policies can only be used on the default folders of a mailbox. Those include the Inbox (root of inbox only and not folders inside inbox), Deleted, Sent, & Drafts folders only. Any non-default created folder inside of a mailbox cannot be assigned to a retention policy.
2.       Because Exchange 2013 In Place Archive is only an option for Enterprise CALs we cannot use Auto-archiving in the retention policies. We can only set the retention policies to delete the messages that meet the defined age requirement within only a portion of a persons mailbox.

Running exchange 2013 cu2 and exchange 2010 sp3 in mixed mode. external dns pointing to 2013 server, and OWA is redirecting to users still on exchange 2010. Woking fine. But if a 2010 mailbox want to set Out of Office nothing happens. Seems like Owa to owa redirection is working but not to ecp.

Anyone knows what to do?

Regards

LS

Here is the setup. I have a web server on a DMZ that I am trying to send email from an app. I have the IP of the DMZ server in a receive connector set up to allow anonymous users to connect. When I try to test connectivity to the remote mail server using"telnet mail.domain.com 25" the session is blank. When I test from my workstation I connect and can see commands when I type ehlo. I have a couple of other receive connectors for various situations and I have tested on them but I am unsuccessful.

Ideas?

Server 2008 R2/Exchange 2010 sp2

- Gymmbo

Hi,

I am using 2  HUB/CAS transport servers with internal CA installed. I want to implement TLS certificate on Edge server for External emails.

My question is I am buying TLS  certificate from third party vendor. He ask me to give FQDN of my certificates. Can I give him my HUB and Edge server FQDN ?

For e.g    cas1.xyz.com (for Hub Transport)

              cas2.xyz.com

              MAIL.XYZ.COM (FOR Edge)

Hi team,

We are facing problem while connecting Ex-2010 SP1 MB (Site-3) user's OWA using Ex-2010 SP1 CAS server (Site-1 & Site-2) and getting error "Outlook Web App isn't available. If the problem continues, please contact your helpdesk."

Our Design:

Site-1: CAS/HT/MB           (IP: 172.16.128.0 MASK: 255.255.255.0 GW:172.16.128.1)

Site-2: CAS/HT/MB           (IP: 172.16.128.0 MASK: 255.255.255.0 GW:172.16.128.1)

CASARRAY and DAG is configured in between Site-1 & Site-2 and we can access the HA environment.

Site-3: MB                        (IP: 172.26.2.0 MASK: 255.255.224.0 GW:172.26.1.1)

Our Goal: We trying to access Site-3 MB OWA using CASARRAY.

Please assist.

Thanks;

NA

I have installed the Connection Filtering agent:

Install-TransportAgent -Name "Connection Filtering Agent" -TransportService FrontEnd -TransportAgentFactory"Microsoft.Exchange.Transport.Agent.ConnectionFiltering.ConnectionFilteringAgentFactory" -AssemblyPath "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.Transport.Agent.Hygiene.dll"

Add-IPBlockListProvider -Name zen.spamhaus.org -LookupDomain zen.spamhaus.org -AnyMatch $true -Enabled $true

Enable-TransportAgent -TransportService FrontEnd -Identity "Connection Filtering Agent"

Restart-Service MSExchangeFrontEndTransport

After this, it doesn't work. Email from ip addresses marked as blacklisted (as can be seen by test-ipblocklistprovider) aren't blocked. Besides, no logging is created in “C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\AgentLog”

Specified cast is not valid. 

You know you're an engineer when you have no life and can prove it mathematically

Hello All,

Though I installed the anti-spam filters on the Exchange 2013 Mail servers, and made sure to aneble them, I see that most SPAM is just arriving at the users mailboxes. The logging of the spam filters is showing that the messages are qualified as non-spam (SCL 0) by the Content Filter. But the Sender ID filter should have blocked these mails already, because the IP address which is sent from is on several blacklists. I have setup the IPblocklistproviders as follows:

[PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts>Get-IPBlockListProvider
Name                                           LookupDomain                                  Priority----                                          ------------                                   --------
SpamHaus                                       zen.spamhaus.org                              6SpamCop                                        bl.SpamCop.net                                7
surriel                                        psbl.surriel.com                              8
sorbs                                          dnsbl.sorbs.net                               9
ix.dnsbl.manitu.net                            ix.dnsbl.manitu.net                           10
combined.njabl.org                             combined.njabl.org                            11
cbl.abuseat.org                                cbl.abuseat.org                               12
spam.rbl.msrbl.net                             spam.rbl.msrbl.net                            13
bl.spamcannibal.org                            bl.spamcannibal.org                           14

Can you please help troubleshooting what is going wrong?

Regards,

Stephan van der Plas

You know you're an engineer when you have no life and can prove it mathematically

I have updated the internal certificate on my edge server (exchange 2007ccr) based on the steps below:

From your edge server:

 In Exchange Powershell perform the following commands:

     New-exchangecertificate

     Remove-edgesubscription

     New-edgesubscription –FileName “c:\whatever.xml”

 Copy the xml file just created to your Hub Transport server.

From your Hub Transport server:

Open Exchange Management Console and go to ”Organization Configuration > Hub Transport > Edge Subscription”

     Remove the current edge subscription

     Click New Edge Subscription (right hand task menu)

     Import the xml file you copied.

From your edge server:

     Restart Microsoft Exchange ADAM service

From your hub transport server:

Open the exchange powershell and perform the following commands:

      start-edgesynchronization

Now I am not getting incoming email, can someone help?

We have scripts we use to send emails to our exchange server, when we have it automate the messages, it randomly drops them, right now we are using ping  and sleep (depending on scripting language) to add some delay to prevent this from happening. 

Using Exchange 2010 and a Sonicwall, pretty sure its not the Sonicwall but the Exchange prevent it from excepting the messages, they are tiny messages, just a line or two of text.

Any idea how to turn this off, or add exceptions? Or what feature is stopping the messages?

Hi All,

I have exchange 2010 with edge server 2010.   Everything is working fine except.   We delete users after the get let go.  Every once inawhile the user gets rehired.  We rebuild the user just like always, but for some reason they cannot receive all the email.  They show up in our company junk folder.

Any Ideas were I can start looking.  

Thanks

Hi guys,
I'm hoping someone can help me pinpoint this ongoing problem we are having with our outbound mail sitting on our server and giving "Delivery is delayed to these recipients or groups" errors.


Some will eventually get through and are filtered straight to the recipients spam folder others never get there.
Messages sent from the same address without attachments seem to get through more reliably, however sometimes still get stuck in the recipients Spam folder.


I believe it is something to do with our domain name configuration but I don't know where to look next.
Our setup is as follows: On our internal LAN we have one domain joined Exchange Server configured as CAS, Hub, Mailbox. All our mailboxes are hosted on this server, and all Client Workstations and User accounts are in this same domain. We only use one domain in AD.


This exchange server is configured to receive mail from two Authoritative Domains which are our external domain names santaclara.com.gt and bellavista.com.gt. Some users mailboxes are configured to use santaclara.com.gt SMTP email addresses and others are configured to use bellavista.com.gt SMT addresses. Both our external domains are hosted by JustHost, and have MX records pointing to mail.santaclara.com.gt and mail.bellavista.com.gt respectively.


The santaclara.com.gt domain has an A-record pointing mail.santaclara.com.gt to the static IP address of our Cisco router. It also has SPF records as follows:
Host RecordTXT ValueTTL
@v=spf1 a mx mx:mail.santaclara.com.gt ip4:190.149.222.173 a:bellavista.com.gt include:mail.santaclara.com.gt mx:bellavsita.com.gt -all14400
www-bellavista-com-gtv=spf1 a mx mx:mail.santaclara.com.gt ip4:190.149.222.173 a:bellavista.com.gt include:mail.santaclara.com.gt mx:bellavsita.com.gt -all14400
The bellavista.com.gt domain has an A-record pointing mail.bellavista.com.gt to the static IP address of the same Cisco router. It also has an SPF record as follows:
Host RecordTXT ValueTTL
@v=spf1 a mx ptr:santaclara.com.gt ip4:190.149.222.173 a:santaclara.com.gt include:mail.santaclara.com.gt mx:santaclara.com.gt -all14400

The Cisco box has a firewall rule to route all mail traffic to the TMG 2010 server it is directly connected to in the perimeter network. This TMG 2010 box is also connected to the internal network and is configured as an Exchange Edge Server. 
We have two send connectors configured on the Hub Server, both are EdgeSync subscriptions to the TMG box: The first is inbound to domain; the second is domain to internet. Both are configured with the FQDN set to "mail.santaclara.com.gt" There is one receive connector configured, the default connector, and this has its FQDN configured as "srv-mail1.hq.santaclara.com.gt" which is the true FQDN of the exchange server and can’t be changed to match the send connectors.
I have checked our domains are not blacklisted, and performed outbound SMTP tests for both using the Microsoft Remote Connectivity Analyzer and everything seems to check out OK:

santaclara.com.gt test results
Performing Outbound SMTP Test
The outbound SMTP test was successful.
Test Steps
Attempting reverse DNS lookup for IP address 190.149.222.173.
The Microsoft Connectivity Analyzer successfully resolved IP address 190.149.222.173 via reverse DNS lookup.
Additional Details
The Microsoft Connectivity Analyzer resolved IP address 190.149.222.173 to host mail.santaclara.com.gt.


Performing Real-Time Black Hole List (RBL) Test
Your IP address wasn't found on any of the block lists selected.
Test Steps
Checking Block List "SpamHaus Block List (SBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamHaus Exploits Block List (XBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamHaus Policy Block List (PBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamCop Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "NJABL.ORG Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SORBS Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "MSRBL Combined Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "UCEPROTECT Level 1 Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "AHBL Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.




Performing Sender ID validation.
Sender ID validation was performed successfully.
Test Steps
Attempting to find the SPF record using a DNS TEXT record query.
The SPF record was found.
Additional Details
SPF record found: "v=spf1 a mx mx:mail.santaclara.com.gt ip4:190.149.222.173 a:bellavista.com.gt include:mail.santaclara.com.gt mx:bellavsita.com.gt -all"


Parsing the SPF record and evaluating mechanisms and modifiers.
The SPF record was parsed and evaluated successfully.
Test Steps
Evaluating A Record lookup mechanism: "+a"
Additional Details
The DNS A Record lookup for IP address 190.149.222.173 found no match for domain 'santaclara.com.gt'.


Evaluating MX mechanism: "+mx"
The MX mechanism indicated a positive status.
Additional Details
The Microsoft Connectivity Analyzer matched MX lookup for santaclara.com.gt to IP address 190.149.222.173.





bellavista.com.gt test results
Performing Outbound SMTP Test
The outbound SMTP test was successful.
Test Steps
Attempting reverse DNS lookup for IP address 190.149.222.173.
The Microsoft Connectivity Analyzer successfully resolved IP address 190.149.222.173 via reverse DNS lookup.
Additional Details
The Microsoft Connectivity Analyzer resolved IP address 190.149.222.173 to host mail.santaclara.com.gt.


Performing Real-Time Black Hole List (RBL) Test
Your IP address wasn't found on any of the block lists selected.
Test Steps
Checking Block List "SpamHaus Block List (SBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamHaus Exploits Block List (XBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamHaus Policy Block List (PBL)"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SpamCop Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "NJABL.ORG Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "SORBS Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "MSRBL Combined Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "UCEPROTECT Level 1 Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.


Checking Block List "AHBL Block List"
The address isn't on the block list.
Additional Details
IP address 190.149.222.173 wasn't found on RBL.




Performing Sender ID validation.
Sender ID validation was performed successfully.
Test Steps
Attempting to find the SPF record using a DNS TEXT record query.
The SPF record was found.
Additional Details
SPF record found: "v=spf1 a mx ptr:santaclara.com.gt ip4:190.149.222.173 a:santaclara.com.gt include:mail.santaclara.com.gt mx:santaclara.com.gt -all"


Parsing the SPF record and evaluating mechanisms and modifiers.
The SPF record was parsed and evaluated successfully.
Test Steps
Evaluating A Record lookup mechanism: "+a"
Additional Details
The DNS A Record lookup for IP address 190.149.222.173 found no match for domain 'bellavista.com.gt'.


Evaluating MX mechanism: "+mx"
The MX mechanism indicated a positive status.
Additional Details
The Microsoft Connectivity Analyzer matched MX lookup for bellavista.com.gt to IP address 190.149.222.173.


Any light, pointers links that anyone can throw my way I will be very grateful for!! 


TIA, Jon

We use a proxy for our mail at mail.ourcompany.com  to connect to our exchange servers at outlook.034d.mgd.msft.net

We use HTTP to connect, connect using SSL only and NTLM authentication

If I am connected to outlook it works, connect to vpn it works, but if I close Outlook and reopen while on VPN it says disconnected?

What is it trying to do at first connect that it fails?

David Sheetz MCP