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.

Sign up for GitHub

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

Jump to bottom

Found NATIPs conf option, but don't think its taking effect. #259

Closed
mocallins opened this issue Dec 4, 2024 · 9 comments
Closed

Found NATIPs conf option, but don't think its taking effect. #259

mocallins opened this issue Dec 4, 2024 · 9 comments

Comments

@mocallins
Copy link

Running mox in a homelab environment, natted.
Is this correct in the email details, trail ?

<html>
<body>
<!--StartFragment-->
10mins 6s ago | 90517ms |   |   |   | dialing smtp server: dial tcp 192.168.0.220:0->67.195.204.77:25: i/o timeout
-- | -- | -- | -- | -- | --


<!--EndFragment-->
</body>
</html>

Seems like it should be the public facing ip address ?
@mjl-
Copy link
Owner

mjl- commented Dec 4, 2024

The NATIPs option only tells mox that it is running in a NAT configuration, and what the actual external IPs are. Mox uses those IPs for its self-checks. It does not influence how outgoing smtp connections are made. So the IPs in the dial error message look reasonable. It's not great that you're seeing a timeout... Hope that doesn't happen for all outgoing connections.

What were you expecting the NATIPs config option to do?

@mocallins
Copy link
Author

The NATIPs option only tells mox that it is running in a NAT configuration, and what the actual external IPs are. Mox uses those IPs for its self-checks. It does not influence how outgoing smtp connections are made. So the IPs in the dial error message look reasonable. It's not great that you're seeing a timeout... Hope that doesn't happen for all outgoing connections.

What were you expecting the NATIPs config option to do?
Just trying to figure out why i cannot get outbound email to work, actually and inbound email as well.

@mjl-
Copy link
Owner

mjl- commented Dec 4, 2024

It looks like outgoing SMTP delivery connections (to port 25) may be blocked. Some ISPs can open up their firewall at request, some don't want you to send email by yourself...

For incoming SMTP, there are various websites out there for testing connectivity to your domain. You can probably get some info from those.

@mocallins
Copy link
Author

Yea i tried DNS Checker, and another 1 that wants to charge for the info, but neither seemed to be of much help.
The free on did provide

Reverse DNS does not match SMTP Banner.

But i couldn't find any further info , on what that means, or how to repair

My ISP is Cox, and i've never seem to got much help from them. To tell you the truth i don't think their very smart about any of this.
They just want you to use what you pay for as run of the mill, and not have to help at all.

@mocallins
Copy link
Author

Would this cause a problem ?

`
IP: 68.12.151.20

Hostname: ip68-12-151-20.ok.ok.cox.net.
`

Even though i'm trying to claim it on my dns ?

@mocallins
Copy link
Author

Hey i ran an nmap scan/probe against my ISP address and it shows oprt 25 open.

[webserver]:</home/pi/> nmap -sV 68.12.151.20
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-06 00:58 CST
Nmap scan report for ip68-12-151-20.ok.ok.cox.net (68.12.151.20)
Host is up (0.014s latency).
Not shown: 997 filtered tcp ports (no-response)
PORT    STATE  SERVICE VERSION
25/tcp  open   smtp
80/tcp  open   http    Apache httpd 2.4.62 ((Raspbian))
161/tcp closed snmp

Any additional ideas ?

@mjl-
Copy link
Owner

mjl- commented Dec 6, 2024

Could you give some more details of the error messages you are seeing? There's not enough to go on now.
Is it incoming and outgoing email that isn't working?
It will help to see logging from mox. You can enable trace logging to get all the protocol details.

FWIW, I cannot connect to 68.12.151.20 on port 25. You may be able to connect from inside your network, but from outside it appears blocked.

@mocallins
Copy link
Author

Yes neither incoming nor outgoing email is occurring.

I will be happy to provide whatever logs you need, just point me in the right direction.

Also here's what i see from telnet to the smtp port.

helo collinsinfotech.com
250-webserver.collinsinfotech.com
250-PIPELINING
250-SIZE 104857600
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-LIMITS RCPTMAX=1000
250 SMTPUTF8

Don't know it helps.

I guess nevermind. it looks as if my isp is actively blocking port 25

Is there anyway of changing the port , although i wouldn't know how the outside world would know to use a different port :(

@mjl-
Copy link
Owner

mjl- commented Dec 7, 2024

Is there anyway of changing the port , although i wouldn't know how the outside world would know to use a different port :(

Indeed that's not possible... It's not very common for ISPs to blocking
incoming SMTP entirely. There's not much harm to do that way. But given the
suspicious DNS behaviour, and the blocking of outgoing SMTP, it doesn't seem
like a good idea to try to host a mail server on that ISP. I would get a
(simple) VPS at a reputable hosting provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mocallins @mjl-