Your message dated Fri, 4 Dec 2015 23:01:22 +0100
with message-id <20151204220122.ga16...@home.ouaza.com>
and subject line Re: Bug#754913: tracker.debian.org: Overhaul of incoming mail
handling
has caused the Debian Bug report #754913,
regarding tracker.debian.org: Overhaul of incoming mail handling
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
754913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: important
I want to redesign the way we handle incoming mails to fix a few
shortcomings:
1/ We currently use different email addresses to forward email to
subscribers (<pkg>@tracker.debian.org) and to collect "news" which
will be displayed on the web (_a...@tracker.debian.org).
There's no good reason for this separation because the latter
is really a subset of the former.
2/ We have to accept all possible emails because our scheme relies on
<sourcepackage>@tracker.debian.org. It would be better to use a single
email (eg dispa...@tracker.debian.org) to collect everything and then
rely on headers and standard "user expansion" (eg
dispatch+<pkg>_<keyword>@tracker.debian.org) to differentiate between
source packages.
3/ The current naming scheme involves theoretical namespace conflicts
between cont...@tracker.debian.org (the bot) and the email associated
to a "control" package (if it existed) and makes it difficult to
add supplementary email namespaces inside @tracker.debian.org... and I
might want (at some point) to add new email addresses for teams
and/or for use in Maintainer fields (think of
http://dep.debian.net/deps/dep2/)
My plan is thus to create a new set of MailProcessing classes whose job
is to analyze incoming emails and decide what to do with them. It would
build on the current plugin mechanism so that each django app can effectively
extend/replace the default rules with its own set of classification rules.
Mails that do not mach any rules are archived in a mailbox for inspection,
just in case.
In conjunction with #754745, this "mail processing" would happen in real
time on new mails added to a single Maildir (where the single
incoming email delivers the mails).
I submit this to share my plan and to invite interested contributors to
review this idea and possibly share their feedback.
Cheers,
--- End Message ---
--- Begin Message ---
On Tue, 15 Jul 2014, Raphaël Hertzog wrote:
> I want to redesign the way we handle incoming mails to fix a few
> shortcomings:
So I implemented something like this today, each vendor can provide
a "classify_message()" function that does return a (package, keyword)
tuple and can do any processing (like storing news) on the analyzed
messages.
I modified the Debian vendor to work like that to store the news.
So if you notice weird stuff with missing news, news appearing twice,
… let me know.
> 1/ We currently use different email addresses to forward email to
> subscribers (<pkg>@tracker.debian.org) and to collect "news" which
> will be displayed on the web (_a...@tracker.debian.org).
> There's no good reason for this separation because the latter
> is really a subset of the former.
Since tracker.debian.org now extracts the news from the usual mails I
stopped the forwarding of mails from the old PTS to
_a...@tracker.debian.org.
> 2/ We have to accept all possible emails because our scheme relies on
> <sourcepackage>@tracker.debian.org. It would be better to use a single
> email (eg dispa...@tracker.debian.org) to collect everything and then
> rely on headers and standard "user expansion" (eg
> dispatch+<pkg>_<keyword>@tracker.debian.org) to differentiate between
> source packages.
While tracker.debian.org still currently accepts f...@tracker.debian.org,
the old PTS now forwards all mails to dispatch+...@tracker.debian.org.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
