Outbound emails don't work

BinaryLane does not filter outbound email on its network. If your server can't send email, the cause is usually Port Blocking: an account-level security feature that blocks outbound TCP ports 22, 25 and 3389 on new servers.

While your account is under review, Port Blocking can't be turned off. Account reviews are typically completed within 24–48 hours on business days. Once the account has been approved, you can turn it off yourself for each server: open the server in mPanel, select Network, then the Port Blocking tab, untick "Block outgoing connections for email, SSH and Remote Desktop (TCP ports 22, 25, and 3389)" and select Save and Apply: https://home.binarylane.com.au/server/-/network/port-block

Port Blocking is one switch for ports 22, 25 and 3389

Port Blocking covers outgoing TCP ports 22, 25 and 3389 together as a single switch, so it cannot be turned off for one port only. You switch it off yourself for each server once your account is approved.

If the Port Blocking switch is greyed out

If your account has been approved but you still cannot change Port Blocking, log out of mPanel and log back in, then try again.

Creating servers with Port Blocking off

Once your account is approved, you can also create servers with Port Blocking already off: send "port_blocking": false when creating the server through the API, or use --no-port-blocking with the BinaryLane CLI.

Using an external mail relay

Sending through an external mail relay or transactional email provider is a good option if you want deliverability handled for you, but it is not required: once Port Blocking is off, your server can send email directly.