Timeline for Sending mail using terminal
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12 at 1:51 | comment | added | Dominic108 | Actually, the reason why I succeeded with my own server is that I had an IP tables rule to redirect outgoing communication toward my server at port 25 to another port to which it listen. So, testing with Google smtp server might be a robust approach. | |
| Feb 9 at 18:55 | comment | added | Dominic108 | This is not reliable. It failed with me, but I could use port 25 to connect with another (non local) server that I maintain. If you maintain your own server and you know it listen and respond to port 25, then it provides an additional check. The difficulty is that it is always possible that the failure is not due to the ISP. For example, perhaps, google rejected my IP. | |
| Jul 5, 2021 at 18:56 | vote | accept | cdummie | ||
| Jun 27, 2021 at 16:59 | comment | added | Stewart |
nmap -sT <your-public-ip-or-domain> checks if your machine is listening on port 25 (inbound). i.e: It's checking port 25 inbound only. This affects your ability to receive emails, but does not tell you whether you can send emails (port 25 outbound). Furthermore: nmap -sT localhost only tells you if your machine is listening on those ports on the local network. It does not test if your ISP, or your router's firewall is blocking anything. If the telnet connection is timed out, then port 25 (outbound) is blocked by your ISP.
|
|
| Jun 27, 2021 at 14:08 | comment | added | cdummie | Thanks for your answer, i tried telnet as you suggested but it turns out that connection is timed out, however, i am not sure if that means that port 25 is blocked because when i run nmap -sT localhost it says that smtp service is open (tcp port 25). | |
| Jun 26, 2021 at 8:19 | history | answered | Stewart | CC BY-SA 4.0 |