“The Da Lakhvi Code” continues ……

In some emails, -5 or -7 was written at the end of the code. That meant that while decoding, the reader needed to count back those many letters. For instance, the email dated 17 February read:
‘Dear Rashid, please make a new email ID. Then mail me on my present ID 002 .1 .004 .7 .09 .7 .07 .7 .000 – 7’.
Using this method, 002 was X, but if we counted back seven letters (as indicated by ‘-7’ at the end of the message), it became P. The deciphered code therefore read ‘purana makan’. It was not surprising, therefore, that emails sent after 17 February originated from
puranamakan@hotmail.com. The matching of this email ID confirmed that this indeed was the correct way to decode the messages.
While both schoolmates sat outside my office waiting for their turn to see me, Pramod once again made sure that the decoding formula worked out by Vivek was in order. When Pramod walked into my office he looked triumphant and relaxed. He explained the decoding methodology to me, and we were finally able to make sense of the coded emails. We then realized that India Gate was going to be the target of an attack, as mentioned in code in the email dated 15 February. The coded message, as stated earlier, was ‘.05 .000 .00 .05.7.03 .7 .0 .4 -7’. When decoded, it read ‘India Gatx’. The last letter was a typo and ‘x’ was meant to be ‘e’.
Therefore, the date for the terror attack was fixed as 25 February and the target was India Gate.
The email dated 18 February read ‘Chacha bird will come two days before time Zak’.

To be Continued ……….