> From: otrs-request@otrs.org
> Subject: otrs Digest, Vol 32, Issue 44
> To: otrs@otrs.org
> Date: Fri, 13 May 2011 18:53:28 +0000
>
> Send otrs mailing list submissions to
> otrs@otrs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.otrs.org/cgi-bin/listinfo/otrs
> or, via email, send a message with subject or body 'help' to
> otrs-request@otrs.org
>
> You can reach the person managing the list at
> otrs-owner@otrs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of otrs digest..."
>

Hello...I am using OTRS 3.0.6. In the system I have set up, OTRS is getting emails from from our NPM server that are triggered by SNMP traps. The NPM server filters and formats the emails sent to OTRS, each email triggered by a specific SNMP trap. We are using this setup to monitor an optical network, including facility (HK) alarms. All is working OK, except for the fact that the SNMP traps that come from our optical nodes do not have the host name of the node embedded in the trap. Instead of implementing hostfiles on the back-end to correlate node location, I am trying to use a regex containing the IP list of all nodes at a specific site as a PostMaster Filter to set the TicketFreeKey#3 (configured as the network locations). Now, when I trigger an alert for testing purposes I can see in the System Log that the regex is working because the alert did hit the filter, and it says that the FreeKey was set to the correct value, but when I look at the ticket created it is not there. The free field is still blank. I have gone over and over the SysConfig, and still cannot find what I have done wrong. Can anybody on the list let me know if they have had similar experiences with the with not being able to set the TriggerFreeKey via PostMaster Filters? Any guidance would be greatly appreciated. 

Thanks,
Eric