analytics/configuration/smtpRules-default.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--
    Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved.
    Cognos (R) is a trademark of Cognos ULC, (formerly Cognos Incorporated).
-->

<!-- 
211 - A system status message. 
214 - A help message for a human reader follows. 
220 - SMTP Service ready. 
221 - Service closing. 
250 - Requested action taken and completed. The best message of them all. 
251 - The recipient is not local to the server, but the server will accept and forward the message. 
252 - The recipient cannot be VRFYed, but the server accepts the message and attempts delivery. 
354 - Start message input and end with <CRLF>.<CRLF>. This indicates that the server is ready to accept the message itself (after you have told it who it is from and where you want to to go). 
421 - The service is not available and the connection will be closed. 
450 - The requested command failed because the user's mailbox was unavailable (for example because it was locked). 

Try again later. 
451 - The command has been aborted due to a server error. Not your fault. Maybe let the admin know. 
452 - The command has been aborted because the server has insufficient system storage. 

The following error messages (500-504) usually tell you that your email client is broken. It's probably best to let the program's author know. 
500 - The server could not recognize the command due to a syntax error. 
501 - A syntax error was encountered in command arguments. 
502 - This command is not implemented. 
503 - The server has encountered a bad sequence of commands. 
504 - A command parameter is not implemented. 
550 - The requested command failed because the user's mailbox was unavailable (for example because it was not found, or because the command was rejected for policy reasons). 
551 - The recipient is not local to the server. The server then gives a forward address to try. 
552 - The action was aborted due to exceeded storage allocation. 
553 - The command was aborted because the mailbox name is invalid. 
554 - The transaction failed. Blame it on the weather. 
-->

<!--in order to make changes to the rules used by the nc mail server you will have to set the advanced property 'smtp.rules.properties.location' to point
to a file on your server or a classloader resource path and include the file in the classes dir (or a jar in webapps lib). while developing new rules it may be usefull to
set the smtp.rules.properties.reread advanced property to true so that the rules file is reread for every request. be sure to unset this after you are happy with the changes.-->
<smtpRules xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\smtpRules.xsd">
	
	<!--transport issues... server or authorisation try again indefinately until its fixed -->
	<smtpRule>
		<smtpError>
			<transport>true</transport>
		</smtpError>
		<smtpBehaviour name="transport">
			<keepMail>false</keepMail>
			<resends number="-1" delaySeconds="30"/>
		</smtpBehaviour>
	</smtpRule>

	<!--the mail is sent with one or more invalid recipients 
		a fail mail with a variation on the original subject will be sent to the user performing the run-->
	<smtpRule>
		<smtpError>
			<invalidRecipients>true</invalidRecipients>
		</smtpError>
		<smtpBehaviour name="invalidRecips">
			<keepMail>false</keepMail>
			<failMail>
				<recipients sendToCurrentRecipients="false">
					<owner>true</owner>
				</recipients>
			</failMail>
		</smtpBehaviour>
	</smtpRule>
	
	<!--these next three rules cope with recipient errors where the email address is valid, but has been rejected by the server. The codes were harvested from the
javamail source 551 is a code that is thrown when the argosoft mail server cannot find the address locally and does not relay-->
	<smtpRule>
		<smtpError>
			<errorCode>550</errorCode>
		</smtpError>
		<smtpBehaviourName>invalidRecips</smtpBehaviourName>
	</smtpRule>
	<smtpRule>
		<smtpError>
			<errorCode>553</errorCode>
		</smtpError>
		<smtpBehaviourName>invalidRecips</smtpBehaviourName>
	</smtpRule>
	<smtpRule>
		<smtpError>
			<errorCode>551</errorCode>
		</smtpError>
		<smtpBehaviourName>invalidRecips</smtpBehaviourName>
	</smtpRule>
	
	<!--the default behaviour is to attempt to resend 3 times with an hour delay the fail mail is the default which uses the original subject and recipients-->
	<defaultSmtpBehaviour>
		<smtpBehaviour name="default">
			<keepMail>false</keepMail>
			<resends number="1" delaySeconds="3600"/>
			<failMail/>
		</smtpBehaviour>
	</defaultSmtpBehaviour>
	
	<!--this sample shows how you can separate the behaviour from the rule
		 this can be useful to re use behaviours-->
	<!--
	<smtpRule>
		<smtpError>
			<invalidRecipients>true</invalidRecipients>
		</smtpError>
		<smtpBehaviourName>invalidRecips</smtpBehaviourName>
	</smtpRule>-->
	
	<!--the error code here is an smtp return code. include a rule here when your mail server is producing
		 unusual or specialized errors that you want to handle differently-->
	<!--<smtpRule>
		<smtpError>
			<errorCode>521</errorCode>
		</smtpError>
		<smtpBehaviour name="specialInvalidRecips">
			<keepMail>false</keepMail>
			<failMail>
				<subject>special error code 521</subject>
			</failMail>
		</smtpBehaviour>
	</smtpRule>-->
	
	<!--this sample shows how a fail mail can be sent to a specific recipient and with a hardcoded subject
       this example is in response to a special error code -->
	<!--<smtpRule>
		<smtpError>
			<errorCode>502</errorCode>
		</smtpError>
		<smtpBehaviour name="speciaErrorCode 502">
			<keepMail>false</keepMail>
			<failMail>
				<subject>special error code 502 - sent to a special recipient</subject>
				<recipients sendToCurrentRecipients="false">
					<recipient address="specialFailMailRecipient@cognos.com"/>
				</recipients>
			</failMail>
		</smtpBehaviour>
	</smtpRule>-->
	
	<!--if you decide to keep a mail from a particular error case, the mail will be left in the database queue. the queue name in the db table will include 
         'backup' in order to reactivate those messages, you will have to execute some sql to change the queue name to the original value and restart the server-->
	<!--<smtpRule>
		<smtpError>
			<errorCode>550</errorCode>
		</smtpError>
		<smtpBehaviour name="specialErrorCode-550">
			<keepMail>true</keepMail>
			<failMail>
				<subject>special error code 550 keep mail</subject>
			</failMail>
		</smtpBehaviour>
	</smtpRule>-->
	
	<!--this is a floating behaviour that can be referenced by name from the other rules-->
	<!--<smtpBehaviour name="invalidRecips">
		<keepMail>false</keepMail>
		<failMail>
			<recipients sendToCurrentRecipients="false">
				<owner>true</owner>
			</recipients>
		</failMail>
	</smtpBehaviour>-->
	

</smtpRules>