Opened 8 years ago

Closed 8 years ago

#54057 closed defect (fixed)

buildbot emails are not sending

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: admin@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc:
Port:

Description

Emails from the buildbot are not arriving.

I see errors like this in the buildmaster's mail log file (I've replaced @ with XXX): 

Apr 29 00:09:29 build postfix/smtp[89274]: 0CFB4B78CD52: to=<perryXXXpiermont.com>, relay=mail1.piermont.com[166.84.7.14]:25, delay=365836, delays=365835/0.1/0.43/0.15, dsn=4.1.7, status=deferred (host mail1.piermont.com[166.84.7.14] said: 450 4.1.7 <buildbotXXXmacports.org>: Sender address rejected: unverified address: host mail.macports.org[136.243.18.213] said: 550 5.1.1 <buildbotXXXmacports.org>: Recipient address rejected: User unknown in virtual alias table (in reply to RCPT TO command) (in reply to RCPT TO command))

Can we add a virtual alias for "buildbot" to the mail server? If we do that, where, if anywhere, should it forward mail to? Or should we change buildbot to send from a different address? Maybe a generic noreply address? Or should replies go to the dev mailing list, like replies to tickets already do?

Change History (1)

comment:1 Changed 8 years ago by neverpanic (Clemens Lang)

Resolution: → fixed
Status: new → closed

I've added buildbot@ as DISCARD address, just like noreply@ already is. That should fix the issue.

I considered making it an address that will reject all mail like we do for nomaintainer@ and openmaintainer@, but that would probably just trigger the same problem (even though the return code would be 554, not 550).

I think mails sent by the buildbot should have a reply-to header that directs answers to the -dev list.

Note: See TracTickets for help on using tickets.