For the mails (both internal and external) bouncing back saying "rejected by a mail rule", IBM has

given following solution. Since it is a regular complaint from many senders, can you please go
thro and confirm possible action please?

MSK

From: Shrikant Veeturi <v.shrikant@in.ibm.com> [mailto:Shrikant Veeturi

<v.shrikant@in.ibm.com>]
Sent: Friday, November 17, 2006 9:00 AM
To: m.senthilkumar@rane.co.in
Subject: RE: PMR#34256,999,744(mail bounce and rule issue )

HI Senthil.

Below are some debugging parameters which can be useful for you to find out which
rule has been executed :

The following NOTES.INI parameters are useful for debugging system rules:

DEBUG_SYSTEM_RULES=1 -- controls output by the server task when registering

and de-registering system mail rules.

DEBUG_MONITOR=X -- is a flags mask that controls debug log statements for

monitors, mostly implemented for user and system mail rules. Here are the useful
flag values for both user and system mail rules:
MONITOR_DEBUG_TRACE_SYSRULE_ACTION (0x0001) 1
MONITOR_DEBUG_TRACE_SYSRULE_EACH (0x0002) 2
MONITOR_DEBUG_TAG_SYSRULE_ACTION (0x0004) 4
MONITOR_DEBUG_TRACE_USERRULE_ACTION (0x0008) 8
MONITOR_DEBUG_TRACE_USERRULE_EACH (0x0010) 16
MONITOR_DEBUG_TAG_USERRULE_ACTION (0x0020) 32

The Trace options can be enabled for each type of rule. Sample NOTES.INI values:

DEBUG_MONITOR=1 traces system rule actions triggered

DEBUG_MONITOR=2 traces each system rule as it executes
DEBUG_MONITOR=3 both 1 and 2
DEBUG_MONITOR=8 traces user rule actions triggered
DEBUG_MONITOR=16 traces each user rule as it executes
DEBUG_MONITOR=24 both 8 and 16
The TAG options cause an item to be added to the note when a user or system rule
action has been triggered. This field is named $FilterBy. Sample NOTES.INI values:

DEBUG_MONITOR=4 tags server rules

DEBUG_MONITOR=32 tags user rules

$FilterBy item: "U3" -- The 3rd enabled user rule took an action on this note.
$FilterBy item: "S2" -- The 2nd enabled system rule took an action on this note.

If there are multiple actions per rule, you will see them all appended to the $FilterBy
text list. The same list is used for user and system rules so you may see:

$FilterBy = "S2", "U7."

NOTE: Adding the flag values for DEBUG_MONITOR will produce multiple debug
levels. For example if you would like to trace the rule Action ( DEBUG_MONITOR
=1), the rule Execution ( DEBUG_MONITOR =2), and have the message tagged
with $FilterBy ( DEBUG_MONITOR =4) you would set DEBUG_MONITOR = 7
(1+2+4).

How to Examine Output Generated from System Mail Rules Debug

Parameters.

Debug_System_Rules=1

Once "set rules" is issued on the server console or the server starts up, information
about the registration of the rules will be generated. At this point rules will be
registered as monitors on each mail.box sequentially.

05:26:56 PM Successfully deregistered system mail rules for mail1.box

05:26:56 PM System Mail rule formula item $FilterFormula_0 not found: Note item not found
05:26:56 PM System Mail rule formula item $FilterFormula_1 read successfully
05:26:56 PM Successfully registered system mail rule filter 1 for mail1.box, MonitorID 445146C8: 1C
05:26:56 PM Successfully deregistered system mail rules for mail2.box
05:26:56 PM System Mail rule formula item $FilterFormula_0 not found: Note item not found
05:26:56 PM System Mail rule formula item $FilterFormula_1 read successfully
05:26:56 PM Successfully registered system mail rule filter 1 for mail2.box, MonitorID 445146C8: 1E

1. All current rules registered as monitors on mail.box will be deregistered.

"Successfully deregistered system mail rules for mail1.box"

2. Each rule, which is stored in $FilterFormula_# of the Configuration document, will

be read and verified. Use NotesPeek to examine the details of this rule in the
Configuration document.
"System Mail rule formula item $FilterFormula_0 read successfully"

3. If the $FilterFormula_# had been Disabled or has been Deleted then the item will
not be registered. (Skip to step 5)
"System Mail rule formula item $FilterFormula_# not found: Note item not found"

4. When the current rule is registered information about the rule, like rule number,
MonitorID, and MonitorID alias will be given. These values can be used with
conjunction with Debug_Monitor to track the rules being executed and triggered.
"Successfully registered system mail rule filter 0 for mail1.box, MonitorID 568EF389 :
11 "
Rule Number_/ Monitor id_/
Alias id_/

5. The rest of the rules will be registered on the current mail.box until
$FilterFormulaCount has been reached.

6. The process happens again until all mail boxes have had the rules registered.

DEBUG_MONITOR=X

Depending on the value given, Debug_Monitor will log information as the rule is
executed and triggered.

DEBUG_MONITOR=1

• Will output information when a system rule have been triggered (the rule
condition has been met) and an action has been performed.

DEBUG_MONITOR=2

• Will output information about each system rules when being tested against its
conditions. When the rules are processed, all registered mail rules should
show execution.

DEBUG_MONITOR=3

• Will output information from both the execution and trigger of the system
rules. If a rule is triggered the output will show the execution and the action
immediately after. If there is no action then only the execution is shown.

05:56:26.84 PM [2BE8:0046-2A20] DebugMonitorTrace> Db=c:\Lotus\Domino\smtp-a\mail3.box

MonitorID=445146C8: 29 system rule 1 has been executed.
05:56:26.85 PM [2BE8:0046-2A20] DebugMonitorTrace> Db=c:\Lotus\Domino\smtp-a\mail3.box
MonitorID=5BB368E6: 2A system rule 2 has been executed.
05:56:26.85 PM [2BE8:0046-2A20] DebugMonitorTrace> Db=c:\Lotus\Domino\smtp-a\mail3.box
MonitorID=5BB368E6: 2A system rule 2 action: $JournalResponsibility changed to 1.
When the execution of a rule is outputed, information is given about the thread id, the
MonitorID and its alias, and the rule number. (In red below)

05:56:26.84 PM [ 2BE8:0046-2A20 ] DebugMonitorTrace> Db=c:\Lotus\Domino\smtp-a\mail3.box MonitorID=

445146C8 : 29 system rule 1 has been executed.
With Debug_Threadid=1 one can determine with which task triggered the processing
of the system rules and with Debug_System_Rules=1 the MonitorID can be matched
with the corresponding $FilterFormula_#.

When the action of a rules is outputed, the same information is given as the execution
except the action the rule takes is also given.

05:56:26.85 PM [2BE8:0046-2A20] DebugMonitorTrace> Db=c:\Lotus\Domino\smtp-a\mail3.box

MonitorID=5BB368E6: 2A system rule 2 action: $JournalResponsibility changed to 1.

This information can be used to give details about the action and to determine
whether the rule performed the correct action.

I hope that Above information will help you in debugging the rules .

Please let me know if you need any further assistance on this PMR .

Thanks and regards,

Shrikant Veeturi
software Engineer
IBM Workplace, Portal, and Collaboration Software
V.Shrikant@in.ibm.com

m.senthilkumar@rane.co.in To Shrikant Veeturi/India/IBM@IBMIN

cc
13/11/2006 14:04 Subject RE: PMR#34256,999,744(mail bounce and rule issue )

1) Please note that the primary contact is given as Email and not as Landline. But I don't know
why IBM is always taking the secondary contact and try to call landline irrespective of time.
2) I have clearly mentioned the delivery failure report in my PMR that DELIVERY FAILURE:
****mail rejected by a mail rule**** is the error message users are getting. If we disable some rule,
it started delivering properly. The issue (or requirement) here is not the rule but how to identify
which rule causing this rejection. If there is a way to find out which rule rejected which mail, we
can give alert to users to remove that particular text or attachment and resend the same mail

We can't send the rules. DFR is not required as we don't require to investigate on the rejection
which is happening properly by would require more details on rejection, which is not found in
tracking centre or anywhere.

MSK

From: Shrikant Veeturi <v.shrikant@in.ibm.com> [mailto:Shrikant Veeturi

<v.shrikant@in.ibm.com>]
Sent: Monday, November 13, 2006 1:29 PM
To: m.senthilkumar@rane.co.in
Subject: PMR#34256,999,744(mail bounce and rule issue )

HI Senthil,

It is to confirm that I will be point of contact for this PMR.

I tried to call you but the number seems to be changed ,please provide your contact
no. so that I can contact you directly when needed.

As per the PMR description , "some of your mails are getting rejected due to server
mail rule you have set ,but you are not able to identify due to which rule it is
bouncing back."

For further investigation we need to know what rules you have in the server and what
the Delivery failure report is saying .
If you can send us the rules and DFR to us then we will try to simulate the issue here
and try to find out the cause .

I will wait for your response.

Thanks and regards,

Shrikant Veeturi
software Engineer
IBM Workplace, Portal, and Collaboration Software
V.Shrikant@in.ibm.com