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

ways to debug why email is not received #90

Open
a18-kaushik opened this issue Oct 17, 2023 · 6 comments
Open

ways to debug why email is not received #90

a18-kaushik opened this issue Oct 17, 2023 · 6 comments

Comments

@a18-kaushik
Copy link

Hi, I've configure the server as follows:

  • ubuntu22.04 ec2 on aws
  • started service on port 3000 and smtp port is 25, allowed origins also configured
  • configured MX and A records for domain
  • api server is working fine
  • opened all ports on ec2 firewall

still not able to get email on mailbox , please suggest things i can check for.

@gcleaves
Copy link
Contributor

I'd start by telnetting to the SMTP port and check whether that works: https://www.comparitech.com/net-admin/telnet-smtp-test/ .

@a18-kaushik
Copy link
Author

a18-kaushik commented Oct 17, 2023

it says
Could not open connection to the host, on port 25: Connect failed

but there is no service running on port 25 when i checked with netstat

@a18-kaushik
Copy link
Author

a18-kaushik commented Oct 18, 2023

@gcleaves I'm able to open 2525 port for smtp and it shows as listening in netstat

question : do i have to make any more changes to receive mail on 2525 as smtp port in application?

@a18-kaushik
Copy link
Author

i think 25 port is necessary to receive incoming requests from any other mail server like gmail and i have no control over that
it's strange that running ahem on smtp port 25 doesn't show it as listening in netstat command

@gcleaves
Copy link
Contributor

Try netstat at various points in the network. I imagine port 25 IS listening on the container. Can you access port 25 from the docker host? At what point is port 25 blocked? That's where you have a firewall/network issue.

Some low cost hosting providers might block port 25 to prevent misconfigured mail servers from acting a spam relays, but I wouldn't expect Amazon to block it.

Does this help? https://repost.aws/knowledge-center/ec2-port-25-throttle

@a18-kaushik
Copy link
Author

thanks for the reply, i tried with docker on an alternate mail server and it works for the meanwhile

also for your above reply there is no container, i'm running directly on an ec2 by ssh into it
and the provided links states there are restrictions on port 25 for outgoing but here incoming is blocked as it's not listening on port 25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants