Closed Bug 467190 Opened 17 years ago Closed 17 years ago

boxset not reporting to tinderbox (again)

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alqahira, Assigned: samuel.sidler+old)

References

()

Details

boxset started a build this morning about about 2:50am MozTime and had been yellow ever since, prior to falling off the waterfall. It's still reporting to the graph server/my perf dashboard, so it sounds like email is fouled up again :(
Sam says boxset is sending out mail (and I assume not getting any bounce/blocked messages from any ISP); does this make this a problem on MoCo's end?
IT says this might correspond to a change they made affecting mail. -> Server Ops
Assignee: samuel.sidler → server-ops
Component: General → Server Operations
Product: Camino → mozilla.org
QA Contact: general → mrz
Version: unspecified → other
Dec 9 23:09:49 dm-mail01 postfix/smtpd[21228]: NOQUEUE: reject: RCPT from cl34.gs02.gridserver.com[64.13.232.43]: 450 4.1.8 <cltbld@boxset.ss.gotdns.org>: Sender address rejected: Domain not found; from=<cltbld@boxset.ss.gotdns.org> to=<tinderbox-daemon@tinderbox.mozilla.org> proto=ESMTP helo=<cl34.gs02.gridserver.com> Your domain doesn't exist. Apparently it used to.
(In reply to comment #2) > IT says this might correspond to a change they made affecting mail. I'd be curious to know who said this. I'm not aware of any email changes in that time frame.
Assignee: server-ops → nobody
Component: Server Operations → General
Product: mozilla.org → Camino
QA Contact: mrz → general
Version: other → unspecified
I mentioned that the timeframe Sam mentioned was close to the timeframe when you made your postini/postfix changed. Apparently it's not related to that.
oh, yeah. tinderbox.mozilla.org doesn't go through them though, so yeah, unrelated.
Found the problem and fixed it. Sorry to bother you guys!
Assignee: nobody → samuel.sidler
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.