the message reached the recipient’s email system but delivery was refused exchange 2003


Error: Messages sent to a Public Folder mailbox may not be delivered, and you may receive a non-delivery report (NDR) similar to the following:

—-Original Message—–
From: System Administrator
Sent: date
To: e-mail address
Subject: Undeliverable: Your message did not reach some or all of the intended recipients.
The following recipient(s) could not be reached: e-mail address on date
The message reached the recipient’s e-mail system, but delivery was refused.
Attempt to resend the message. If it still fails, contact your system administrator.
<ExchangeServerName. Your_DomainName.com #5.2.1>
Solution:
  1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. In the System Manager Microsoft Management Console (MMC), locate the public folder that you want to configure.
  3. On the Action menu, click Properties.
  4. Click the Permissions tab, and then click Client Permissions.
  5. In the box at the top of the Client Permissions dialog box, select Anonymous. In the Roles box, change the role from None to the level of access that you want. For example, select the default level of access to Contributor.
  6. Click OK two times

Ref url: http://support.microsoft.com/kb/319753

Advertisements

rpc.nfsd unable to set any sockets for nfsd


Error: When you install and restart NFS service you will get an error “rpc.nfsd unable to set any sockets for nfsd”

Root cause: This problem may occur due to rpcbind service is not working or the app is not been installed on the server.

Solution:

1. Check the rpcbind service works perfectly by:- #rpcbinfo -p

2. If it throws an error by “rpcinfo: can’t contact portmapper: RPC: Remote system error – No such file or directory”

3. Then we need to install the rpc package by

3a. # yum install avahi
Installing : libdaemon-0.14-1.fc13.i686
Installing : avahi-0.6.27-1.fc14.i686

4. Then restart rpcbind service and check # rpcinfo -p status

5. Then restart nfs service.

6. Check the NFS daemon are avaiable in all run levels by #chkconfig nfs –list

7. Now restart the NFS service where the service starts successfully.