xxgenius
asked on
Exchange SMTP gateways routing users
i have to put an exchange server 2000 on the internet as a gateway SMTP server. this server is going to forward mail into the exchange server behind the firewall. what i would like to do is add an antispam server (Windows 200 SMTP) in the middle and forward mail for specific users only from the gateway through the antispam server. all other users will go directly to the exchange server behind the firewall. i have done this before but have used Sendmail as the gateway (it has an alias table to route certain users based on their smtp address). the reason why i am using the exchange server as the SMTP gateway is licensing issues with antivirus. i want to scan the viruses on the SMTP servers and the exchange server.
does anyone know a way exchange can do this with active directory?
i have seen MS KB 251124 (for 5.5), this is what i need to do in Exchange 2000. i have never deployed exchange servers as SMTP gateways before, i have only used either windows SMTP or sendmail.
does anyone know a way exchange can do this with active directory?
i have seen MS KB 251124 (for 5.5), this is what i need to do in Exchange 2000. i have never deployed exchange servers as SMTP gateways before, i have only used either windows SMTP or sendmail.
ASKER
thanks for the info, i'll look it over and see what i can test. i hoping for something a bit easier to manage.
ASKER
the posted article is not the equivalent. that explains forwarding mail in AD. what i need it the ability to do alias routing with exchange 2000/2003.
I wouldn't say that it's no resolution, just that as the only solution is not worth implimenting. The posted article does not forward in [or through] AD, it simply uses AD to store the equivalent of the custom recipient in 5.5 as an email enabled contact. It's still an SMTP forwarded message using an intermediate secondary domain name. The outside server doesn't even have to know whether it is Exchange or Sendmail on the inside. AD is required outside but only to hold Exchange together.
Anyway delete or zero/paq as you like, I don't care.
Anyway delete or zero/paq as you like, I don't care.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Presumably your outside server is going to sit in it's own little AD forest and org rather than being part of your internal AD structure.
The option to forward unresolved mailboxes to the main internal server will be needed to bypass the spam server for those users you're not filtering for, I think it's under the delivery tab of the virtual smtp server.
There's going to be a problem of the outside server recieving a mail for a spam-filtered user having to forward the mail to user@yourdomain.com when it thinks it and the internal server are responsible for user@yourdomain.com, therefore you'll have to forward it to a dummy domain user@yourdomain.spam and set up an additional domain name and recipient addresses on the internnal server with @yourdomain.spam under the default recipient policy.
I am worried about the licensing though, I think you have to buy a license for each user/mailbox/forwarding on the outside server as well as the CAL on the inside one.