Re: Messagelabs issue with remote workers

"Poch" <poch@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>I have a client who has recently introduced the MessageLabs service.
>Following the instructions provided they have restricted only the
>MessageLabs servers from being able to connect to the Exchange 2000 Virtual
>SMTP Server. This of course in turn prevented the remote users who use POP
>and IMAP and Outlook/Outlook Express from being able to send Email via this
>server.

That's right. They should be using the SMTP servers at MessageLabs,
not your SMTP server.

>These restrictions have since been removed in order to allow the
>remote workers to connect and send mail.

This is the wrong thing to do. Have those clients use the SMTP server
in your MX record, e.g. the MessageLabs SMTP servers.

>In turn this has resulted in a lot
>of spam and virus infected messages slipping through the net as they are
>delivered directly to the server bypassing MessageLabs.

No kidding? :)

>There must be others
>in a similar situation. What have you managed to come up with in order to
>allow the remote workers to function and prevent the unwanted messages from
>getting in? I have only the mentioned resources to work with and alternative
>mail filtering solutions are out of the question.

Instruct the remote uses to use your new SMTP server at MessageLabs.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
.

Relevant Pages

  • Re: SMTP lockdown, MessageLabs
    ... Create an destination set with the MessageLabs IPs. ... On your mail server publishing rule, *listen to requests only from* this destination set. ... directly to our ISA Server using its external IP address. ...
    (microsoft.public.isa.configuration)
  • Re: ISA Server 2004, Exchange 2003, RPC over HTTP, SMTP lockdown
    ... Put the MessageLabs in parallel to the ISA with one NIC sticking into your internal network and the other NIC connected to your internet router/gateway. ... Set the default gateway of your Exchange server to the internal IP of your MessageLabs and on your SMTP connector, set the smart host to the internal IP of the MessageLabs device within square brackets. ...
    (microsoft.public.isa.publishing)
  • SUMMARY: ES40 Server Crash
    ... Subject: ES40 Server Crash ... This email has been scanned for all viruses by the MessageLabs Email ... Security System. ... For more information on a proactive email security ...
    (Tru64-UNIX-Managers)
  • Messagelabs issue with remote workers
    ... MessageLabs servers from being able to connect to the Exchange 2000 Virtual ... SMTP Server. ... allow the remote workers to function and prevent the unwanted messages from ... mail filtering solutions are out of the question. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange IMS Connector Issue
    ... Did this start after you introduced the MessageLabs AV? ... > Hits the IMS on the remote site. ... > If I create a new email address on a remote server, ...
    (microsoft.public.exchange.admin)