mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 23:15:49 +03:00
[GH-ISSUE #867] SMTP Server Setup for receiving Pings #607
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#607
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @djarbz on GitHub (Jul 27, 2023).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/867
I have been fighting with this all afternoon.
I have email notifications working, but I am unable to receive emails on my instance.
If I Telnet in, I can dump an email, but if I send an email from say my Gmail account, my instance will never receive it.
Actually, in Google Workspace, it will say rejected:
The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 [healthchecks.example.com. <REDACTED IP ADDRESS>: FAILED_PRECONDITION: connect error (111): Connection refused]I know that my service is listening on port 25 and reachable externally, tested via telnet on a remote VPS as my ISP blocks port 25.
@cuu508 commented on GitHub (Jul 31, 2023):
Can you test with a few other mail providers besides Gmail, to see if it's something Gmail-specific?
@djarbz commented on GitHub (Jul 31, 2023):
Gmail is the only service that I have access to the server side logs to.
I did test with my work email and it bounced as well.
@cuu508 commented on GitHub (Jul 31, 2023):
Does sending test email from here work? https://sendtestemail.com/
@djarbz commented on GitHub (Jul 31, 2023):
Unfortunately it did not work.
This tool did work however: https://www.smtper.net/
I filled out the host/port/from/to fields.
@djarbz commented on GitHub (Jul 31, 2023):
In my registrar I do have the following records.
A - example.com --> server IP (ideally I would like this one to go away)
A - healthchecks.example.com --> server IP
MX - healthchecks.example.com --> healthchecks.example.com priority 10
@cuu508 commented on GitHub (Jul 31, 2023):
In https://www.smtper.net/ the default port is 25 – did you leave it as-is, or did you specify a different port?
@djarbz commented on GitHub (Jul 31, 2023):
I did use port 25.
@cuu508 commented on GitHub (Jul 31, 2023):
I'm not sure what to make of it – perhaps the server running your Healthchecks instance has port 25 blocked to/from some destinations but not all?
@djarbz commented on GitHub (Jul 31, 2023):
This is really weird, I just got a bunch of emails to come through on my test check.
Thing is, I didn't change anything...
@cuu508 commented on GitHub (Jul 31, 2023):
Another guess – perhaps it's something to do with DNS caching?
Say, if you were changing the A and MX records for healthchecks.example.org, perhaps the old values were still in some DNS resolver caches. Once the cached values expired, the deferred emails could come through?
@djarbz commented on GitHub (Jul 31, 2023):
I haven't touched them since Friday.
@cuu508 commented on GitHub (Jul 31, 2023):
Well then maybe that's not it (assuming short TTLs before the changes).
In any case, it's not yet clear to me there's anything to fix for me here. If you manage to isolate the problem to something in the Healthchecks codebase, I'm all ears.
@djarbz commented on GitHub (Jul 31, 2023):
Yeah, I think I can close this out. I just wish I knew what the issue was.