Hi Mohammed, if your customers aren't assigned unique ip subnets (usually business/leased-line customers) which are/should be documented seperately in the appropriate radb but are originating from dynamic access like DSL's you're somewhat out of any other option.
Even static assignments, radb-entries and everything else will not protect you against 'blackmailing' by some lists (like sorbs blocking whole asn's). regards, Marcus > -----Ursprüngliche Nachricht----- > Von: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] Im Auftrag von > Mohammad Khalil > Gesendet: Montag, 15. März 2010 11:39 > An: cisco-nsp@puck.nether.net > Betreff: [c-nsp] SMTP > > > hi all > > we have a lot of our customers that are uses SMTP servers > other than our own server > which causes the subnet to be black listed > we tried to block them from accessing any other SMTP server > except our own server using access lists on our core routers > it works fine but is that the optimal solution for that?? > is there any other ways to do that ? > > Thanks > > _________________________________________________________________ > Hotmail: Powerful Free email with security by Microsoft. > https://signup.live.com/signup.aspx?id=60969 > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
