The short version is: sobonito.com and targetmatch.com are known spammers. They are currently hosted by some ISP that uses above.net for backbone service. Neither said ISP nor above.net have satisfactorily taken action against the spammers (according to SPEWS), so the blocklisting against those spammers has been promoted to "level 1", which means the entire netblock of the backbone provider (above.net) is now blacklisted. mozilla.org's upstream provider is meer.net. meer.net uses above.net as a backbone provider. Which places us inside of the above-mentioned level 1 netblock. This blocklisting has been in place since at least September, however there seem to be an increasing number of Bugzilla users complaining about it recently.
I suspect email@example.com would like to be cc'ed on this bug (He is having his email blocked by zoneedit which uses SPEWS)
Reassigning to default owner/qa on endico's open bugs so I don't have to watch her to get mail on them.
Assignee: endico → myk
QA Contact: myk → justdave
We will shortly have two separate /27 address spaces at our disposal, and the new one is not listed in SPEWS. :) The obvious thing to do is relocate our mail services to a server residing in this new address space at the OSUOSL colo, once it's set up.
Assignee: myk → justdave
QA Contact: justdave → myk
Depends on: 215282
Priority: -- → P4
This is a mass-reassign of bugs that I'm not actively working on right at this moment to the default component owner, since we now have a larger IT staff than just me. These bugs will be getting redistributed to other sysadmins as sysadmin time becomes available.
Assignee: justdave → server-ops
Priority: P4 → --
Justin is now the QA for this component.
QA Contact: myk → justin
-> default assignee
Assignee: server-ops → nobody
Our mail server moved to a new colo a month or so ago, and our new netblock is not in the SPEWS list. Resolved by changing providers :)
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.