Ticket #4557 (closed defect: fixed)
Ticket changes notification stopped working
Reported by: | opty | Owned by: | zaytsev |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | adm | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Branch state: | no branch | Votes for changeset: |
Description
It seems that ticket changes notification stopped working some time ago.
Maybe just for some Gmail users or I missed a change?
Change History
comment:2 Changed 4 months ago by zaytsev
Hmmm, changing priority didn't help, so I've disabled IPv6 altogether and rebooted. I wonder if this will bring anything. Also looked as the bugs list:
https://groups.google.com/g/mc-bugs
It seems that the last messages are from 2023, but Postfix is sending stuff to the upstream SMTP. So I'm wondering whether OSU OSL has done something to block the mail. I guess I have no other choice but to ask them...
comment:3 Changed 4 months ago by zaytsev
OSU OSL says IPv6 is not supported, so I was right to disable it. The mail problem is still under investigation.
comment:4 Changed 4 months ago by zaytsev
- Owner set to zaytsev
- Status changed from new to accepted
Apparently it problems started when Google decided to enforce at least SPF compliance and our records were never fully up to date. I hope that the issue will be resolved now that I've corrected the records.
comment:5 Changed 4 months ago by zaytsev
- Status changed from accepted to testing
- Resolution set to fixed
Notifications are now delivered.
It's supposed to be working:
I find it curious, that apparently IPv6 is halfway broken on the VM:
Resolution seems to be working, but networking doesn't o_O I wonder if it's a host or guest configuration issue. Anyways, reprioritized IPv4 via gai.conf (didn't even know such a thing existed before!), which seems like the easiest solution for now, rather than investing time and effort in trying to find out what is actually going on - and wondering if this solve the slow posting issue.