At the weekend, I attempted to implement a new firewall onto our system and everything was going fine until testing Exchange and found out we could not receive emails via smtp. (They go out fine).
My 1st port of call was looking into the firewalls port forwarding but everything with regards to port 25 was fine,
The next test i attempted was to check the exchange response from the firewall using,
# telnet 192.168.1.24 25
220 NAME.DOMAIN.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 9 Aug 2005 14:40:22 +0100
That was fine.
From what i remember they came into the queues then seemed to be delivered but did not come into the user's mailbox.
In the end i gave up and reverted back to the old firewall and then all the test emails came into the mailboxes.
The only thing i changed on the Exchange server was the default gateway (to the new firewall).
One thing i did notice after i reverted back to the old firewall, is that when i went to the user properties> email address's in SBS was that his default smtp reply address had changed back to the local domain rather than the companys domain name.
Any suggestions? Would this have anything to do with the MX record?
My 1st port of call was looking into the firewalls port forwarding but everything with regards to port 25 was fine,
The next test i attempted was to check the exchange response from the firewall using,
# telnet 192.168.1.24 25
220 NAME.DOMAIN.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 9 Aug 2005 14:40:22 +0100
That was fine.
From what i remember they came into the queues then seemed to be delivered but did not come into the user's mailbox.
In the end i gave up and reverted back to the old firewall and then all the test emails came into the mailboxes.
The only thing i changed on the Exchange server was the default gateway (to the new firewall).
One thing i did notice after i reverted back to the old firewall, is that when i went to the user properties> email address's in SBS was that his default smtp reply address had changed back to the local domain rather than the companys domain name.
Any suggestions? Would this have anything to do with the MX record?
