After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 622432 - Mails to buildmaster@fixed.gnome.org get lost
Mails to buildmaster@fixed.gnome.org get lost
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2010-06-22 20:06 UTC by Frederic Peters
Modified: 2010-09-06 13:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frederic Peters 2010-06-22 20:06:38 UTC
build.gnome.org used to trigger builds automatically, from emails it received by being subscribed to the commits-list@ mailing list; it stopped working a long time ago but forgot acting on this…

Anyway, there is ~buildmaster/.procmailrc on fixed.gnome.org, that should move incoming mails to the correct mailbox, but nothing gets in.

I tried a stupid "mail buildmaster@fixed.gnome.org -s test < /dev/null" and nothing was written to the procmail log file, but also I  didn't receive any bounce.

Could someone look into this? Thanks. (don't hesitate to ping me for more info)
Comment 1 Olav Vitters 2010-06-23 09:28:36 UTC
1st check:

Jun 23 00:00:09 fixed postfix/local[14003]: 8ADC4228053: to=<buildmaster@fixed.gnome.org>, relay=local, delay=0.1, delay s=0.05/0/0/0.04, dsn=5.2.0, status=bounced (cannot append message to file /usr/local/buildmaster/mail: cannot open file: Permission denied)
Comment 2 Olav Vitters 2010-06-23 09:32:02 UTC
Probably SELinux. Disabled that for now, though selinux bits should be fixed.
Comment 3 Olav Vitters 2010-06-23 09:35:53 UTC
+ Resubscribed buildmaster@fixed.gnome.org to commits-list (was unsubscribed due to bounces)
Comment 4 Frederic Peters 2010-06-23 11:18:24 UTC
I don't know if there's a special rule that would allow connections from menubar.gnome.org, but if there's not I just realized it simply wouldn't connect to port 25; on window.gnome.org:

   $ telnet fixed.gnome.org 25
  Trying 209.132.180.166...
  telnet: connect to address 209.132.180.166: Connection refused
Comment 5 Olav Vitters 2010-06-23 11:57:25 UTC
Frederic: That is on purpose. We have a separate backchannel network for all Red Hat servers.

SELinux didn't solve it:
Jun 23 11:46:42 fixed postfix/local[24509]: 9B895228051: to=<buildmaster@fixed.gnome.org>, relay=local, delay=0.08, delays=0.06/0/0/0.02, dsn=5.2.0, status=bounced (cannot append message to file /usr/local/buildmaster/mail: cannot open file: Permission denied)
Comment 6 Olav Vitters 2010-06-23 14:38:41 UTC
Interestingly, it should actually deliver it to procmail. But seems postfix delivers it directly. Not sure why that is.

For the directory, permissions seem to be ok. Assume 'local' delivery agent runs under the postfix user.
Comment 7 Christer Edwards 2010-09-01 20:40:36 UTC
More recent logs show:

Sep  1 18:46:59 fixed postfix/pickup[8329]: 068C3228052: uid=6307 from=<fpeters>
Sep  1 18:46:59 fixed postfix/cleanup[1948]: 068C3228052: message-id=<20100901184659.068C3228052@fixed.gnome.org>
Sep  1 18:46:59 fixed postfix/qmgr[2714]: 068C3228052: from=<fpeters@fixed.gnome.org>, size=15919, nrcpt=1 (queue active)
Sep  1 18:46:59 fixed postfix/local[1954]: 068C3228052: to=<fpeters@fixed.gnome.org>, orig_to=<fpeters>, relay=local, delay=9711, delays=9710/0.07/0/0.12, dsn=5.2.0, status=bounced (can't create user output file. Command output: procmail: Couldn't create "/var/mail/fpeters" )
Sep  1 18:46:59 fixed postfix/cleanup[1948]: 4F5C2228053: message-id=<20100901184659.4F5C2228053@fixed.gnome.org>
Sep  1 18:46:59 fixed postfix/qmgr[2714]: 4F5C2228053: from=<>, size=17780, nrcpt=1 (queue active)
Sep  1 18:46:59 fixed postfix/bounce[1960]: 068C3228052: sender non-delivery notification: 4F5C2228053
Sep  1 18:46:59 fixed postfix/qmgr[2714]: 068C3228052: removed
Sep  1 18:46:59 fixed postfix/local[1954]: 4F5C2228053: to=<fpeters@fixed.gnome.org>, relay=local, delay=0.07, delays=0.04/0/0/0.03, dsn=5.2.0, status=bounced (can't create user output file. Command output: procmail: Couldn't create "/var/mail/fpeters" )
Sep  1 18:46:59 fixed postfix/qmgr[2714]: 4F5C2228053: removed

Looks like procmail is getting it, but can't create the required directory.
Comment 8 Olav Vitters 2010-09-01 20:45:54 UTC
fpeters@fixed is wrong. Should not work.

buildmaster@fixed.gnome.org is where it should be delivered to.
Comment 9 Olav Vitters 2010-09-02 07:31:12 UTC
<cedwards>      well part of it is that buildmaster user is setup with Maildir mail/{new,cur,tmp}, but /etc/aliases was pointing to a file at /usr/local/buildmaster/mail
<cedwards>      appending a trailing slash gets past that
<cedwards>      now its an issue of uid/gid 99 (nobody) writing to those folders.
<cedwards>      Sep  1 21:36:05 fixed postfix/local[22130]: warning: maildir access problem for UID/GID=99/99: create maildir file /usr/local/buildmaster/mail/tmp/1283376965.P22130.fixed.gnome.org: Permission denied
<cedwards>      my brain is a bit mush right now (getting a cold), but I think it's closer than it was if anyone else wants to stab at it.


Good find! buildmaster should NOT be in /etc/aliases (will prevent it from using procmail). Removed it, now it should work again. Re-enabled delivery in commit-list configuration.
Comment 10 Frederic Peters 2010-09-04 07:57:47 UTC
Unfortunately mails are ending up in /var/mail/buildmaster, without going through procmail :/
Comment 11 Christer Edwards 2010-09-06 03:20:40 UTC
/var/mail/buildmaster is now in Maildir/ format, delivery is successful and the previous mbox has been imported.

Can you please update your buildbot configuration to point to this location and let me know if this will be acceptable?
Comment 12 Olav Vitters 2010-09-06 07:23:02 UTC
IMO, we should fix the problem. I think I just broke the procmail filtering.
Comment 13 Frederic Peters 2010-09-06 08:19:06 UTC
I updated the build master configuration to look for mails in /var/mail/buildmaster/ and it works now. Unless you want to keep this open to fix the procmail filtering this issue can be closed.  Thanks.
Comment 14 Christer Edwards 2010-09-06 13:11:14 UTC
In my discussion with Frederic yesterday he stated that he had no real *need* for procmail, that was simply what had been used historically. The real need broke down to: 1) mail being properly delivered 2) delivered mail stored in Maildir/ format.

Those two requirements have been met, so my vote is to close the ticket.