Re: Exchange IMS Connector Issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: T (T_at_T.com)
Date: 05/12/04 

Date: Wed, 12 May 2004 15:07:34 +0100

Hi

this was all working fine until Monday this week. W have been using
Messagelabs for since Jan with no problems.

I have done some further tests whereby I link my German Exchange Server
direct to our exchange server here and I get an email through when I pick a
name of the GAL. Also if I change my IMS here to use DNS then I can send to
Germany no problems. When I re-introduce Messagelabs I get the issue again.
It's almost like if I pick a name of the GAL I get the issue. Messagelabs is
scanning sent and received emails

I know when you send a message gtom the GAL to another Exchange Server in
the Org it attaches other info into the header. Another interesting point
the remote server NT application log has error 3004, saying cannot send NDR
as originating address is blank

regards

tony

"Susan VanAllen [MVP]" <svanallen@nospam-mvps.org> wrote in message
news:eVShlkBOEHA.808@tk2msftngp13.phx.gbl...
> Did this start after you introduced the MessageLabs AV?
>
> "T" <T@T.com> wrote in message news:40a2057c$1_2@nnrp1.news.uk.psi.net...
> > Hi
> > Exchange 5.5 on NT4
> >
> > I have three exchange servers in different sites connected by IMS, all
in
> > same Org. My central site has directory replicators to the other two
> sites.
> > This has been working for a few years no problem. However
> >
> > If I send an email using the GAL and select a user on a different site,
> the
> > email goes across the connector, through Messagelabs Anti virus service.
> > Hits the IMS on the remote site. When the MTA tries to transfer the
> message
> > to the Information Store, it can't find the recipient in the address
list.
> > Generates an NDR which it can't send to me, appears to be same problem.
> Also
> > the problem is both ways. Directory Replication also longer works for
the
> > same reason.
> >
> > If I create a new email address on a remote server, then on my local
> Outlook
> > client type the SMTP address of the new mailbox (won't resolve as the
dir
> > replication is not working) send the email, it hits the remote server
and
> is
> > delivered as expected.
> >
> > Picking names of the address lists seems to be the problem when the
email
> > hits the remote site.
> >
> > All other email between local site users and external organisations is
> fine.
> >
> > Thanks for you assistance
> >
> > Tony Lamb
> >
> >
>
>

Relevant Pages

  • Re: SBS 2003 Exchange Missing Emails
    ... The sender does not get a NDR report or any notification that ... We have a SBS 2003 Exchange Server that is behind a Netscreen box. ... the message (although it's a good chance that MessageLabs handles ... ISP's spam filter, may have categorized the IP addresses as a source ...
    (microsoft.public.exchange.admin)
  • Re: Time is off in the SMTP log file
    ... >we use MessageLabs for our spam and virus scanning. ... >exchange server. ...
    (microsoft.public.exchange.admin)
  • Time is off in the SMTP log file
    ... we use MessageLabs for our spam and virus scanning. ... exchange server. ...
    (microsoft.public.exchange.admin)