Menu
Reply
  • 520
  • 43
  • 151
DreamOfCheese
Rising star
116 Views
Message 11 of 14
Flag for a moderator

Re: Port Forwarding SMTP 25 on a Super Hub 3

It was likely put there for the same reason as 53, to deter people who might not know better from giving it a go and running publically accessible mail servers or DNS servers

Misconfigured mail servers running the risk of spam, and misconfigured DNS servers running the risk of being used in amplification attacks.
0 Kudos
Reply
  • 19
  • 0
  • 0
midi_user
Joining in
106 Views
Message 12 of 14
Flag for a moderator

Re: Port Forwarding SMTP 25 on a Super Hub 3

Yeah. 

0 Kudos
Reply
  • 3
  • 0
  • 0
UKIkarus
Joining in
30 Views
Message 13 of 14
Flag for a moderator

Re: Port Forwarding SMTP 25 on a Super Hub 3

Hi There,

I too stumbled upon this with a home lab setting up Exchange, turns out if you don't have a spare router to hand and want a quick fix (and are comfortable with JavaScript) the entire "Blocked Ports" check is just client-sided JavaScript validations, easily overridden with the dev tools in browsers.

That being said, a proper router with the Hub in modem mode would give you much more control.

0 Kudos
Reply
  • 19
  • 0
  • 0
midi_user
Joining in
18 Views
Message 14 of 14
Flag for a moderator

Re: Port Forwarding SMTP 25 on a Super Hub 3

Hi,

That is useful to know.

I ended up getting a new router and putting my VM Hub in Modem Mode.
0 Kudos
Reply