conflict between access-list and vpn WHY!!!????

[picnmix]

Hi I have a problem when I setup my access-lists to restrict who can send me mail via port 25 (SMTP)and I have VPN enabled on the PIX The mail stops. I can't see what is wrong with my config as I have used this config on about 60 other pix's and it's fine. Below is the config any ideas?
PIX Version 6.1(4)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password KpbXjmEjDSl86hDz encrypted
passwd KpbXjmEjDSl86hDz encrypted
hostname pixfirewall
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
no fixup protocol smtp 25
names
access-list smtp permit tcp 193.109.254.0 255.255.254.0 host 1.2.3.204 eq smtp
access-list smtp permit tcp 195.245.230.0 255.255.254.0 host 1.2.3.204 eq smtp
access-list smtp permit tcp 194.106.220.0 255.255.254.0 host 1.2.3.204 eq smtp
access-list smtp permit tcp 85.158.136.0 255.255.248.0 host 1.2.3.204 eq smtp
access-list smtp permit tcp 216.82.240.0 255.255.240.0 host 1.2.3.204 eq smtp
access-list smtp permit tcp host 195.216.16.211 host 1.2.3.204 eq smtp
access-list 101 permit ip 10.0.0.0 255.255.255.0 172.16.1.0 255.255.255.0
pager lines 24
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside 1.2.3.205 255.255.255.248
ip address inside 10.0.0.254 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool pptp-pool 172.16.1.200-172.16.1.250
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 1.2.3.204 10.0.0.2 netmask 255.255.255.255 0 0
access-group smtp in interface outside
route outside 0.0.0.0 0.0.0.0 1.2.3.206 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-pptp
no sysopt route dnat
telnet 10.0.0.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe 40
vpdn group 1 client configuration address local pptp-pool
vpdn group 1 pptp echo 60
vpdn group 1 client authentication local
vpdn username user1 password 4
vpdn username user2 password 3
vpdn username user3 password 2
vpdn username user4 password 1
vpdn enable outside
terminal width 80

 

[vlf]

I like to set up an access list on all interfaces, even if it's permit ip any any. But, you could create a temporary access list on your internal interface that has permit tcp 10.0.0.2 any eq 25 permit ip any any. To see if you're getting hits. If you are, try being more specific. Also, try telnetting to these ips from your smtp box on port 25. (telnet 193.109.254.x 25). If you get a blank screen, it's working outbound.

If you get hits on your access list, check your translate table. sh xlate | include 10.0.0.2

While you're doing this, look at the log and see if there are any errors associated with any of these IPs.

And, make sure there are hits on your smtp access list.

 

[hbalf1]

Hi
Did you resolve this, because I think I am having the exact same issue and cannot figure it either
TIA
HB