-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ticket changes notification stopped working #4557
Comments
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. |
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... |
OSU OSL says IPv6 is not supported, so I was right to disable it. The mail problem is still under investigation. |
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. |
Notifications are now delivered. |
|
Oh man, another server migration has broken our FTP mirrors without anyone noticing sometime on June, 22. I'm hoping to have repaired that now... |
I can confirm that notification works again, thanks! |
Important
This issue was migrated from Trac:
opty
(opty77@….com)It seems that ticket changes notification stopped working some time ago.
Maybe just for some Gmail users or I missed a change?
The text was updated successfully, but these errors were encountered: