>But I think you may have explained both the mail problem and why my TF >gate never worked correctly; the other TF server I was trying to share >conferences with is in the same domain (although different sub-domain) >as both my server and the STMP server my server relays to. Is there a >workaround for that?
No "work-around" is necessary as long as the full domain is different, which it is.
The most common mitake I find people make is to put domains in the SMTP Gateways "domain" list. This is unecessary, and can be harmful.
Marking the SMTP gateway as default is all that is necesary.
The domains list for gatewyas is to tell Mail Server to route mail destined to x.sub-domain.com via a specific gateway.
For example, when setting up a tfnet account, say they are foo, as foo.tfnet.org. And say this host will connect by modem or TCP to pick up news an email from the spider island host.
So I do not want mail for foo.tfnet.org routed through the SMTP gate anymore. That means I need to add foo.tfnet.org to the domains list of the gateway I want to handle the mail. In this case, the foo TFNet gateway.
Say that foo was going to call klonzone to pick up their mail, then I would add foo.tfnet.org to the klonezone domains list. The foo mail would get dumped in with the klonezone mail, and klonezone's Mail Server would sort and route it. If klonezone is setup with a foo gateway, the mail would be delivered.
Once mail is routed to the SMTP Gateway and forwarded to the upstream SMTP server, the Internet's DNS takes over. In the DNS there are magic records called MX records in the DNS database that say for foo.tfnet.org, deliver email to mail.spiderisland.com. And thats how incoming mail end up here for routing via Mail Server's own rules.
