SMTP Error and Reply codes

I was recently asked about SMTP Errors / Reply Codes and I realized that I have not committed them to memory , so I decided to look them up and found this really nice table.  

Check the RFC index for further mail-related RFCs.

Reply codes in numerical order
Code	Meaning
200	(nonstandard success response, see rfc876)
211	System status, or system help reply
214	Help message
220	<domain> Service ready
221	<domain> Service closing transmission channel
250	Requested mail action okay, completed
251	User not local; will forward to <forward-path>
354	Start mail input; end with <CRLF>.<CRLF>
421	<domain> Service not available, closing transmission channel
450	Requested mail action not taken: mailbox unavailable
451	Requested action aborted: local error in processing
452	Requested action not taken: insufficient system storage
500	Syntax error, command unrecognised
501	Syntax error in parameters or arguments
502	Command not implemented
503	Bad sequence of commands
504	Command parameter not implemented
521	<domain> does not accept mail (see rfc1846)
530	Access denied (???a Sendmailism)
550	Requested action not taken: mailbox unavailable
551	User not local; please try <forward-path>
552	Requested mail action aborted: exceeded storage allocation
553	Requested action not taken: mailbox name not allowed
554	Transaction failed

Thanks to  Greenend.org

PowerShell Script to list daily health checks of all Exchange 2007 Servers.

$ExchServer=Get-ExchangeServer
foreach ($Server in $ExchServer)
{
echo $Server.name (Test-ServiceHealth $Server)
}


SMTP Port 25

Upgrade of a NetBackup master server to version 7.1.0.2 may cause bmrsavecfg failures at backup time when Bare Metal Restore (BMR) information is being collected.  At backup time, the BMR process runs a bmrsavecfg job that will collect information from the client and submit the data into the BMR database on the master server to be imported. Although this process previously worked prior to the upgrade, there may be failures while the data is being imported into the BMR database.

Error Messages in Job Detail Status:

 BMRERR: Received BMR error: Failed to import Config file. (1) 
Error bpbrm(pid=6456) BMRERR: Received BMR error: Failed sending the discovery. (1) 
Error bpbrm(pid=6456) BMRERR: Received BMR error: BMR information discovery failed. (1)

Symantec TechNote

NetBackup Status Code 59

Every now and then some of my Netbackup jobs end with status code 59 which means that the Netbackup master or Media server is not in the client Server allow list.  This usually happens after an Agent upgrade which not a big issue, but annoying none the less.

Message: access to the client was not allowed
Explanation: The master or the media server tries to access the client, but the client does not recognize the server as a valid server.
For the Enterprise Vault Agent: The names of all of the media servers among the Enterprise Vault servers are not specified in the client configuration.
Recommended Action: Do the following, as appropriate:
•    If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:
•    1. Open the Backup Archive and Restore Utility on the Windows Client.
•    2. Select File >Specify NetBackup Machines and Policy Type
•    3. On the Specify NetBackup Machines  and Policy Type dialog opens Select Edit Server list and type in the name of Netbackup master or media server that will backup the client up..

Update: I've not had a chance to try this fix but it seems related.  From Symantec How TO articles. 

bpsetconfig

I have also seen this fix for status code (46) I've seen the technote but do not have the link. 
From the Netbackup OppsCenter Help Menu

Netbackup: Import Disk Based images

This is the procedure I used to import Netbackup disk based images from a failed media server.  This is a 2 phased method that uses the NBU Admin console.  Phase 1 initiates the import process by locating the path to the images to be imported and the second phases imports the images into the database.  The disk images must be present on a local disk. In my experience network importing from a network share did not work.

Phase 1
Importing NetBackup disk images
First, run the "phase 1 import".
1. Start the NetBackup Administration Console and go to the Catalog section.
2. From the menu select Actions > Initiate Import and a dialog box will appear.
3. Check the "The images to be imported are on disk" radio button and enter a disk path to import images from.
4. Check the Activity Monitor for progress of the phase one import.

Phase 2
Once the "phase 1 import" completes, run the "phase 2 import".
1. Start the NetBackup Administration Console and go to the Catalog section.
2. Under Pathname:, enter the disk path used for the phase 2 import.
3. Select a date range for the images to import and click the Search button.
4. Select Backup IDs to import from the search results.
5. From the menu select Actions > Import to begin the phase 2 import.
6. Check the Activity Monitor for progress of the phase 2 import.

Once the phase 2 import completes successfully, the disk images will be available for restores.


Documentation

VDR: Remove Damaged Restore Points

Remove Damaged Restore Points

Corrupt restore points, which are identified during integrity checks, should be removed. Restore points may be identified as damaged during transient connection failures. If transient connection failures are possible, check if damaged restore point issues are resolved after connections are restored.

Prerequisites
Before you can remove damaged restore points, you must have restore points in a functioning Data Recovery
deployment.

Procedure
1 In the vSphere Client, select Home > Solutions and Applications > VMware Data Recovery.
2 Click the Reports tab and double-click the integrity check that failed.

The Operations Log for the event opens in a separate window. Note which restore points triggered the
failure.

3 Close the Operations Log and click the Restore tab.

4 From the Filter dropdown list, select Damaged Restore Points.
Available restore points are filtered to display only the virtual machines with damaged restore points. It
may be necessary to expand a virtual machine's node to display the damaged restore point.

5 Select damaged restore points for removal and click Mark for Delete.

6 Initiate an integrity check.
Completing an integrity check causes all restore points marked for deletion to be removed.

7 Review the results of the integrity check to ensure no damaged restore points remain.


VMware Data Recovery Administration Guide
28

Exchange 2007: Fowad all Mail

This is the Procedure to forward all mail from one Exchange 2007 mailbox to another mailbox without leaving a copy on the original recipient mailbox. 

Exchange management Shell:

Set-Mailbox -Identity "John Smith" -ForwardingAddress "sara@contoso.com"

Use following ccmlet to forward all mail while leaving a copy on the original recipient mailbox. 

Set-Mailbox -Identity "John Smith" -ForwardingAddress "sara@contoso.com" -DeliverToMailboxAndForward $true

Exchange Management Console:

1.   In the console tree, expand Recipient Configuration, and then click Mailbox.

2.  In the result pane, right-click the mailbox for which you want to configure mail forwarding and click Properties.

3.  In <Mailbox> Properties, on the Mail Flow Settings tab, click Delivery Options, and then click Properties.

4.  Click the Forward to check box. This enables the Browse button.

5.  Click Browse to open the Select Recipient dialog box. Select the recipient to whom you want to forward messages, and then click OK.

6.  If you want incoming messages to be delivered to the mailbox as well as to the forwarding address configured, select the Deliver message to both forwarding address and mailbox check box. Clear this check box to forward all incoming messages without retaining copies in the mailbox.

7.  Click OK to return to <Mailbox> Properties.

8.  Click OK.