제2의 비엔지니어 인생관을 꿈꾸며
An internal email distribution group set with an external email address is not able to receive emails from external users. You do not receive Non-Delivery Reports (NDR) as well. This issue is seen on both Microsoft® Exchange Server® 2007 and 2010 versions.
The email distribution groups are configured to require sender authentication by default. When it comes to messages from external sources, it is not possible to authenticate the sender. To successfully send messages externally, you need to disable the mandatory authentication of senders.
To enable the email distribution group to receive emails from external sources, follow the procedure below:
1.Log on to the Exchange Server as an administrator user.
2.Click Start, All Programs, Microsoft Exchange Server 2007, Exchange Management Console.
3.In the Exchange Management Console window, on the left-hand pane, browse to Recipient Configuration, Distribution Group.
4.Select the email distribution group from the middle pane and click Properties in the right-hand pane.
5.In the email distribution group Properties window, select the Mail Flow Settings tab. For example, the image below shows the Properties window of the email distribution group 'AA Sales'.
6.Select Message Delivery Restrictions and click the Properties... button on the top.
Email Distribution Group Properties
7.In the Message Delivery Restrictions window, uncheck the 'Require that all senders are authenticated' check box.
Disable the sender authentication
8.Click OK, Apply and OK again. The email distribution group will now be able to receive emails from the external sources.
9.By default, all email distribution groups are set to authenticate the senders, so the procedure above needs to be applied to all email distribution groups that need to receive externally sent emails.
Note: The procedure above is also applicable for Exchange Server 2010.
그룹메일이 자꾸 라우팅 실패가 떨어지면서 SMTP 송수신이 문제인가 한참을 찾았습니다. 외부에서 개인메일 전부 송수신되고 내부에서도 그룹메일 전부 송수신이 되는데 유일하게 외부에서 그룹메일로 보내면 인증안되었다고 트래킹로그에 남더랍니다. 2013 만쓰고 있어서 2010이 긴가민가만 생각이 들고 이런경우 혹시나 싶어서 포스팅 남깁니다.
http://www.cievo.sk/2013/04/13/exchang ··· omain%2F
We had Active Directory domain called DOMAIN.LOCAL. There was Exchange 2010 installed. It was fully functional. After some time I added new sub-domain/child domain SUB.DOMAIN.LOCAL and migrated users with mailboxes from DOMAIN.LOCAL to SUB.DOMAIN.LOCAL.
Error stated: Exception message: Could not find any available Domain Controller in domain DC … so problem is probably in the way Exchange locates domain controllers. When users clicked F5 or refreshed website, he could see his e-mails normally.
There was also event 2130 logged on Exchange server saying Exchange Active Directory Provider could not find an available domain controller in the domain.
When you want to install Exchange into Active Directory domain, you need to prepare forest and also domain before you install it. You use setup.com (from installation DVD of Exchange) with some switches (for example /PrepareSchema, /PrepareAD,…). So new added domain SUB.DOMAIN.LOCAL to existing AD Forest was not prepared for Exchange implementation. I ran following command setup.com /PrepareDomain:SUB.DOMAIN.LOCAL:
If you have more then one domain to prepare for Exchange, you can use command setup.com /PrepareAllDomains.
The best way to run /PrepareDomain or /PrepareAllDomains is:
I hope you will not make same mistake as I did
트리도메인에 익스체인지 설치할때 엄청난 삽질을 하다보다 이글보고 겨우 해결된 케이스였습니다.
2013 다르고 2010 다르다보니 많이 어지럽기도 하고 트리도메인 만들때부터 단번에 설치되는 케이스가 한번도 없었습니다. 자식도메인 별무리가 없었는데 트리도메인은 정말 어지럽더군요.
sudo apt-get update –fix-missing
sudo dpkg –configure -a
sudo apt-get install -f
the problem of a broken package still exist the solution is to edit the dpkg status file manually.
Unlock the dpkg – (message /var/lib/dpkg/lock)
sudo fuser -vki /var/lib/dpkg/lock
sudo dpkg –configure -a
You can delete the lock file with the following command:
sudo rm /var/lib/apt/lists/lock
You may also need to delete the lock file in the cache directory
sudo rm /var/cache/apt/archives/lock