Mail SMTP Relay - Reverse DNS Question
-
In that case any issue would be from MailChimp, right?
-
@scottalanmiller said:
@Dashrender tons of people can send from home on port 25. It's very common.
Actually, no it is not. Many providers have blocked outbound port 25 for years on their residential services. AT&T implemented the block in like 2004 or 2005.
-
@Sparkum PTR should never be a problem. If you setup an SPF record allowing your IP, assuming you have a static IP, that should handle it.
But if I followed all this right, the entire thing is moot as you are wanting all mail delivered to your holding service and then it will send it on to your house?
That should mean nothing needs to be involved with sending because the mail relay/holder should just be trusted by your local mail server and sending it directly.
-
@JaredBusch said:
@scottalanmiller said:
@Dashrender tons of people can send from home on port 25. It's very common.
Actually, no it is not. Many providers have blocked outbound port 25 for years on their residential services. AT&T implemented the block in like 2004 or 2005.
Many providers have blocked, but many have not. While it is not surprising to be blocked, it is not surprising at all to not be blocked.
-
@scottalanmiller said:
@JaredBusch said:
@scottalanmiller said:
@Dashrender tons of people can send from home on port 25. It's very common.
Actually, no it is not. Many providers have blocked outbound port 25 for years on their residential services. AT&T implemented the block in like 2004 or 2005.
Many providers have blocked, but many have not. While it is not surprising to be blocked, it is not surprising at all to not be blocked.
Only provider I can think of off the top of my head would be Frontier, on their original network. Not the ones they bought up recently, because their networks are still integrated into the rest of the original ones. And I'm not even sure on that, as I don't touch Frontier home circuits often.
Every cable provider from Comcast down to Mediacom block 25. AT&T and Verizon did it years ago. Hell, CenturyLink and Windstream do it. If you got an ISP that opens 25 outbound to the world, it's a very, very, very small minority.
-
I'm on a random cheap connection down here in Texas. Just tested here at the condo and port 25 is definitely open: Xfinity
-
Just tested Time Warner. They are open.
Frontier was open last I knew. Verizon was open last I tested. Optimum was open I am pretty sure. I've heard of people having it closed and know that crappy services like Comcast block it. But I've never to actually be blocked anywhere that I have been.
-
@scottalanmiller said:
Just tested Time Warner. They are open.
Frontier was open last I knew. Verizon was open last I tested. Optimum was open I am pretty sure. I've heard of people having it closed and know that crappy services like Comcast block it. But I've never to actually be blocked anywhere that I have been.
Are you testing business or residential connections? Business connections have not been blocked generally.
-
Residential in all of the above cases. Either my apartment or people's homes.
-
Hey.
Sorry for the delay, Tis the Season eh.
So ya, rDNS didnt matter on the relay, its working perfectly right now.
Thanks all for the tips and tricks,
Now onto my next homelab adventure!
-
@Sparkum said:
Hey.
Sorry for the delay, Tis the Season eh.
So ya, rDNS didnt matter on the relay, its working perfectly right now.
Thanks all for the tips and tricks,
Now onto my next homelab adventure!
What fixed it then?
-
@Dashrender
Nothing reallyrDNS is still failing but the relay is working perfectly.
Simply whitelisted it on the mail server to be safe (but wasnt needed) and mail is flowing perfectly.
I think my random setting changes fixed it and I was simply focusing on the reverse DNS failure
-
@Sparkum said:
@Dashrender
Nothing reallyrDNS is still failing but the relay is working perfectly.
Simply whitelisted it on the mail server to be safe (but wasnt needed) and mail is flowing perfectly.
I think my random setting changes fixed it and I was simply focusing on the reverse DNS failure
Aww.. OK - thanks
-
Whitelisting would definitely do it.
