[Teammetrics-discuss] Commitstat using key authentication?

[Sukhbir Singh]

> Considering your last mail I think such mails should go straight to the
> listspam table (instead of just ignoringt it completely).

We already do that :)

In liststat.py, in the loop which iterates over the messages, we do a
`continue` or a skip only in the cases of:

    Line 192 - 'From' header is empty
    Line 247, 252 - 'Date' header cannot be parsed
    Line 288 - Unable to save to save the data to the database
(exception is never raised)
    Lines 307 - Payload is invalid (broken)
    Lines 351 - Message-ID already exists

For all cases above, it doesn't make sense to continue parsing the
message (please correct me if I am wrong). So, for all other cases
like encoding/ decoding errors, the message goes through our spam
'filter' instead of being ignored completely.

I am just waiting to test this tomorrow with a non-English list (had
to delay due to scheduled power cut) to see how well it goes and then
we will finalize this.