No worries at all Mike, there isnt really anything you can do for me. The best way to return the favour is to learn from what I have taught you and repeat it to someone who is asking if you ever have the opportunity. That is how these forums work.

In regards to writing another trigger for the task side of things. Personally, I think that you should just add it to your existing trigger.

Triggers can impact on each other and there is no real point in adding two different triggers that are triggered by the same thing on two different objects.

i am not completely sure what you mean by adding a trigger to ask, but:

If you are refering to adding information to the task when the criteria sets the lead status to "Contacted", then adding a completely new trigger would probably only complicate things. As you already have the event and the record queried within your current trigger you can do something like this:

Step 1: add custom boolean field to activity called something like: ContactStatusSet__c or whatever field you would like to use for stating that the lead status was altered through the trigger.

Step 2. Introduce a list of Tasks at the top of the page  List<Task> tasksToUpdate = new List<Task>();

Step 3: Change this line:
 

if(Email.Subject.Contains('&Message Sent:')){

//Action to be taken

    L.Status = 'Contacted';

//Add leads which need to be updated into one list to avoid governor limits
    LeadsToUpdate.add(L);

    }

to this line:
 

if(Email.Subject.Contains('&Message Sent:')){

//Action to be taken

    L.Status = 'Contacted';

//Add leads which need to be updated into one list to avoid governor limits
    LeadsToUpdate.add(L);
Email.ContactStatusSet__c = true;
tasksToUpdate.add(Email);

    }

Step 4: Add this line at the end:

if(tasksToUpdate.size() > 0) {

    update LeadsToUpdate;
    }

Finally:

It is best to keep all trigger functions to do with an object under one trigger. 

E.G. Every Account trigger in the one super account trigger. This is to ensure that you control the order of which processes are executed.

You can do so and keep it ordered through:

trigger LeadTrigger on Lead (before update,before insert, before delete, after update, after insert, after delete) {

if(trigger.isbefore){
if(trigger.isinsert){

}else if(trigger.isupdate){

}
}
if(trigger.isafter){
if(trigger.isinsert){

}else if(trigger.isupdate){

}
}

}

All logic that occurs before insert, after insert, etc You can decide where and when it is exactly executed.

This way whenever a DML function is executed, you can catch it and perform neccessary work on it.

Hope this helps, all the best and goodluck