= phenomenon = Last night I updated and built postgresql and postgresql-jdbc in master and f16 branches. I got the expected emails about the four git commits. I did not get email for the lookaside-cache uploads, nor for the completed koji runs, nor for the submitted bodhi tickets. Something's rotten in the state of Denmark.
= reason =
= recommendation =
The emails appear to have sent fine. I see the lookaside uploads on the scm list and in the logs.
Sep 12 06:48:10 bastion03 postfix/smtp[20796]: E8426C0C3A: to=tgl@redhat.com, orig_to=postgresql-jdbc-owner@fedoraproject.org, relay=ext-mx.corp.redhat.com[10.4.123.10]:25, delay=3.7, delays=0.02/0/0.04/3.7, dsn=2.0.0, status=sent (250 2.0.0 p8C6oCmC021976 Message accepted for delivery)
Can you double check any spam folders or filters?
Replying to [comment:1 kevin]:
Ah, sorry, should have thought to check that myself. The logs show that my spam filters are bouncing these for lack of a Message-ID --- specifically, the message ID appears to be getting assigned at mx1.redhat.com and not by the sending machine, which is a violation of relevant RFCs as well as a common spoor of crappy spam engines. That's never happened before and clearly indicates some recent change in the buildsystem mail infrastructure. Please fix it.
On closer inspection, all the dropped messages included this header:
X-RedHat-NoId: 10.5.126.12 sent message with No ID
so you may have just one misconfigured machine.
Yep. I think I have this fixed. ;)
We put in place a new bastion host and new postfix on rhel6 doesn't rewrite headers under the same conditions. :(
Can you see if this is fixed from your view? please reopen if you see any further issues.
Replying to [comment:4 kevin]:
Yes, I just got a few koji messages and they were marked with message-IDs assigned by bastion03.phx2.fedoraproject.org. I still find it odd that they're not assigned by the originating machine, but if you're satisfied with doing it at the bastion, it's OK with me.
Login to comment on this ticket.