[FIX] mail_tracking: process sent events

Up until now, the `sent` event type was never processed, probably because it "made no sense", as an unsent email would never trigger an event.

However, it makes sense to process it because you may have a local relay that transmits mails over to the mail provider. In those circumstances, you should have 2 "sent" events (one from the relay and another one from the provider).

Also marked some useless parts of code for removal.

@Tecnativa TT32365

Author: Jairo Llopis

mail_tracking/controllers/main.py

@@ -41,6 +41,7 @@ def _request_metadata(self):
             "ua_family": request.user_agent.browser or False,
         }
 
+    # TODO Remove useless controller
     @http.route(
         [
             "/mail/tracking/all/<string:db>",

mail_tracking/models/mail_tracking_email.py

@@ -385,6 +385,7 @@ def event_create(self, event_type, metadata):
                 _logger.debug("Concurrent event '%s' discarded", event_type)
         return event_ids
 
+    # TODO Remove useless method
     @api.model
     def event_process(self, request, post, metadata, event_type=None):
         # Generic event process hook, inherit it and

mail_tracking/models/mail_tracking_event.py

@@ -122,6 +122,10 @@ def _process_bounce(self, tracking_email, metadata, event_type, state):
         )
         return self._process_data(tracking_email, metadata, event_type, state)
 
+    @api.model
+    def process_sent(self, tracking_email, metadata):
+        return self._process_status(tracking_email, metadata, "sent", "sent")
+
     @api.model
     def process_delivered(self, tracking_email, metadata):
         return self._process_status(tracking_email, metadata, "delivered", "delivered")