Yes i dont want anyone to access port 25 within the VM too because i dont want my clients to send spam from the VM. I wanna allow the incoming connections ofc to receive mails but dont want anyone to send out mails.Of course, in that case only outgoing (relative to VM) traffic is filtered, incomming is still allowed.
From where to where with which rules applied?
Again, if you have outgoing traffic dropped, then services from the outside can still make an incomming (relative to your VM) connection. If you drop also incommig connections, then services from the outside will not be able to connect to your VM.
As expected
Because the traffic from within the VM to itself does not necessarily go through the filters as you might expect. Is there a reason you don't want this?
If my client can access port 25 from VM he can send out spam too which is what i dont want at all
Secondly for eg if mail2web is able to make connection to my VM how can it even send out the mail when outgoing is blocked?
For testing I sent a mail from my IMAP email address to my random gmail address and it went through which is what I dont want at all
My outgoing traffic rules are
DROP MAIL
DROP tcp OUTGOING 25
DROP tcp OUTGOING 26
DROP tcp OUTGOING AND INCOMING 465
DROP tcp OUTGOING AND INCOMING 587
Last edited: