Open JoeCohen opened 3 months ago
This may have functioned properly as of 2024-06-05 (which should help isolate when the bug occured). See attached. Gmail - Re A new bug.pdf
These emails are being created, but not sent. Example, from Production log/email-debug.log:
...
2024-07-28 20:25:27 -0400 SAVE QueuedEmail::CommentAdd from=D.TempestThomas to=Huafang comment=200779
2024-07-28 20:25:27 -0400 SAVE QueuedEmail::CommentAdd from=D.TempestThomas to=alicesamanita comment=200779
2024-07-28 20:25:27 -0400 SAVE QueuedEmail::CommentAdd from=D.TempestThomas to=dolomite747 comment=200779
2024-07-28 20:25:27 -0400 SAVE QueuedEmail::CommentAdd from=D.TempestThomas to=Kebes comment=200779
...
2024-07-28 20:30:39 -0400 MAIL comment from=38275 to=165687 object=observation-554261
2024-07-28 20:30:40 -0400 SEND QueuedEmail::CommentAdd from=D.TempestThomas to=Mathewbub comment=200779
2024-07-28 20:30:40 -0400 MAIL comment from=38275 to=165725 object=observation-554261
2024-07-28 20:30:40 -0400 SEND QueuedEmail::CommentAdd from=D.TempestThomas to=MeganEpife comment=200779
2024-07-28 20:30:40 -0400 MAIL comment from=38275 to=165928 object=observation-554261
2024-07-28 20:30:41 -0400 SEND QueuedEmail::CommentAdd from=D.TempestThomas to=Robertoamurb comment=200779
2024-07-28 20:30:41 -0400 MAIL comment from=38275 to=165994 object=observation-554261
They are not stuck in the email queue. Production:
irb(main):001> QueuedEmail.count
=> 66
@pellaea, @nimmolo, @mo-nathan: Any ideas about how to debug this, or even figure out when things broke? (I can't figure out how to test whether a particular commit was working, as I think mail is never actually sent in development mode. Am I wrong?)
Maybe try responding to your own comments with a second account, or ping me and i'll respond.
I suspect the problem is in email, e.g. a spam filter external to MO.
@nimmolo: Thanks for the suggestion. I have tried that, but will try it again with addresses at different email providers.
Tried again. Left comment and two responses on your Obs https://mushroomobserver.org/122027. Original comment from me. 1st response from user Oregon Mycological Society. I did not get a response to this. (I did check spam & trash.0 2nd response from me. Oregon Mycological Society (with non-Gmail email provider) didn't get a response to the above.
nimmo Jul 29, 2024, 10:28 PM (8 hours ago) Joe - This may possibly have to do with our standing re: suspected spammer lists. There's a way to check if we're on a blocklist, and a way to get cleared, but it takes time.
@nimmolo: Re standing on suspected spammer lists:
It sounds like you know more than I remember about it.
I don’t imagine there’s an issue with the test server, but it’s possible. According to the DMARC report, the problems are reported by this Google IP address
mushroomobserver.org 209.85.220.41 mail-sor-f41.google.com The IP address associated with test.mushroomobserver.org is : 138.197.41.143
On Jul 30, 2024, at 6:54 AM, Joseph D. Cohen @.***> wrote:
@nimmolo https://github.com/nimmolo: Re standing on suspected spammer lists:
If you can point me in the right direction(s), I'll try to get some more info. I checked a recent DMARC report from Google. Perhaps it indicates problems with DKIM. See https://us.dmarcian.com/dmarc-xml/details/LzAByfGq0o2St1rH/ https://us.dmarcian.com/dmarc-xml/details/LzAByfGq0o2St1rH/. I don't know what that means. Is there an issue with the test server? I also checked Debouncer to see if mushroomobserver.org was on a blacklist. I didn't see any problems. — Reply to this email directly, view it on GitHub https://github.com/MushroomObserver/mushroom-observer/issues/2263#issuecomment-2258412174, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO3TP4ZACZSXC5H6UT6JNTZO6LKHAVCNFSM6AAAAABLUFQM3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJYGQYTEMJXGQ. You are receiving this because you were mentioned.
~MO fails to email User when second User posts a Comment in response to (first user's) Comment.~ Users do not receive "response to your comment" emails; emails created when a second User posts a Comment in response to (first user's) Comment. (These are different from emails created when another user posts a Comment on your Observation.)