@David-TP Surely you mean that incoming ports are closed by default? That's not what I'm trying to do here.

My IP has been blacklisted by Spamhaus, they have provided examples of SMTP connections being made from my IP with falsified HELOs.

Either:

1. A device on my network has been compromised and is trying to send spam as part of a proxy network, or
2. My ISP is sharing my WAN IP between multiple subscribers and it's nothing to do with my network (they shouldn't, but they are awful - wouldn't surprise me).

What I'd like to be able to do is enable more detailed logging at the router somehow so that I can see when a device requests a port 25 connection. Then if it happens I could identify the device via the IP/MAC and sort it out. And it if didn't happen but Spamhaus were still recording dodgy activity then it points to option 2 above.

At the very least I'd like to be able to just block outgoing port 25 connections.

So far I can't seem to find a way to do either of these things - the Deco system is brilliant for the mesh side of things, but seems extremely limited in terms of advanced config options.

Please do let me know if you can think of a solution!

Thanks

@David-TP I think the Raspbery Pi solution you're talking about is probably Pi-hole - which acts as a DNS proxy but would not do what I want to do in terms of logging (or blocking) outgoing requests to hosts using a particular port.

I could probably set something up with a Pi as a proxy between the main Deco and the wider internet, passing all traffic through it, but I'd need to do more research.

It's a shame the Deco system itself doesn't offer more advanced config, it's very basic.