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

Can no longer send a signed email message

$
0
0

My certificate was working fine to sign emails yesterday. I don't encrypt, just sign.

Now I am unable to sign.  My certificate reports as valid.  (Outlook 2013 - Windows 8.1 Enterprise)

Found a number of entries for mismatched email addresses and for encrypted emails.  None of those suggestions apply as my email address is contained within my certificate despite the statement in the error message that a certificate matching my email address could not be found. 

Full error text:

Invalid Certificate

Microsoft Outlook cannot sign or encrypt this message because there are no certificates which can be used to send from the e-mail address 'xxxxxx @ yyyyy.zzz. Either get a new digital ID to use with this account, or use the Accounts button to send the message from an account that you have certificates for.



Create Secure channel between o365 & Exchange 2013 on prem

$
0
0

Hey guys , 

 i have a doubt on how to create an secure connection between o365 and on-premises exchange 2013 server, i.e mails within my domain xyz.com (on cloud) to xyz.com (on prem) should be sent from o365 directly to my on prem exchange without opening port 25 on firewall.

pls help guys. I am new to o365 ,


Lui-A

Email IDs are placed under 'example@domain.com' for couple of users?

$
0
0

Hi,

We use exchange 2013 CU5 hybrid of O365

We observed for couple of users like - when they receive email ID from external IDs it will place the email under 'example@doamin.com' format rather than usual way ofUserName/Domain/Department display name format

Eg:

Usually if any email from external IDs to internal user the email once received, will show as display name format -UserName/Domain/Department

But today couple of users complained saying their external email user complained , they see as -'username@domain.com'

what could be the reason


Manju Gowda

Prevent users from changing the from in Exchange 2013

$
0
0

I am trying to prevent Exchange from sending emails from addresses that do not exist in the organization. For example sales@somedomain.com is a valid email address setup in Exchange and should send emails. However aslkjs38@somedomain.com is not an email address assigned to any users however the Exchange server will still send the emails as long as someone logs into the server with a valid user account and password.  They have made it apparently impossible to find the actual user account that is sending the emails so I would like to prevent Exchange from sending emails that aren't associated with a user account and also matching the users account that logged in.  Also if anyone knows how to find the users security account that is actually sending an email in the queue that would be helpful as well.

Exchange Server Mail Flow

$
0
0

Hi Friends,

I need your help on Exchange server 2013. I want to receive mails from multiples mail id's from domain user, 

If I'm sending mail through acb@abc.com, abc2@abc.com, abc3@abc.com, abc4@abc.com.... I can receive only on info@abc.com

Please let me know the configuration on exchange server 2013.  

Thanks.

  

Exchange 2013, Recipient Validation. CAS/MBX ROle.

$
0
0

Hey Team,

I realize that enabling recipient validation on a mailbox server / CAS server (multirole) causes any invalid recipient to block the whole message and pretty much make recipient validation useless for exchange 2013 unless an edge server is used.

Here is my question:

We are using mcafee saas but for a few different reasons we are not able to get LDAP/S working correctly (original plan) so we are not able to use Mcafees recipient validation, the idea then was to use Exchange's recipient validation but of course there is the known issue of it not working correctly.

Can I just have Mcafee SaaS send all email traffic to port 2525 and bypass the "CAS Server's port 25" completely?

This link here: Is where I got the bright idea from: https://helpdesk.spamtitan.com/support/solutions/articles/4000003763-dynamic-recipient-verification-using-exchange-2013

Thanks,

Robert


Robert


I coudn't received mail from outside domain such as Yahoo, Gmail ,etc

$
0
0

Dears, 

I couldn't received mail from outside domain such as Yahoo, Gmail ,etc

the followingout put of Recive connector :



Unable to email a Distribution List from an External email address

$
0
0

Howdy,

We have two Distribution Lists that we need tobe able to send to from external email addresses.  I went into the ECP and edited the Delivery Management setting and changed it fromOnly senders inside my organization to Senders inside and outside of my organization but I still can't send to the DL.

Is there another setting somewhere that might be preventing these emails from coming through?

Thanks!

UPDATE: Just got a rejection bounce with the error below.  It says to change the setting that I already changed so not sure what else to check.

~~~~~~~~~~~~~~~~~~~~~

Delivery has failed to these recipients or groups:

Your message couldn't be delivered because the group you're sending to needs to know who you are before it will accept your message.

To fix this problem, ask the email admin for the group to configure the group to accept messages from you.

For Email Administrators
This error occurs when the group is configured to reject email from senders outside of the group's organization. To fix the issue, the recipient's email admin must either add the sender's address to the group's list of allowed senders or they must select the group's delivery management option that allows senders both inside and outside of their organization to send email to it.


Not able to send out internet emails. Not able to receive emails yet!

$
0
0

Hello all

Little background.  my company is currently using 2 companies to host our emails.  bluehost has our domain and x7hosting has our emails.  It is a simple pop email service.  We want to change over to exchange so we purchased a server that will act as a file server and a exchange server.  About 1 month ago I set up exchange server and was able to sent out emails with no issues but was not able to receive emails due to x7hosting still holding on to our domain. flash forward to today we want to redirect our domain to our in house server with exchange.  OUT of the blue i am no longer able to send out emails. we have not yet redirected our domain to our server but we would like to do so ASAP.  currently our emails are staying in our drafts.

i have gone through multiple forums but cannot find any luck

currently using this server with 2 NIC cards one is for a file server

Migration from 2010 to 2013 exchange - which server is a receiver connector

$
0
0
We started migration from our exchange 2010 server and now how in place also 3 new exchange 2013 servers in DAG. I am wondering how to check which Exchange server is now receiver connector for extarnal messages? Is it only exchange 2010 server?

Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

$
0
0

Dear All,

I have exchange server 2013 running with windows server 2012.

My email server have been send and receive email with internal and external as normal.

Today, i got the problem the email cannot send out to external and get the error below:

Please comment.

BR,

Khemarin


Khemarin333@hotmail.com

Use Office 365's EOC as Smart Host

$
0
0

Hi,

 This is my situation, i've an Exchange 2013 Server On-Premises, and i'd like to create a Send Connector that would use Office 365's EOC as SmartHost.
I've read about how to do this, but i keep getting an error from the EMC that says:


error

No se puede hacer coincidir el nombre de identificador rblSmartHostAuthMechanismNone con un nombre de enumerador válido. Especifique uno de los siguientes nombres de enumerador e inténtelo de nuevo: None, Verbose 
 
 
Which roughly translated would be something like...

 The identifier's name "rblSmartHostAuthMechanismNone" won't match any valid enumerator's name. Specify any of the following enumerator names and try again: None, Verbose.

(I've posted this message on the Office 365 forum and they told me to try here...)  -i tried to add a link, but the site wouldn't let me-

Just in case it is not clear, i did all the necessary steps on the Office 365 EAC, and it went smoothly. That error message occurs when i try to create (or modify) a Send Connector in my on-premises server.

Can you think of any suggestions for me?

Thanks!

Transport Rule Condition Block Secondary SMTP for External

$
0
0

Hi all,

Is there a way to limit users to use secondary SMTP addresses to mail external?

For example:

John Smith has manager@contoso.com as his primary SMTP and j.smith@contoso.com as secondary SMTP.

John may only mail external with his primary SMTP manager@contoso.com

I can only block users currently, cause if I add secondary SMTP tobe blocked, it will recognize the User like it does with the Check names button...

thanks in advance


Spam SenderIDConfig

$
0
0
Hi.

I set this:

Set-SenderIDConfig -SpoofedDomainAction StampStatus

What is this stamp in message? Can i change it?

I want redirect all of stamp message to one mailbox. How i can do it?

Thanks.

Sending warning to sender for external email address

$
0
0

Hi;

I am using Exchange 2013 Standard, is there anyway that I can do on Exchange to send a warning email back to sender if who try to send email out of the organization email domain?

Can I turn on something on Exchange Shell?


KW - CNE,MCSE,VCP5


Certificate errors despite valid wilcard cert installed

$
0
0

Hi all,

Exchange 2013_CU9 With multiple older/expired SMTP-enabled SAN certs installed, Newwildcard cert was installed and SMTP-enabled before the old ones expired. When the old ones expired, I started to get

"There is no valid SMTP Transport Layer Security (TLS) certificate for the FQDN of Mail1.domain com The existing certificate for that FQDN has expired. The continued use of that FQDN will cause mail flow problems. A new certificate that contains the FQDN of MAIL1.domain.com should be installed on this server as soon as possible. You can create a new certificate by using the New-ExchangeCertificate task."

Why? Should I remove all the old ones With "Date invalid" to get rid of this? And how can I do this without something breaking here?

Thanks.


Accepted Domains best practice

$
0
0

Hi,

So I have a single Exchange 2013 server. We recently migrated from Exchange 2007 (and that server has been decommissioned). We use Solarwinds Orion for network monitoring. It has an alerting function. I added the IP address of the Solarwinds sever to our internal relay Receive Connector so Exchange will accept messages from the Solarwinds server. I can send alerts to any internal email address successfully (for instance I set the recipient to my own email address and it worked). However, we want to be able to have alerts go to our pager. So I put in the recipient address ofxxxxxxxxxx@usamobility.net. This function works perfectly fine for other systems that we have alerting set up on (for instance we use APC Struxtureware for alerting our pager on power outages). I am also able to send an email to the pager from my Outlook. However, the Solarwinds server logs this error:

The server rejected one or more recipient addresses. The server response was: 550 5.7.1 Unable to relay

The only way I'm able to get it to go through successfully is if I go to Mail Flow > Accepted Domains and add usamobility.net as aninternal relay. I'm sure that nobody is going to hack into our network and start spamming us with emails to usamobility.net but is this a bad practice? What type of security threats am I open to? Am I doing this wrong is there another way around this problem?

Thanks in advance!


Configuring receive connectors (externally secured options)

$
0
0

We have two domains with AD two-way trust and Exchange GAL synchronization done via Forefront identity Manager 2010. We have a problem with meeting room reservation, user from domain A is trying to book meeting room from domain B (there is a contact object in domain A for this meeting room from domain B). The problem is that such room is not sending response confirmation email to user and meeting room is visible as tentative. I alreadyset "externally secured" option on receive connectors in domain B:

exchange 2010 server - receive connector role:HubTransport, scoping exchange server in domainA IP port 25, security: tls and externally secured

3x exchange 2013 servers - receive connector role:FrontendTransport, scoping exchange server in domainA IP port 25, security: tls and externally secured

I am not sure whether this is enough configuration for receive connectors, what about receive connector  for hubtransportrole on 2013 exchange servers? Should I also configure them, what ports?

Domain A: one exchange 2013 server

Domain B: one exchange 2010 server (meeting rooms hosted in db on this server) and 3 exchange 2013 servers in DAG, prepared to migrate mailbox db from 2010 server

mail.protection.outlook.com Delisting

$
0
0

We moved to another location and got a new ip from ISP and our exchange server is not able to send emails to some recipients getting .mail.protection.outlook.com error.

user@domain.com
BN1AFFO11FD036.mail.protection.outlook.com #550 5.7.1 Service unavailable; Client host [72.76.xxx.xx] blocked using Blocklist 1; To request removal from this list please forward this message todelist@messaging.microsoft.com ##

This is the error I am getting and I did email to delist@messaging.microsoft.com and I am wondering when will my IP get unblocked as this is causing a lot of communication issues. I checked my ip for blacklist but its not in any database. Hope I'll be able to find some solution soon on this.


 

Exchange 2013 Out Of Office not working internally or externally

$
0
0

Hi

We are having an issue with OOO. I have checked Remote-Domains and the settings are enabled, we are using a smart host and I have queried if that can handle the OOO mails, but that should not stop internal OOO, I have used Get-MailBoxAutoConfiguration and OOO is enabled on the account. Accounting to the delivery report in exchange the mail is generated and sent. I have also checked autodiscover on outlook and the url is correct, no errors. Any this else I can check?

Viewing all 2249 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>