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

Exchange Server 2010 mails bounce back from Exchange 365

April 9, 2019, 1:31 am
$
0
0

All exchange 365 server users bounce our mails back. We use Exchange Server 2010.

Other external mails are fine just 365 users.

Delivery has failed to these recipients or groups:

--- A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.



Diagnostic information for administrators:

Generating server: mail.oaib.org.tr

--- #< #5.0.0> #SMTP#

Original message headers:

Return-Path: <--->
Received: from oaibexch.oaib08.gov ([172.15.0.16]:10946 helo=mail.oaib.org.tr)
        by mail.oaib.org.tr with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256)
        (Exim 4.91)
        (envelope-from <--->)
        id 1hDlAv-0002eh-Pg; Tue, 09 Apr 2019 10:28:09 +0300
From: =?utf-8?B?QmHFn2FrIEhhdGljZSBHb2vDp2VvxJ9sdQ==?=
        <---->
To: Mustafa KARSU <--->, =?utf-8?B?QsO8bGVudCBLQVlBTEk=?=
        <---->
CC: Ebru Atamer <--->, Ceren Solmazoglu
        <--->, Ayfer Koca <--->
Subject: =?utf-8?B?UkU6IFRIQUlGRVggMjAxOSAtIE1pbGxpIEthdMSxbMSxbSBPcmcuIEhrLg==?=
Thread-Topic: =?utf-8?B?VEhBSUZFWCAyMDE5IC0gTWlsbGkgS2F0xLFsxLFtIE9yZy4gSGsu?=
Thread-Index: AdTU54Fkkw+Tq+cBRairWqaGh1j+rwJXrDRQAABc5goAKihgkAPtMV2Q
Date: Tue, 9 Apr 2019 07:24:20 +0000
Message-ID: <89BE31E2EDA6C8488104FB9824E3495101A7C232D5@oaibexch.oaib08.gov>
References: <89BE31E2EDA6C8488104FB9824E3495101A7BEB7F1@oaibexch.oaib08.gov>,<89BE31E2EDA6C8488104FB9824E3495101A7C03D87@oaibexch.oaib08.gov>
<90FE8AA5-644B-4258-9888-73CE343F4646@gaib.org.tr>
<DB6P189MB0517686497F08B4EBBA1511F8C410@DB6P189MB0517.EURP189.PROD.OUTLOOK.COM>
In-Reply-To: <DB6P189MB0517686497F08B4EBBA1511F8C410@DB6P189MB0517.EURP189.PROD.OUTLOOK.COM>
Accept-Language: tr-TR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.10.5]
x-esetresult: clean, is OK
x-esetid: 37303A29FEF7D66B6C7D64
Content-Type: text/plain
MIME-Version: 1.0
X-Sophos-OBS: success
X-CTCH-PVer: 0000001
X-CTCH-Spam: Unknown
X-CTCH-VOD: Unknown
X-CTCH-Flags: 0
X-CTCH-RefID: str=0001.0A0B0212.5CAC48FF.00AA,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0
X-CTCH-Score: 0.000
X-CTCH-ScoreCust: 0.000
X-CTCH-Rules:
X-Exim-DSN-Information: Due to administrative limits only headers are returned

↧
Search

Force queue emails in exchange

April 9, 2019, 4:33 am
$
0
0

Dears,

We have an application that sends a huge load of emails. 

The application relay through an exchange 2010. We want to use office 365 also to relay emails. Therefore we created a send connector and receive connector between exchange and office 365, but the thing is that the mailbox passed the Office 365 limit which is 30 emails per minute per mailbox.

Therefore we are searching for a solution to queue the emails in exchange and limit it to 30 emails.

So in each minute the exchange should send 29 emails and the other emails will be queued for delivery.

Please advise.

Best Regards,

↧
↧

Mail sent using the wrong send connector

April 9, 2019, 8:56 am
$
0
0
Hello, I have Exchange 2013 Organization with 2 sites. 2 servers in Site1 (CAS and MBX/HUB) and 2 servers in Site2, same roles.
I have Fortimail as Smart Hosts in each site. Both connectors has SMTP * with cost 10, but each one has the "Scoped send connector" checkbox checked, and only the corresponding server for that site. So, Site1 send connector has only MBX/HUB server on that site and Site2 the same. No DAG, separated servers with databases in each server,
The thing is that someone with a mailbox hosted in a database in server in Site2 send a mail, and the mail apparently goes through Site1 send connector. Got the mail and the header says that the sender is the fortimail from Site.
If I check delivery reports the mail appear as delayed and in the info says that the mail was sent to a remote site. I am scratching my head and thinking which log could I check to know the route is taking the mail to be sent using the wrong connector.
Something to say, the send connectors are using instead the direct fortimail records, a DNS zone with MX records inside. In site1 the mx record with cost 10 is the site1 fortimail and the mx record with cost 20 is the site2 fortimail. Same thing for DNS zone for site2, but fortimail for site2 has cost 10 and fortimail for site1 has cost 20. This is for failover, so if site2 lost connection with fortimail in site2, goest to site1 fortimail, but don´t know if this is happening because the fortimail is up and sending mails and only happens for this mailbox.
Is there a tracking log I can check?
↧

+91-(995) [88O2] 839 Husband Wife Dispute Problem Solution Baba ji Hong kong

April 9, 2019, 11:06 pm
$
0
0
FDFDSPNSNIGOSIROHOIHGIFHGIUFHGIFGF
↧

S/MIME and credential roaming

February 14, 2019, 3:19 am
$
0
0

Hello Exchange Admins,

we have an internal request, to provide S/MIME signing and encryption capabilities to end users (approx. 3,000). So we are evaluating implementations and talking about the best way.

Circumstances
- using internal certificates from Windows PKI (AD)
- consider lifecycle (name changes, renewals, Root CA expiries, device changes)
- S/MIME should be used in Outlook (auto deployment) and on iOS device (may be imported manually)
- secure end-to-end encryption, with low user interaction

There seems to be multiple ways out there, to accommodate these Circumstances.
1. Auto Enrollment of certificates using GPO (is able to deploy public key information to AD/GAL automatically and private key information to user with internal PKI) with Credential Roaming (is capable to address the multiple device handling). Credential Roaming seems to be suboptimal.
2. Developing a custom solution, which creates certificates on behalf of user, deploys public information to AD/GAL, private information to user (based on manydependencies). This seems to be tricky, complex and weak.

What are your experiences?

Thanks.
Paul.

↧
↧

Remove Internal Exchange Server Names and IP Addresses from Message Headers on Exchange server 2013

January 6, 2019, 4:20 am
$
0
0

Hi Team,

We are running Exchange server 2013 without Edge server only CAS and Mailbox and third party email gateway.

Whenever external senders send email to wrong recipient the NDR gives the full information about the internal host name and IP address of exchange server.

I followed the below link.

https://practical365.com/exchange-server/remove-internal-exchange-server-names-ip-addresses-message-headers/

the article is for a scenario where Edge transport servers is used, how do i configure this when there is no edge transport server ?

TechGUy,System Administrator.


↧

*@91&@Bhopal}((9636854282)) LoVe PrObLeMs S p e C i a L i s T B-A-B-A-J-I- in

April 10, 2019, 1:55 am
$
0
0
dkvedikfuhiufskfhsikfhisfhzkfhsihfsikhsi?
↧

Remove Internal Exchange Server Names and IP Addresses from Message Headers on Exchange server 2013

January 6, 2019, 4:20 am
$
0
0

Hi Team,

We are running Exchange server 2013 without Edge server only CAS and Mailbox and third party email gateway.

Whenever external senders send email to wrong recipient the NDR gives the full information about the internal host name and IP address of exchange server.

I followed the below link.

https://practical365.com/exchange-server/remove-internal-exchange-server-names-ip-addresses-message-headers/

the article is for a scenario where Edge transport servers is used, how do i configure this when there is no edge transport server ?

TechGUy,System Administrator.


↧
Search

Help with setting up authenticated external mail relay through our on-premises exchange 2013 servers

April 11, 2019, 1:21 pm
$
0
0

I need to configure external smtp relay with authentication on exchange 2013 server.
I went through the article below :

https://practical365.com/exchange-server/exchange-2016-smtp-relay-connector/

This article explains how to setup external SMTP Relay with Exchange Server 2016 Using Authentication, but I guess it is still relevant to exchange 2013. Is that correct?

So I tested the external relay by using the "Send-MailMessage" powershell command and using port 587 (without ssl switch as we don't have cert on that connector).
It did not succeed without credential as expected and succeeded with credential as expected.

On-premises exchange servers send to office 365 and then it should go out to internet. 
How can I get confirmation that it was using “SERVERNAMEClient Frontend SERVERNAME” connector for receive.
If I enable "RequireTLS" on this connector then are there any issues I should be aware of?

And which send connector it is using to send out to Office 365.
As per the article below it should be going through the send connector that is set to use "<OurDomain>-com.mail.protection.outlook.com":-
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/set-up-connectors-to-route-mail

I need to ensure that TLS 1.2 is used between on-premises exchange and office 365. Thus I need to ensure which connector it is going through.

↧
↧

Exchange 2013 : 550 5.1.1 User unknown for many recipients except just one recipient address is wrong

April 25, 2017, 6:31 am
$
0
0

Hello,

We have a strange error with our Exchange 2013 Server (CU13).

When an external user sends mail to 2 recipients which have same domain (samedomain.fr for example), if an address is wrong, the sender receives an error (see below) says 2 address are unknows. 

                   The mail system

<test3@samedomain.fr>: host mail.samedomain.fr[X.X.X.X] said: 550 5.1.1 User
    unknown (in reply to end of DATA command)

<toto@samedomain.fr>: host mail.samedomain.fr[X.X.X.X] said: 550 5.1.1 User
    unknown (in reply to end of DATA command)

Any ideas ?

Thanks for help.

Benoît

↧

Relayed email from printer/scanner to different domain in the same office 365 tenant.

April 14, 2019, 8:24 am
$
0
0
I need to relay email from printer/scanner using our internal exchange 2013 server "EX1" (int.abc.com domain). Even I need to allow email to other domains like xyz.com.
Our user mailboxes are already in Office 365.
Internal exchange server has a send connector setup to send email through "def.mail.protection.outlook.com" smart-host for "*" fqdn.
Other domain like xyz.com are federated to same Office 365 tenant as abc.com.
Currently I can't scan from scanner (setup to send mail through EX1) to xyz.com . It says EX1 is not in the allowed senders list for xyz.com domain.
I think one way to solve it is to add EX1 to the spf record for xyz,com. 
We need to do this for lot of domains.

I want to find out if there is a better way. Can office 365 route internally between abc.com and xyz.com without doing spf check as xyz.com domain is in same Office 365 tenant as abc.com?
↧

Setting up S/MIME on Exchange 2013

April 15, 2019, 6:19 am
$
0
0

Hello,

I've been tasked to setup S/MIME on the Exchange server and pretty much followed these steps.http://dizdarevic.ba/ddamirblog/?p=78

My main concern is the certificate. I guess I would need to get a new cert for the receiving end to install on their server. Would I need to install that same cert on the exchange server? How would this affect the current CA cert on the exchange server? Could I use the existing CA cert that I have? and if so, will it also send our private key to them?

Sorry, Cert is not my strong suit.

↧

Ignored X-OriginatorOrg header value 'domain name' because session capabilities do not allow it

April 15, 2019, 1:25 pm
$
0
0

I am trying to figure out why this e-mail is getting rejected.

Any help would be appreciated: 


2019-04-15T14:55:11.125Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,0,SERVERIP:25,208.117.55.132:42396,+,,
2019-04-15T14:55:11.125Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,1,SERVERIP:25,208.117.55.132:42396,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2019-04-15T14:55:11.125Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,2,SERVERIP:25,208.117.55.132:42396,>,"220 SERVERNAME.corp.userdomain Microsoft ESMTP MAIL Service ready at Mon, 15 Apr 2019 10:55:11 -0400",
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,3,SERVERIP:25,208.117.55.132:42396,<,EHLO o1.f.az.sendgrid.net,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,4,SERVERIP:25,208.117.55.132:42396,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,5,SERVERIP:25,208.117.55.132:42396,>,250-SERVERNAME.corp.userdomain Hello [208.117.55.132],
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,6,SERVERIP:25,208.117.55.132:42396,>,250-SIZE 62914560,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,7,SERVERIP:25,208.117.55.132:42396,>,250-PIPELINING,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,8,SERVERIP:25,208.117.55.132:42396,>,250-DSN,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,9,SERVERIP:25,208.117.55.132:42396,>,250-ENHANCEDSTATUSCODES,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,10,SERVERIP:25,208.117.55.132:42396,>,250-STARTTLS,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,11,SERVERIP:25,208.117.55.132:42396,>,250-X-ANONYMOUSTLS,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,12,SERVERIP:25,208.117.55.132:42396,>,250-AUTH NTLM,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,13,SERVERIP:25,208.117.55.132:42396,>,250-X-EXPS GSSAPI NTLM,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,14,SERVERIP:25,208.117.55.132:42396,>,250-8BITMIME,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,15,SERVERIP:25,208.117.55.132:42396,>,250-BINARYMIME,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,16,SERVERIP:25,208.117.55.132:42396,>,250-CHUNKING,
2019-04-15T14:55:11.250Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,17,SERVERIP:25,208.117.55.132:42396,>,250 XRDST,
2019-04-15T14:55:11.360Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,18,SERVERIP:25,208.117.55.132:42396,<,MAIL FROM:<bounces+5636024-4d17-kelley=userdomain@sendgrid.net>,
2019-04-15T14:55:11.360Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,19,SERVERIP:25,208.117.55.132:42396,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2019-04-15T14:55:11.360Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,20,SERVERIP:25,208.117.55.132:42396,*,08D6A0AAD45874BD;2019-04-15T14:55:11.125Z;1,receiving message
2019-04-15T14:55:11.360Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,21,SERVERIP:25,208.117.55.132:42396,>,250 2.1.0 Sender OK,
2019-04-15T14:55:11.454Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,22,SERVERIP:25,208.117.55.132:42396,<,RCPT TO:<kelley@userdomain>,
2019-04-15T14:55:11.579Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BD,23,SERVERIP:25,208.117.55.132:42396,>,250 2.1.5 Recipient OK,
2019-04-15T14:55:13.078Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,24,SERVERIP:25,148.163.135.239:55120,<,DATA,
2019-04-15T14:55:13.078Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,25,SERVERIP:25,148.163.135.239:55120,>,354 Start mail input; end with <CRLF>.<CRLF>,
2019-04-15T14:55:13.078Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,26,SERVERIP:25,148.163.135.239:55120,*,,Ignored X-OriginatorOrg header value 'silvertonmortgage.com' because session capabilities do not allow it
2019-04-15T14:55:13.094Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,27,SERVERIP:25,148.163.135.239:55120,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
2019-04-15T14:55:13.266Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,28,SERVERIP:25,148.163.135.239:55120,>,"250 2.6.0 <SN6PR05MB49748EF7EF39F5FABB72AF7CBE2B0@SN6PR05MB4974.namprd05.prod.outlook.com> [InternalId=121105192845808, Hostname=SERVERNAME.corp.userdomain] Queued mail for delivery",
2019-04-15T14:55:13.328Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,29,SERVERIP:25,148.163.135.239:55120,<,QUIT ,
2019-04-15T14:55:13.328Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,30,SERVERIP:25,148.163.135.239:55120,>,221 2.0.0 Service closing transmission channel,
2019-04-15T14:55:13.328Z,SERVERNAME\Default Frontend SERVERNAME,08D6A0AAD45874BB,31,SERVERIP:25,148.163.135.239:55120,-,,Local

↧
↧

Mail stuck in send queue

April 17, 2019, 12:05 pm
$
0
0

Getting this error when sending email to internet:

4.4.1 Error encuntered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060."

↧

Target host responded with Error. 535 5.7.3 Authentication Unsuccessful.

April 18, 2019, 4:05 am
$
0
0
Exchange Server Mail Submission Error. 
↧
Search

GAJSHGAHJFHAFAHGFHAGHAFHGAHGASF?

April 20, 2019, 12:00 am
$
0
0
GAJSHGAHJFHAFAHGFHAGHAFHGAHGASF?
↧

Black Magic Specialist Astrologer +91-9636854282

April 20, 2019, 12:14 am
$
0
0
BHCJHASVFHGAFGSVFDGHVFDHASVFGHAVFGHAVFGAVFA?
↧
↧

Is it possible to change an alias into a public folder?

March 27, 2019, 11:41 am
$
0
0

I have an alias email address that is set up to include several people for work but only 2 people have been given access to check the inbox for that alias. I'm looking to change the alias into a public folder so that no one is attached to the address and it only allows to the specific person or persons to see the reply instead of everyone. Can an alias email address be turned into a public folder?


↧

Opening Encrypted Emails with Exchange Account or Microsoft Account

March 14, 2019, 8:46 am
$
0
0
We have what may be a unique situation and I am hoping someone might be able to provide some assistance.  Our company is using Office 365 with a login of user at syr.companyname.  However, our email addresses are name at companyname. Our email is still run through and Exchange server.  We run into an issue when encrypted emails are sent to our employees through a customer's Office 365 account.  We cannot open the emails using our Office 365 login because the email address is not what is used for logging into Office 365. I understand the customer can modify their send settings to allow a different email address to open the encrypted emails, but they refuse to make that change.  We can use the one-time passcode, but this is extremely inconvenient as we receive several daily encrypted emails from the customer.  Since Microsoft no longer allows the option of creating a personal Microsoft login using a work email address, does anyone else have any suggestions on what we can do?  (Using a "personal" Microsoft login using the work email address does allow us to open the encrypted emails without issue.  However, not everyone had previously created a personal Microsoft login prior to the change.)  Our mail is hosted through an on-premises Exchange server.  We have not migrated to  AIP, our email is directed through Exchange and not 365.  Is there anyway we can add the email address as an alias to the Microsoft account when email is not hosted through 365?
↧

Migration from Exchange server 2010 to 2013

April 21, 2019, 10:17 pm
$
0
0

Hii,,

we have installed exchange 2013 in exchange 2010 environment.


User's can send email within Ex2010

User's can send email within Ex2013

User's can send email from Ex2010 to Ex2013

But cannot send from Ex2013 to Ex2010(if relay is enabled)

It gets queued and when i removed the message from toolbox with NDR, it says "The delivery to recipients has failed" The recipients email system isn't accepting emails now.

 I  checked the default receive connector settings on Ex2010 and found that "Exchange server" & "legacy Exchange servers" permissions are checked.


Not sure what i am missing.......

Thanks 





↧
Viewing all 3660 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>