Can I create a Transport rule with condition of "If recipient address (support@contoso.com) is bcc, then silently discard" ?

October 22, 2014, 2:44 pm

≫ Next: Exchange 2013 - How to determine if malware filter is enabled?

I need to create a rule that will take any email that was sent to recipient support@contoso.com as a Blind Carbon Copy recipient, and silently discard it. We should never receive mail from the outside from senders that bcc our support email address. It is always spam and can easily be filtered, but from what I read, Exchange 2013 doesn't come with the ability to use bcc recipient to create a condition with. I read there may be some 3rd party solutions, but I can't find any. Please suggest the best solution to this trivial non-feature of Exchange 2013 that should come included out of the box.

Thanks,

Keith

↧

Exchange 2013 - How to determine if malware filter is enabled?

October 22, 2014, 7:54 am

≫ Next: What are the correct Send Connectors settings in Exchange 2013

≪ Previous: Can I create a Transport rule with condition of "If recipient address (support@contoso.com) is bcc, then silently discard" ?

We are using Exchange 2013. We want to implement a third-part Anti-spam filter and read that it is best to make sure that the built-in malware filter is not enabled - how do we check whether it is or not?

↧

What are the correct Send Connectors settings in Exchange 2013

October 22, 2014, 8:47 pm

≫ Next: Issue with send on behalf of

≪ Previous: Exchange 2013 - How to determine if malware filter is enabled?

I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles. I am trying to set the send connectors settings, because I've not been able to send nor receive external email via owa. Since I'm separating the exchange roles, my mailbox servers only use internal IP settings and cannot resolve external DNS. I'm thinking I need to tick, proxy through CAS for it to work? any suggestions?

↧

Issue with send on behalf of

October 23, 2014, 7:17 am

≫ Next: Unable to Send Mail

≪ Previous: What are the correct Send Connectors settings in Exchange 2013

New poster here so I'm not sure that I'm posting in the correct forum...

I have an issue I've been wrestling with but I've not had any success trying to resolve it. I have one user who is trying to forward a contact to someone. When he right clicks and selects "Forward Contact as Outlook Contact" he gets a bounce back message immediately saying "He doesn't have permission to send on behalf of this user". The kicker here is the person that it says he doesn't have permission to send on behalf of is WHOEVER is in the to field when he sends it. This is true for any email address I've tried. If you forward as a buisness card instead of outlook contact, it works fine. I have exposed the from field and he is listed as the from address. This is Outlook 2010 on Exchange 2010.

I'm scratching my head here. He has no access to send on behalf of anyone. I've even went as far as to re profile his Outlook with a new profile and allowed it to re download.

Any ideas on where to start with this?

EDIT: Same as the issue described here: http://community.spiceworks.com/topic/211697-can-t-forward-contacts-in-outlook-2010-in-an-exchange-2010-environment

It was unresolved in this post.

↧

Unable to Send Mail

October 23, 2014, 10:51 pm

≫ Next: Duplicate MessageIDs with Exchange 2010

≪ Previous: Issue with send on behalf of

After working fine for years, no one in my Exchange Organization can send e-mail. When they send a new message, it does not appear in the Sent mail and never makes it to a server queue (as far as I can tell). When I look at the delivery report for one of these messages, I get "Delivery report information for this message isn't available." This is true whether using Active Sync, OWA, or standard Outlook. Inbound SMTP works fine. I use separate Mailbox and Edge servers; CAS and Hub services are combined. Can you think of anything I can do to troubleshoot?

↧

Duplicate MessageIDs with Exchange 2010

October 9, 2014, 2:03 am

≫ Next: Getting Messge Undeliverable errors on email account that is active

≪ Previous: Unable to Send Mail

Hi,

A customer was complaining that some mails were not received by them. So I’ve been back and forth with them a couple of times and every time I show them our logs that their server accepts the message and we get an id from them so the message is delivered properly.
Now they dug a little bit deeper and noticed that it seems our Exchange server is handing out duplicate message IDs and the email is flagged as duplicate by their mail system and therefore removed and thus never received by them.
Outlook clients do not have any special plugins installed and are running on our Citrix environment which has Symantec Endpoint Protection as the virusscanner.
Using the Tracking Log Explorer I can see, when entering the MessageID of the message that is giving issues, that there are 3 messages with the same ID. All those emails are sent within 1 hour intervals but I do not think duplicate detection applies here since it is only for incoming emails.
The message subjects + content is completely different for each of the emails.
Our Exchange 2010 version is: 14.02.0247.005

Does anyone know how we can fix this issue?

Thanks

↧

Getting Messge Undeliverable errors on email account that is active

October 24, 2014, 1:56 am

≫ Next: Missing Check Box Deliver Message to Both Forwarding in Exchange 2013

≪ Previous: Duplicate MessageIDs with Exchange 2010

Hi All,

We are experiencing the same problem below but I don't know how to solve it in Exchange 2013.

We have an employee that is restarting his position with our company. His account was removed when he left years ago but had a contact with the email address first.last@company.us . I deleted that contact and set him up a new AD and email account. I have his account setup as the first.last@company.us, but I keep getting

"The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk."

I checked and the email address is listed in email addresses. One of the Alias email addresses work fine, but the one that is on his cards (the one above) does not. Any ideas?

↧

Missing Check Box Deliver Message to Both Forwarding in Exchange 2013

November 12, 2013, 3:55 pm

≫ Next: E-mails are not going out. all emails stuck in queue exchange 2013

≪ Previous: Getting Messge Undeliverable errors on email account that is active

We recently finished installing Exchange 2013 and it has been working fine. However, we noticed that we cannot keep messages to both forwarding address and mailbox. We do not have the check box option in Delivery Options.

How do we fix or enable that the check box for Deliver message to both forwarding address and mailbox?

↧

E-mails are not going out. all emails stuck in queue exchange 2013

July 6, 2014, 5:40 am

≫ Next: DNS SPF Bounce Back Issue

≪ Previous: Missing Check Box Deliver Message to Both Forwarding in Exchange 2013

I have installed new Exchange server for my company.. but e-mails are not going out from my domain.. I am getting below error.

MX, RDS, Exchange connectivity analyzer all going good. but e-mail are not going out.

getting below error. if some body can help...

gmail.com DnsConnectorDelivery Retry 2 "Saturday, July 05, 2014 1:31:10 PM" "[{LRT=7/4/2014 12:09:04 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" 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 173.194.75.26:25};{FQDN=gmail.com};{IP=173.194.75.26}]"

hotmail.com DnsConnectorDelivery Retry 2 "Saturday, July 05, 2014 1:30:53 PM" "[{LRT=7/5/2014 1:09:40 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" 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 65.54.188.72:25};{FQDN=hotmail.com};{IP=65.54.188.72}]"

↧

DNS SPF Bounce Back Issue

October 24, 2014, 9:51 am

≫ Next: Secheduling/delaying delivery of messages of the type newsletter / informaiton mail

≪ Previous: E-mails are not going out. all emails stuck in queue exchange 2013

Hello,

I am trying to send an email from IP: 64.32.183.2 to email: megan.faillace@corepoweryoga.com and get this bounce back email.

Do any of you know what I need to create on the TXT record for the DNS? I've created an SPF record but still get an error message.

See the testconnectivity results below. Any help would be appreciated!

Performing Outbound SMTP Test
The outbound SMTP test failed.

Additional Details

Elapsed Time: 24104 ms.

Test Steps

Attempting reverse DNS lookup for IP address 64.32.183.2.
The Microsoft Connectivity Analyzer successfully resolved IP address 64.32.183.2 via reverse DNS lookup.

Additional Details

The Microsoft Connectivity Analyzer resolved IP address 64.32.183.2 to host smtp.wemanageproperties.com.
Elapsed Time: 86 ms.
Performing Real-Time Black Hole List (RBL) Test
Your IP address wasn't found on any of the block lists selected.

Additional Details

Elapsed Time: 23609 ms.

Test Steps

Checking Block List "SpamHaus Block List (SBL)"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 901 ms.
Checking Block List "SpamHaus Exploits Block List (XBL)"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 872 ms.
Checking Block List "SpamHaus Policy Block List (PBL)"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 1045 ms.
Checking Block List "SpamCop Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 91 ms.
Checking Block List "NJABL.ORG Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 8349 ms.
Checking Block List "SORBS Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 3773 ms.
Checking Block List "MSRBL Combined Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 241 ms.
Checking Block List "UCEPROTECT Level 1 Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 71 ms.
Checking Block List "AHBL Block List"
The address isn't on the block list.

Additional Details

IP address 64.32.183.2 wasn't found on RBL.
Elapsed Time: 8262 ms.
Performing Sender ID validation.
Sender ID validation failed.

Additional Details

Elapsed Time: 407 ms.

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 mxv=spf1 a mx a:corepoweryoga.com mx:exchange.corepoweryoga.com ip4:173.239.121.125 a mx ~all"
Elapsed Time: 87 ms.
Parsing the SPF record and evaluating mechanisms and modifiers.
SPF record evaluation resulted in a Sender ID failure.

Additional Details

Elapsed Time: 320 ms.

Test Steps

Evaluating A Record lookup mechanism: "+a"

Additional Details

The DNS A Record lookup for IP address 64.32.183.2 found no match for domain 'corepoweryoga.com'.
Elapsed Time: 2 ms.
Evaluating A Record lookup mechanism: "+a"

Additional Details

The DNS A Record lookup for IP address 64.32.183.2 found no match for domain 'corepoweryoga.com'.
Elapsed Time: 0 ms.
Evaluating MX mechanism: "+mx"

Additional Details

No MX records for domain corepoweryoga.com matched the specified IP address.
Elapsed Time: 123 ms.
Evaluating A Record lookup mechanism: "+a:corepoweryoga.com"

Additional Details

The DNS A Record lookup for IP address 64.32.183.2 found no match for domain 'corepoweryoga.com'.
Elapsed Time: 0 ms.
Evaluating MX mechanism: "+mx:exchange.corepoweryoga.com"

Additional Details

No MX records exist for exchange.corepoweryoga.com.
Elapsed Time: 84 ms.
Evaluating IP address mechanism: "+ip4:173.239.121.125"

Additional Details

IP address 64.32.183.2 didn't match entry 173.239.121.125.
Elapsed Time: 0 ms.
Evaluating A Record lookup mechanism: "+a"

Additional Details

The DNS A Record lookup for IP address 64.32.183.2 found no match for domain 'corepoweryoga.com'.
Elapsed Time: 0 ms.
Evaluating MX mechanism: "+mx"

Additional Details

No MX records for domain corepoweryoga.com matched the specified IP address.
Elapsed Time: 108 ms.
Evaluating All mechanism: "~all"
All mechanisms indicated a negative status.

Additional Details

Status: SoftFail
Elapsed Time: 0 ms.

↧

Secheduling/delaying delivery of messages of the type newsletter / informaiton mail

October 24, 2014, 6:27 am

≫ Next: Send a notification based on sender's domain

≪ Previous: DNS SPF Bounce Back Issue

Hi Everyone,

I would like to set a rule (on the transport servie maybe) to schedule the dilivery of messages sent to a big number of recipients.

I have checked around on TN regarding Throttling Policy and Transport Rules and I find a little difficult to pinpoint the right parameter to get the correct effect.

Here what I intend to do:

Max allowed reciepients per message, I think I found the setting (I belive it is "Set-TransportConfig -MaxRecipientEnvelopeLimit")
Max number of messages sent per minute (for the whole Exchange organisation) (I think it isSet-TransportService -MaxConnectionRatePerMinute)
Messages that exceeds the "MaxRecipientEnvelopeLimit" are scheduled to be delivered between 2-4 am and sent in bulks for examole if a message sent to 5000 recipients, it sent only to 500 at a time. (I am aware that one could achieve this by using Outlook rules but it's not an option. This has to be achieved by the Exchange organisation)

And this is of course in Exchange 2013 env. I would very much appreciate any help!

Take care!

↧

Send a notification based on sender's domain

October 21, 2014, 3:30 am

≫ Next: Change Microsoft Exchange Approval Assistant - Reply to

≪ Previous: Secheduling/delaying delivery of messages of the type newsletter / informaiton mail

Hey guys,

Is there a way for me to send an automatic notification to external senders, based on their domain? For example user@domainA.com sends me an email and I want him to receive an email, that he should use another server to send mail with. I know you can do similar things with transport rules, but can my goal be achieved with them?

Thanks

↧

Change Microsoft Exchange Approval Assistant - Reply to

October 26, 2014, 10:28 am

≫ Next: Exchange 2010 External Message SLA

≪ Previous: Send a notification based on sender's domain

Hi there

I created moderated group with single Moderator

I want a configuration when message is rejected the user know who to ask if the message is rejected

If a user try to use [reply] he gets reply to Microsoft Exchange Approval Assistant - which send failure notice

↧

Exchange 2010 External Message SLA

October 27, 2014, 8:42 am

≫ Next: A parameter was specified that isn't valid on an Edge Transport server.

≪ Previous: Change Microsoft Exchange Approval Assistant - Reply to

Hi Team,

I have a question. I have 4 mailbox and 2 CASHT exchange 2010 in HQ site. all Mailbox active at HQ

I have +- 5000 Mailbox and have 150 send/receive message per mailbox average. I also configured alerting tools that count outgoing mail from internal to external roundtrip

my alerting tools send alert with details internal to external message more than 2 sec consume time.

when I check in tracking log. its true, the message need 2 sec to deliver message to external smtp gateway

so my question is. is this appropriate condition, the message send more than 2 sec?

is this condition still meet exchange SLA? if yes I will adjust my alerting tools to extend more second

im sure there are no performance issue in my HT server. I already trace

please help :)

thanks

↧

A parameter was specified that isn't valid on an Edge Transport server.

October 27, 2014, 12:53 am

≫ Next: Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

≪ Previous: Exchange 2010 External Message SLA

Hi, please help, I'm trying to create a rule to Exchange Edge server to filter certain types of attachments and get the error (New-TransportRule : A parameter was specified that isn't valid on an Edge Transport server). I want to create a rule blocking JS and VBS attachments archived zip and rar.

New-TransportRule "Block js" -AttachmentExtensionMatchesWords js -RejectMessageEnhancedStatusCode 5.7.1 -RejectMessageReasonText "Block extension js" -enabled $true

↧

Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

October 28, 2014, 12:07 am

≫ Next: Restricting users to send email to internal users only

≪ Previous: A parameter was specified that isn't valid on an Edge Transport server.

Hi everybody,

I'm having some issues with an Exchange 2013 server.

When some users try to logon to the OWA page it keeps loading the page and ends with a time-out.
This only applies to 6 or 7 users, other users can login and open the page.

I tried to replace the signed certificate to solve this problem, and did a online analyzer check, most tests come out good.

I can't seem to find the source of this problem.

There are also multiple users that are having trouble to receive e-mail through the wifi on phones and tablets at home but when they switch to 3g it works fine.

You might need more information, just ask.. i don't know where to search anymore.

I tried inheritance on the AD, disabled SSL in the IIS, restarted the server, replaced the signed cert. etc.

Update:

I set the selfsigned cert in the IIS default web page,, to check if it responds to the certificate and it does, so the issue doesn't come from the certificate.

This issue probably came up after CU1, and i've read something about healthboxes..

I'm going to install CU6 and hope for good result.

Kind regards,

Tim

↧

Restricting users to send email to internal users only

October 27, 2014, 9:51 am

≫ Next: fake "next hop domain" and fake "from address" on queue viewer

≪ Previous: Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

I am working with SharePoint 2013 office 365. Are we able to set up some rule in Exchange for certain users that if we give them a email account they can only send messages to internal users?

↧

fake "next hop domain" and fake "from address" on queue viewer

October 28, 2014, 2:13 am

≫ Next: how to send automated emails from exchange server using PS

≪ Previous: Restricting users to send email to internal users only

Hey guys,

I have installed and configured exchange edge 2010 for send and receive internet mail. Recently when open queue viewer I seeHundreds of fake Next Hop Domain and fake From address that doesn't exist in directory(xyz@mydomain.com that xyz doesn't exist). How I can fix this problem?

Thanks.

↧

how to send automated emails from exchange server using PS

October 29, 2014, 5:53 am

≫ Next: CAS -> Edge Transport Failure

≪ Previous: fake "next hop domain" and fake "from address" on queue viewer

Hi, we are making automated scripts to send a text file with some mail addresesses to another company to inject those mails address into her exchange server.

The PS script what we use are this:

<#
script de automatización de envío de correo
Desarrollado en el Dpto de Operaciones Soluciones IT (c) 2014
Version 1.00
#>

Clear-Host

Write-Host "Script de envío de archivo de contactos" -ForeGroundColor Magenta
Write-Host "Creado por Alpha Systems S.R.L. (c) 2014" -ForeGroundColor Magenta
Write-Host " "
Write-Host " "<#
Solicitamos los datos para el envío de los correos
#>

Write-Host -NoNewLine "Ingrese el fqdn del dominio de correo: " -ForeGroundColor Yellow;$Suffix=Read-Host
Write-Host -NoNewLine "Ingrese el nombre de nuestro servidor Exchange: "-ForeGroundColor Yellow; $Server=Read-Host
Write-Host -NoNewLine "Ingrese la dirección de correo destino: "-ForeGroundColor Yellow;$Receipt_Mail_Address=Read-Host
Write-Host -NoNewLine "Ingrese la dirección de correo remitente: "-ForeGroundColor Yellow;$Sender_Mail_Address=Read-Host
Write-Host " "
Write-Host " "<#
Armamos el correo electrónico y lo enviamos
#>

$filename=“c:\Sync\Contacts-"+$Suffix+".txt”

$msg=new-object Net.Mail.MailMessage
$att=new-object Net.Mail.Attachment($filename)
$smtp=new-object Net.Mail.SmtpClient($Server)

$msg.From=$Sender_Mail_Address
$msg.To.Add($Receipt_Mail_Address)
$msg.Subject = “Correo automatizado – Contacts-"+$Suffix+".TXT”
$msg.Body=“Envío automatizado del archivo Contacts-"+$Suffix+".TXT”
$msg.Attachments.Add($filename)

$smtp.Send($msg)
Write-Host "Enviando Correo automatizado, por favor espere ... " -ForeGroundColor Green
Write-Host " "
Write-Host " "
Write-Host "Correo enviado" -ForeGroundColor Green

In the script we are asking for the name of the server, the sender and destination mail address.

In exchange Server 2010 this PS script works fine, but in Exchange 2013 SP1 does not work, we receive the following error message

Exception calling "Send" with "1" argument(s): "Mailbox unavailable. The server response was: 5.7.1 Unable to relay"
At C:\sync\RobotSendAutoMail.ps1:44 char:1+ $smtp.Send($msg)+ ~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException+ FullyQualifiedErrorId : SmtpFailedRecipientException

We need what this script works again in Exchange 2013

Raulito

↧

CAS -> Edge Transport Failure

October 29, 2014, 8:05 am

≫ Next: problem with exchange 2007 SP3 and mac mail app loading mails

≪ Previous: how to send automated emails from exchange server using PS

All,

So I'm trying to send mail from inside -> Internet, and my messages are getting stuck in the queue saying "451 5.7.3 Cannot achieve Exchange Server Authentication."

This is a brand new Exchange setup, brand new receive connector created by default.

All of my edgesync stuff works fine. I can start-edgesync, works great. No errors. No failures.

I thought it may have been the TLS certificate (I initially had the original self-signed cert).

The only thing I'm wondering is if it's failing because I applied my single unified cert to this server (the same cert I'm using for OWA/Autodiscover/etc). I put the 'smtp.contoso.com' in the SAN field.

I can SEND mail from the outside just fine. It shows up in my internal mailbox. So Edge -> CAS/Hub is working great.

Pretty standard setup.

2x Dual Role CAS/MBX boxes in a DAG

1x Edge Transport in DMZ

No firewall between CAS/MBX servers

Firewall between CAS/Edge

Ports open between CAS/Edge:

2525 (bidirectional)

25 ( bidirectional)

50389 (CAS -> Edge)

50636 ( CAS -> Edge)

↧