Finally got the SMTP Server working correctly now by specifying "KC135ATS.NET" as local & changing the old default domain name of "INETSERVER" to "KC135ATS.NET". After restarting, everthing worked correctly with all Wingate sending & recieving all of our internal Exchange Server's traffic. I've gotten that KAV plug-in working, too. I'm truly amazed at the number of viruses KAV detects on our SMTP feed! Sometimes as many as 40 a day. We've had far less virus incidents since activating it. And, combatting SPAM is much easier via the SMTP Server's policies. Very cool...
How does an external user authenticate and relay mail through the Wingate server. Say I'm at home connected to my mail server via IMAP/SMTP & want to send mail to a recipient (
eds@asua.net) outside of my domain (@kc135ats.net). I get a "relaying not allowed" message (which is good since Wingate doesn't know who I am). How does one securely or unsecurely authenticate? I've read the KB articles but still remain confused. To add to that confusion, I have a Win98 box that CAN send mail from Outlook 2000 but my Windows 2000 boxes can't. Why's that?
Thanks,
Billbo
I have an Enterprise Wingate 5.x with unlimited users. Is it possible to provide external users web mail with the mail server