Hi there!
sorry for the off-topic thread, I’m writing about the list itself.
At work we built a feature in a mail client that deals with newsletters subscriptions.
Subscriptions are identified by messages having a List-ID or List-Unsubscribe header. Then, to differentiate mails being newsletters or list discussions, one heuristic is to look at the Precedence
header, it can be bulk
for mass mailing (so newsletters) or list
(discussions). And when working on that I noticed that PHP lists were wrongly sent the mails with Precedence: bulk
. Is this something that could be fixed?
It’s not a big deal since I’ve since added another heuristic that works woth the PHP mailing lists (classify subscription as discussion is it has a List-Post
header) but wanted to let you know, it may be useful for other clients if / when they implement features using those headers.
Also, the List-ID is not properly formatted, it’s supposed to be wrapped in angle brackets but it’s not, so instead of List-Id: [internals.lists.php.net](http://internals.lists.php.net)
it should be List-Id: <[internals.lists.php.net](http://internals.lists.php.net)
> or even List-Id: PHP Internals list <[internals.lists.php.net](http://internals.lists.php.net)> to give it a human friendly name. One downside of fixing it though is that it may break automatic filtering rules of people matching exactly
List-Id: internals.lists.php.net.
···
regards,
Mathieu Rochette