Nirbheek applied for gnome foundation membership and put me up as a voucher. I didn't receive the e-mail consequently sent to my leio at gentoo.org address, while the other vouchers got it to their personal addresses. After tracking it, it was received fine by me when they sent it directly to leio at dustbite dot net, instead of my gentoo.org alias. Please investigate if something is going on with the forwarding alias. On the other hand, I'm getting gnome bugzilla and some mailing list mail forwarded fine, only problems with membership-applications.
Created attachment 262259 [details] Mail headers of the missing mail as provided by the sender
Created attachment 262261 [details] Mail headers from the successfully received direct mail when by-passing gentoo alias The mail headers as seen in my INBOX from the mail re-sent directly to my inbox address - where gentoo dot org alias is supposed to forward. Only thing I can think of is Precedence: bulk header
We are delivering mail from gnome.org. Example: oodpecker mail # grep 71DF71B425A smtp.log.1 Feb 11 15:26:38 woodpecker postfix/smtpd[3731]: 71DF71B425A: client=menubar.gnome.org[209.132.180.169] Feb 11 15:26:38 woodpecker postfix/smtpd[3731]: 71DF71B425A: filter: RCPT from menubar.gnome.org[209.132.180.169]: <menubar.gnome.org[209.132.180.169]>: Client host triggers FILTER smtp-amavis:[127.0.0.1]:10024; from=<ftp-release-list-bounces@gnome.org> to=<remi@gentoo.org> proto=ESMTP helo=<menubar.gnome.org> Feb 11 15:26:38 woodpecker postfix/cleanup[3813]: 71DF71B425A: message-id=<20110211152626.9CE282384FC@window.gnome.org> Feb 11 15:26:38 woodpecker postfix/qmgr[2631]: 71DF71B425A: from=<ftp-release-list-bounces@gnome.org>, size=3531, nrcpt=2 (queue active) Feb 11 15:26:45 woodpecker postfix/smtp[2671]: 71DF71B425A: to=<eva@gentoo.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.5, delays=0.68/0.02/0.01/6.8, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=04201-01, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as AACBD1B400F) Feb 11 15:26:45 woodpecker postfix/smtp[2671]: 71DF71B425A: to=<remi@gentoo.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.5, delays=0.68/0.02/0.01/6.8, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=04201-01, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as AACBD1B400F) Feb 11 15:26:45 woodpecker postfix/qmgr[2631]: 71DF71B425A: removed woodpecker mail # grep AACBD1B400F smtp.log.1 Feb 11 15:26:45 woodpecker postfix/smtpd[2647]: AACBD1B400F: client=localhost[127.0.0.1] Feb 11 15:26:45 woodpecker postfix/cleanup[3026]: AACBD1B400F: message-id=<20110211152626.9CE282384FC@window.gnome.org> Feb 11 15:26:45 woodpecker postfix/qmgr[2631]: AACBD1B400F: from=<ftp-release-list-bounces@gnome.org>, size=3853, nrcpt=2 (queue active) Feb 11 15:26:45 woodpecker postfix/smtp[2671]: 71DF71B425A: to=<eva@gentoo.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.5, delays=0.68/0.02/0.01/6.8, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=04201-01, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as AACBD1B400F) Feb 11 15:26:45 woodpecker postfix/smtp[2671]: 71DF71B425A: to=<remi@gentoo.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.5, delays=0.68/0.02/0.01/6.8, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=04201-01, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as AACBD1B400F) Feb 11 15:26:46 woodpecker postfix/local[2698]: AACBD1B400F: to=<eva@gentoo.org>, relay=local, delay=0.6, delays=0.12/0/0/0.48, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail) Feb 11 15:26:47 woodpecker postfix/local[3824]: AACBD1B400F: to=<remi@gentoo.org>, relay=local, delay=2, delays=0.12/0/0/1.9, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail) Feb 11 15:26:47 woodpecker postfix/qmgr[2631]: AACBD1B400F: removed
Return-Path: <apache@gnome.org> This address is fails SAV. host mail.gnome.org[209.132.180.169] said: 554 5.7.1 <apache@gnome.org>: Recipient address rejected: Spammer go away I've whitelisted it for now.
Can someone help provide a technical blurb that we can give to GNOME infra team, so that they can fix the underlying issue?
Their Return-Path/MAIL FROM envelope on those outbound mails is not a valid mail destination. This causes SAV to fail it. Return-Path must be a valid address for bounces to get delivered.
