Skip to content
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

Closed
mc-butler opened this issue Jun 27, 2024 · 8 comments
Closed

Ticket changes notification stopped working #4557

mc-butler opened this issue Jun 27, 2024 · 8 comments
Assignees
Labels
area: adm Administrative tasks prio: medium Has the potential to affect progress

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/4557
Reporter 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?

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 27, 2024 at 16:32 UTC (comment 1)

It's supposed to be working:

Jun 27 16:19:57 midnightcommander postfix/smtp[4943]: D64CE438AC: to=<opty's address>, relay=smtp.osuosl.org[140.211.166.137]:25
, delay=0.34, delays=0.11/0.02/0.07/0.14, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 1B3EC40BCB)

I find it curious, that apparently IPv6 is halfway broken on the VM:

Jun 27 16:19:56 midnightcommander postfix/smtp[4943]: connect to smtp.osuosl.org[2605:bc80:3010::138]:25: Network is unreachable  
Jun 27 16:19:56 midnightcommander postfix/smtp[4943]: connect to smtp.osuosl.org[2605:bc80:3010::133]:25: Network is unreachable  
Jun 27 16:19:56 midnightcommander postfix/smtp[4943]: connect to smtp.osuosl.org[2605:bc80:3010::137]:25: Network is unreachable  
Jun 27 16:19:56 midnightcommander postfix/smtp[4943]: connect to smtp.osuosl.org[2605:bc80:3010::136]:25: Network is unreachable

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.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 27, 2024 at 16:41 UTC (comment 2)

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...

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 27, 2024 at 20:07 UTC (comment 3)

OSU OSL says IPv6 is not supported, so I was right to disable it. The mail problem is still under investigation.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 28, 2024 at 8:24 UTC (comment 4)

  • 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.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 28, 2024 at 8:49 UTC (comment 5)

  • Status changed from accepted to testing
  • Resolution set to fixed

Notifications are now delivered.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 28, 2024 at 8:50 UTC (comment 6)

  • Status changed from testing to closed

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 28, 2024 at 9:12 UTC (comment 7)

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...

@mc-butler
Copy link
Author

Changed by opty (opty77@….com) on Jun 28, 2024 at 10:10 UTC (comment 8)

I can confirm that notification works again, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: adm Administrative tasks prio: medium Has the potential to affect progress
Development

No branches or pull requests

2 participants