Ok, gonna try to keep this is short as possible.. Got a mail server at a co-lo site getting throttled with spam so Postini was employed. Postini was effective, but not as effective as it could be without locking down smtp to their IP range. That can be achieved - no problem.
The problem is, the clients still rely on connecting to smtp (as the mail server is on the net, not in house), so once the rule is in place, everyone's smtp stops working.. Also, the archaic email server being used does not allow for smtp to listened on alternate or additional ports.. So, my thought to work around this is to:
1. come up with a random port number, i.e. 61061
2. reconfigure the users email clients to use the default smtp port of 61061
3. configure the pix to redirect all port requests from 61061 to port 25 of the mail server
My question is, can I achieve this while still keeping Postini happy? The current access list for postini is:
access-list outsidein permit tcp 64.x.x.x 255.255.240.0 host 70.x.x.43 eq smtp
What command can I add/modify to keep the above acl happy, while allowing users from the office to hit smtp by being redirected to the same server from the "dummy" port (61061)
Thanks
The problem is, the clients still rely on connecting to smtp (as the mail server is on the net, not in house), so once the rule is in place, everyone's smtp stops working.. Also, the archaic email server being used does not allow for smtp to listened on alternate or additional ports.. So, my thought to work around this is to:
1. come up with a random port number, i.e. 61061
2. reconfigure the users email clients to use the default smtp port of 61061
3. configure the pix to redirect all port requests from 61061 to port 25 of the mail server
My question is, can I achieve this while still keeping Postini happy? The current access list for postini is:
access-list outsidein permit tcp 64.x.x.x 255.255.240.0 host 70.x.x.43 eq smtp
What command can I add/modify to keep the above acl happy, while allowing users from the office to hit smtp by being redirected to the same server from the "dummy" port (61061)
Thanks