• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 366
  • Last Modified:

Problem receiving POP Email


I'm hvaing trouble receiving POP e-mail from an ISP from behind a PIX 506 firewall.  Attempts to telnet to port 110 from behind the firewall fail, however, from outside the pix the connection is fine, so I know it is something in the firewall configuration.

I have the following access-list applied on the outside interface in.

access-list rdpin permit tcp any interface outside eq 3389
access-list rdpin permit tcp host [ISP Mail Server] gt 1024 any

Initially, the access-list was for the RDP only, however I thought opening the ports above 1024 was the problem with POP.  With no access-list it still does not work and opening pop3 port does not work either.  What needs to be open for POP to function on the internal network?
  • 4
  • 3
  • 2
  • +2
1 Solution
Are you able to browse internet from behind the firewall.

I mean are you able to telnet on port 80 of any website. e.g google.com etc.

If yes, then you need to modify your IN to OUT access-list.
caplinktechAuthor Commented:
I can browse the internet from behind the pix, but telnetting to port 80 from behind the pix fails.
Are you using some proxy server.

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

caplinktechAuthor Commented:
nope, this is what has me baffled as well.
To quickly take a look at it, can you post the sanitized configuration of your pix firewall ? (I mean just remove the last 2 octets of your public ips).

Do you have any access-lists assigned to you inside interface? By default all traffic is allowed outbound along with the return traffic so you don't need the inbound access-list entry either.
The PIX will dynamically assign ports for traffic that is originated from the inside. As lrmoore indicated, the PIX by default does not filter outbound traffic. If you have no restrictive ACLs applied to the INSIDE interface, then I suggest that you look at you client.

JEEGO(AL) - in the spirit of the just ended World Cup
caplinktechAuthor Commented:
Sorry for the non prompt reply, but this just has me completely confused.  The POP e-mail manages to work intermittantly at a very rare occurance, like once every 2 weeks for some unknown reason.  I don't think the problem is on the client as none of the computers behind the pix can telnet to port 110 of the pop server which initally led me to believe there was a problem with the ISP.  However, aside of the pix, telnetting to 110 is not a problem at all.

I have the sanitized config below.  It is a very basic config with VPN.

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password x encrypted
passwd x .2KYOU encrypted
hostname mine
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
access-list 100 permit ip
access-list 100 permit ip
access-list rdpin permit tcp any interface outside eq 3389
access-list rdpin permit tcp host [ISP_Mail_IP] gt 1024 any  <--- I added this hoping it might do something to make it work, it hasn't
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 24.x.x.187
ip address inside
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnpool
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 100
nat (inside) 1 0 0
static (inside,outside) tcp interface 3389 3389 netmask 255.255.255.
255 0 0
access-group rdpin in interface outside
route outside 24.x.x.185 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 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 TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set caplinkset esp-des esp-md5-hmac
crypto dynamic-map cisco 1 set transform-set caplinkset
crypto map caplink-map 20 ipsec-isakmp dynamic cisco
crypto map caplink-map interface outside
isakmp enable outside
isakmp key x address x netmask x no-xauth
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 1000
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash sha
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup caplinkclient address-pool vpnpool
vpngroup caplinkclient dns-server
vpngroup caplinkclient wins-server
vpngroup caplinkclient split-tunnel 100
vpngroup caplinkclient idle-time 1800
vpngroup caplinkclient password x
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
: end
I would venture to say that the problem is the ISP's and not yours..
I'm currently using cable modem with PIX506 config very similar to yours and I have zero problems getting pop3 email (all my EE mail) from any of my PC's inside..
Although I did have a problem one time when I changed the outside IP address - the mask defaulted to class A because I fat-fingered it. Only problem I has was email. Pop3 mail server IP was in that same class A network so it never got forwarded to a gateway..

caplinktechAuthor Commented:
That is what has me confused is I have no idea what could be wrong on the ISP end.  

The masks are right and they on the same class A networks anyway (had to double check since I tried everything else).

I just am idealess as what the issue could be because as I said previously, the ISP works flawlessy outside of the Pix.

Is there anymore to trace the packets somehow to try to get a better understanding of what is happening?
Enable logging to see if anything is being blocked - the PDM log is pretty comprehensive if you enable it.
enable session monitoring (in your console or ssh/ telnet window) or output to syslog server
Try using debug packet and filter on the protocol, i.e.
  debug packet inside dst <pop3IP> netmask proto tcp dport 110 both

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 4
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now