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

Can't Receive Mail - New Domain and Exchange Setup

I just brought up a brand new Windows 2000 Domain with Exchange 2000.

For whatever reason I can send mail, but not receive for outside the network.

I don't see any errors in the event viewer nor am I getting in NDRs.

Here is some info about the network:

Single DC with Exchange: (server name is BEAVIS)
Internal Domain: jetselectric.com
External Domain is also www.jetselectric.com (However, we do not host the DNS for our public name)
Web host has a record created to forward all email to exchange.jetselectric.com
I have a MX record created on the DC with the host name exchange for beavis.jetselectric.com

Here is the running config from our 501 PIX:

: Saved
PIX Version 6.3(3)
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password uXrsXO3xdRQ10kEs encrypted
passwd uXrsXO3xdRQ10kEs encrypted
hostname JETSFW
domain-name jetselectric.com
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 102 permit tcp any interface outside eq smtp
access-list 102 permit tcp any interface outside eq www
access-list 102 permit tcp any interface outside eq https
access-list 102 permit tcp any interface outside eq ftp
access-list 102 permit icmp any any
access-list inside_outbound_nat0_acl permit ip any
access-list outside_cryptomap_dyn_20 permit ip any
pager lines 24
logging on
mtu outside 1500
mtu inside 1500
ip address outside
ip address inside
ip audit info action alarm
ip audit attack action alarm
ip local pool jets-pool
pdm location inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0 0
static (inside,outside) tcp interface smtp smtp netmask 255.255.255
255 0 0
static (inside,outside) tcp interface www www netmask
5 0 0
access-group 102 in interface outside
route outside 255
timeout xlate 0:05: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 RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http inside
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 ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup jets-vpn address-pool jets-pool
vpngroup jets-vpn dns-server
vpngroup jets-vpn wins-server
vpngroup jets-vpn default-domain jetselectric.com
vpngroup jets-vpn idle-time 1800
vpngroup jets-vpn password ********
telnet inside
telnet inside
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
: end

I can send mail fine. I can also send and receive internally.

Any ideas?


Justin Durrant
Justin Durrant
  • 3
  • 2
1 Solution
I don't see a public IP address in your static statements for BEAVIS.  And the MX record points to your PIX firewall.  Are you forwarding SMTP packets somehow?

Try adding a static (inside,outside) Public.Ip.Address.Here netmask X.X.X.X 0 0

Then point your MX record for your internet domain for the public IP of Beavis.

Might need to add a conduit record also - conduit permit tcp host X.X.X.X eq smtp any (where x.x.x.x is internet addy of Beavis)
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
Well Beavis doesn't have a public IP address. The MX record on BEAVIS has the name "exchange" and points to beavis.jetselectric.com.

Right, but from the internet, your jetselectric.com domain has an MX record that points to exchange for mail.

jetselectric.com        MX preference = 10, mail exchanger = exchange.jetselectric.com
exchange.jetselectric.com       internet address =

Now, is your outside interface of your PIX firewall as it appears from your config listed:
ip address outside

So, unless your PIX is set up to forward port 25 traffic to BEAVIS (which I didn't see), you'll need to do something similar to what I provided above.

Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
The PIX is setup to forward port 25.. see:

static (inside,outside) tcp interface smtp smtp netmask 255.255.255
255 0 0

Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:

I cannot ping exchange.jetselectric.com or from within Jets.. Is this a problem?

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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