Issues with Send-MailMessage, Exchange 2013 and Distribution Groups - The server response was: 4.7.0 - PRX1

Hello,

I have a scheduled task running a PowerShell script as a Domain User that at the end sends an email to a Distribution Group.

As part of trying to identify why it doesn't always send to the Distribution Group I have added in an identical command to send the message directly to myself. The email to me is received but the email to the group is never received.

The transcript from the script includes this error:

Send-MailMessage : Error in processing. The server response was: 4.7.0 
Temporary server error. Please try again later. PRX1 
At C:\_Scripts\_IDAM\_IDM\manageAD_TestEmail.ps1:187 char:1+ Send-MailMessage -To toaddress -From replyaddress ...    

+ CategoryInfo          : InvalidOperation: (System.Net.Mail.SmtpClient:Sm    tpClient) [Send-MailMessage], SmtpException    
+ FullyQualifiedErrorId : SmtpException,Microsoft.PowerShell.Commands.Send    MailMessage
  • I can email the group through Outlook
  • The group is set to receive unauthenticated email (inside and outside the organisation)

Help... please...


  • Edited by mtwelve Monday, January 19, 2015 12:07 PM
January 19th, 2015 12:06pm

Hi ,

1.To segregate this issue just try to send an email to distribution group via telnet command from the machine on where the scheduled task is running.

telnet smtp server ip 25

2.Same time please tell me is this issue is happening intermittently or else it is persisting constantly for all the emails send to distribution group.

3.On your command ,Please use the smtp server ip address instead of using the host name.

Reply me if anything is unclear.

Free Windows Admin Tool Kit Click here and download it now
January 19th, 2015 1:35pm

Hi,

Please refer and see if it helps...: https://social.technet.microsoft.com/Forums/exchange/en-US/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5?forum=exchangesvrgeneral

Add the local server's IP to our hosts file in below format:

192.168.1.5 server
192.168.1.5 server.domain.local

Restart "Microsoft Frontend Transport" and "Microsoft Exchange Transport" services
January 19th, 2015 3:42pm

See if this one helps

http://www.servolutions.com/support/articles/Temporaryservererror2013.htm

Free Windows Admin Tool Kit Click here and download it now
January 19th, 2015 3:44pm

Hello S.Nithyanandham,

1. Didn't work - 451 4.7.0 Temporary server error. Please try again later. PRX1

2. From the script this must have worked before but it then became intermittent, last few days, and now I can't get it to send at all.

3. Didn't make a difference. Same errors.

I will look at the other suggestions. I have seen those articles but hadn't explored because they were PRX5 errors.... whatever that may indicate.

January 19th, 2015 4:08pm

Are you supposed to add the HOSTS file entries for the Exchange server to that Exchange server?
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2015 4:30pm

Hi ,

Where that scheduled script is running ? is it running on a separate machine or it is running directly on a exchange server ?

Have you checked the network card settings and bindings on the exchange server to make sure the name resolution part is working fine?

January 20th, 2015 5:41am

The script is running on a member server not an Exchange server

What is the expected configuration? Is there an example or test procedure for me to check against?

We have 4 CAS servers and 2 Mailbox servers

Free Windows Admin Tool Kit Click here and download it now
January 20th, 2015 9:33am

Hi ,

Thanks for your update.Please reply back with your answers for my questions.

Did you face any error when you try to send an email from exchange server to that distribution group through telnet commands ?

On your script please tell which exchange server is used as smtp server ?i mean whether cas or mailbox server ?

On your member server how many network cards did you have ?

On your member server just have the Host A records like below 

192.168.1.10 casserver1

192.168.1.10 casserver1@abc.com

On the above scenario i would assume 192.168.1.10 as your smtp server ip address .In your case it would be cas or mailbox.

January 20th, 2015 9:46am

Hi,

According to error message 451 4.7.0 Temporary server error. Please try again later. PRX1, it seems that the encoded SMTP response for when proxy fails because destinations were not provided.

Please try to new a Distribution Group and disable Require that all senders are authenticated for test. Besides, please try to run following command by EMS:

Send-MailMessage -To groupaddress -From replyaddress  -Subject "test mail" -Body "this's a test mail, can you get it?" -SmtpServer "xxxx"

Additional, please run Test-Mailflow to double confirm whether everything is ok.

Best Regards,
Allen Wang

Free Windows Admin Tool Kit Click here and download it now
January 20th, 2015 9:56am

Your suggestion of testing from the Exchange made think to try testing each individual CAS server. It turns out when using 2 of our 4 CAS servers the email sends fine. This is through Telnet and the script from the member server.

SMTP server is set to the 4 CAS servers using DNS round robin. As above when it is set to one of the specific, working, CAS servers it send OK.

Member server has one virtual NIC. It's working with those 2 of the 4 CAS servers without having to add the Hosts file entries.

Is there an example of the NIC/DNS setup requirements for Exchange that may indicate what is wrong with the other 2 servers? They have one adapter and no DNS reference set to the loopback address....

January 20th, 2015 11:47am

Hi ,

I am not sure for a checking purpose , please disable the ipV6 on those cas servers network adapters and check the results.

Before disabling that just check whether ipv6 is disabled on the cas servers which is working fine.

Free Windows Admin Tool Kit Click here and download it now
January 20th, 2015 1:44pm

IPV6 is disabled on all the NICs on all the CAS servers - working and nonworking

I have checked and none of the servers have the registry changes identified here - http://support.microsoft.com/kb/929852

January 20th, 2015 4:11pm

Hi ,

1.while trigerring emails through those two problematic cas servers why don't we have a host file entry on the member server for a checking purpose.

2.For a testing purpose ,Instead of using default receive connectors on those two cas servers why don't we create a new dedicated receive connector (with front end transport role) for that member server to relay emails. 

On that newly created receive connector just have only the ip address of the member server in the remote network settings.

Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2015 8:13am

Hi,

we had the same issue - actually we still have.
With Professional support we found out:
- when email was sent using a frontend rec. connector, it was not accepted, if:
- recipient was a distribution group
- recipient was in internet
- it worked, when:
- mail was sent using to HubTransport rec. connector directly or
- mail was sent to mailbox enabled user in our organization

Unfortunately professional support did not find any solution
- hosts file modification
- AD check
- recreating a default configuration of rec. connector
- restart of services

Fortunately:
- problem "solved" when reboot of server was done after several hours

In our case we had 2 nodes cluster, therefore we could afford to wait (and meanwhile to exclude impacted exchange server).

I believe, that a root cause was not solved, because we had this issue already before (usually after CU installation or a reboot), but professional support is break-fix and does not do root cause analysis (which is in scope of premier support). I also believe it is not because of configuration error, but because of bug. It might be nice if Microsoft could investigate the problem deeper because as you can see, you're not the only impacted user.

Note: Sometimes restart of frontend transport and transport service helped, too. Actually because of this issue we have integrated it to our mailflow check script.

April 13th, 2015 7:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics