Opened on 06/22/2015 at 07:28:32 AM
Closed on 09/07/2015 at 07:59:25 AM
#2703 closed defect (fixed)
Rietveld fails to send mails since June 17/18th
| Reported by: | matze | Assignee: | matze |
|---|---|---|---|
| Priority: | P1 | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | Ollie, fhd, fred | Blocked By: | |
| Blocking: | Platform: | Unknown | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Many, if not all, mails from codereview.adblockplus.org are not received any more. According to the provider logs, the last ones delivered successfully where sent June 17th. The server logs indicate issues since June 18th:
Jun 18 09:22:20 codereview1 postfix/qmgr[8347]: 381F41880BD9: from=<m...@codereview1.adblockplus.org>, size=553, nrcpt=1 (queue active) Jun 18 09:22:20 codereview1 postfix/smtp[17715]: connect to codereview1.adblockplus.org[213.239.213.135]:25: Connection refused Jun 18 09:22:20 codereview1 postfix/smtp[17715]: connect to codereview1.adblockplus.org[2a01:4f8:a0:83ad::2]:25: Connection refused Jun 18 09:22:20 codereview1 postfix/smtp[17715]: 381F41880BD9: to=<r...@codereview1.adblockplus.org>, orig_to=<root>, relay=none, delay=286195, delays=286194/0.21/0.06/0, dsn=4.4.1, status=deferred (connect to codereview1.adblockplus.org[2a01:4f8:a0:83ad::2]:25: Connection refused)
No idea why the daemon attempts to connect to itself..
Attachments (0)
Change History (4)
comment:1 Changed on 06/22/2015 at 07:30:12 AM by matze
- Component changed from Unknown to Infrastructure
- Priority changed from Unknown to P1
comment:2 Changed on 06/22/2015 at 12:54:06 PM by matze
comment:3 Changed on 06/22/2015 at 12:56:10 PM by matze
- Blocked By 2683 added
comment:4 Changed on 09/07/2015 at 07:59:25 AM by matze
- Blocked By 2683 removed
- Resolution set to fixed
- Status changed from new to closed
- Tester set to Unknown
No similar issues in the last weeks, seems to work as expected.
Note: See
TracTickets for help on using
tickets.
It looks like the logs quoted above are the result of bounced mails that came back. I've postsuper -d ALL deferred them. It also seems like the actual issue is (or was) #2683, leading to a ton of bounces for reply@codereview-hr.appspotmail.com and thus triggering some blocking throttle mid-way.