TrappingBadMessagesGWIA

From CoolSolutionsWiki

> my other wikis

Trapping bad messages going through GWIA

Error message: AA02-Invalid minimum string length


[edit]

Setting up to trap the bad messages

NOTE: Assuming Linux, but the steps are similar on NW/Windows.

  1. Modify /opt/novell/groupwise/agents/share/gwia.cfg and near the bottom of the file you will see a rt 4 . This stands for receive thread 4, by changing this to zero the receive thread will be zero and the GWIA will NOT forward messages to the other queues.
    1. vi /opt/novell/groupwise/agents/share/gwia.cfg | press </b> /</b> and typ rt or you can page down. Don't make my mistake of editing the commented one near the top of the file, if there is one ALSO at the bottom it will ignore your modification.
    2. You want to minimize the "down time" because all incoming mail will queue up - so try to do this fast.
  2. /etc/init.d/grpwise stop
  3. /etc/init.d/grpwise start
  4. Have the person send the message that will NOT pass through your system.
    1. You may need to figure out which directory is the gwia's receive directory. To do this, (assuming you use GW http monitor) go to: http://TheIpAddrOrDNSofYourGwiaBox:9850 | environment or config and see the gwia directory. On my system it is /opt/novell/groupwise/domain/gwgate/gwia/receive I did mkdir rec1 and then as the messages queued up in the receive directory I cp *.* rec1
    2. I used wingrep to grep through the messages to find the sender, to ensure we captured the problem message. Once we confirmed we had the broken message we re-enabled the receive threads (rt).
  5. re-enabling the incoming mail
    1. vi /opt/novell/groupwise/agents/share/gwia.cfg | change rt 0 to rt 4 </b> | shift : | wq
    2. /etc/init.d/grpwise stop
    3. /etc/init.d/grpwise start
    4. send mail incoming to verify incoming is now working again. You should also see the receive directory start to be empty.
[edit]

Labbing with the trapped message

Now that you have the "bad message" you can feed it to your lab system without impacting the production system.

Open the bad message with a text editor and change the TO fields to match your test system.

Mine was (lets dream something up). minime@novellrocks.com
So, I replaced the customers TO to mine. Then I put this in my gwia receive directory. Guess what, it failed. So, I applied all the latest beta code and it still failed. See my wiki on applying GW patches on Linux .

Then, I made a copy of the bad message and started removing lines and seeing if it would process (watching POA logs or login).

Without too much trouble, I found the two lines that were causing some problems.

I used "Beyond Compare" to view the original bad message and my copied by message and moved lines over and back and forth until I came up with the right broken lines.

Trial_error1.JPG

You will see the RED part of the message that was causing the problem. We then contacted the sender and asked them if it was easy/difficult to remove this on outgoing. It was easy for them to remove it and then the customer began to receive email from this problem domain!!

Retrieved from "http://wiki.novell.com/index.php/TrappingBadMessagesGWIA"