OK pardon the verbosity but . . .Here is the whole picture:
I am upgrading a very bad peer to peer network where POP3 email (and website) was hosted elswhere. I set up a Mitel 6.0 final box (fresh install) with all updates as a server & gateway, using DHCP server to 15 workstations. The mitel is connected directly to the DSL modem.
Hardware is a Dell PowerEdge 600SC Server with mirrored IDE drives, an IBM e1000 gigabit card as the internal interface and an IBM e100 as the external.
Using Static IP on Verizon DSL
The primary ibay is running MamboServer 4.5.
Installed contribs are:
phpmyadmin
Coppermine
awstats
phpsysinfo_2.1
mrtg
Clam AV and Spamassassin from Jesper Knudsen's nice installation files (
http://www.swerts-knudsen.dk)
We also set up a SUse OpenExhcnage server to run groupware and webmail behind the Mitel.
After stabilizing the local network, we updated the www DNS record to host the organization's website on the mitel. This worked fine.
2 weeks later we switched the email to use the Mitel by setting up a relay from the old POP3 server providers exchange server. The idea was to use the Exchange server as a relay in case we ever went down
Mail was relayed through the mitel box to filter for spam and viruses and forwarded (using the Delegate Mail Server setting) to the OpenExchange server.
This all worked great for a week. Then suddenly. . . .No Mail. In troubleshooting I also found out we could no longer reach the website of the company running the relay server (a bank of ips at 207.103.198.x). Otherwise web access and mail sending function normally.
Further trouble shooting showed that if I connect a workstation directly to the DSL modem (in front of the mitel box which) I can again reach the sites at 207.103.198.x.
I have solved our immediate problem by adding a 4 port router between the mitel and the DSL modem and putting the Suse OpenExchange server on the same subnet as the external interface of the mitel. The OpenExchange server now collects the mail flawlessly.
However, this is not the ideal set up (for a wide variety of reasons) and the whole range of addresses at 207.103.198.x are still blocked out by the mitel server.
I though it might be spamassassin, or IPtables, but I cannot find anything in wither of those programs' configuration which appears to be causing the problem.
I backed up the mitel configuration to a local machine, erased the server and did a clean SME6.0 install again and viola, the block was gone.
However, once I restored the configuration from the workstation the block was back on.
I am somewhat of a neophyte to Linux, but I have configured and run 6 mitel boxes in a variety of configurations over the past two years. All of them are still running with no problem.
This on has me stumped.
Any help in the form of tips or cures would be greatly appreciated
-A
