On Fri 22 May 2009, Stephen Gran wrote:
So I've looked through a few weeks of mail logs to packages.debian.org,
and it looks like it collects some useful mail from automated scripts
on various debian.org machines (primarily ries), and about 1000 spams a
day from elsewhere. I haven't done an
On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote:
Hello all,
So I've looked through a few weeks of mail logs to packages.debian.org,
and it looks like it collects some useful mail from automated scripts
on various debian.org machines (primarily ries), and about 1000 spams a
day
On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote:
If this is actually the case, I'd like to close the domain down to only
accept mail from other debian.org machines. If it's not, I'd like to work
with people who do use it to either make it possible to send their mail
from
On Saturday 23 May 2009, Artur R. Czechowski wrote:
What about requiring a GPG signed email by key in developers or
maintainers keyring?
As others have already mentioned, the addresses are also intended as
contact point for upstream developers and users, i.e. people who don't
have such a key.
Stephen Gran wrote:
It sounds like the service should probably stay open. I would have been
happy to restrict something that is only a spam attractor, but if it's
more than that, than I'm happy people find it a useful service. If the
teams who do use it think it can still be useful and be
Stephen Gran wrote:
This one time, at band camp, Jonathan Wiltshire said:
The debian-l10n-english team, and perhaps others, use this domain to
keep the maintainer in the loop during Smith English-language reviews
and the subsequent translations.
This one time, at band camp, Adeodato Simó
Stephen Gran sg...@debian.org wrote:
day from elsewhere. I haven't done an exhaustive survey, but it seems
pretty clear so far that the domain does not get any significant amount
of legitimate mail from machines other than the debian.org hosts.
If this is actually the case, I'd like to
I use b...@packages.debian.org to contact the maintainer of blah. I
use this to alert maintainers of reverse build-deps when I do
something drastic to one of the libraries I maintain.
I'm open to other options, of course. What is the recommended
practice for this scenario?
Thanks,
-Steve
8 matches
Mail list logo
