Re: Inbound mail, sub-domain

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

From: Brian D. McGrew (brian_at_doubledimension.com)
Date: 10/07/04 

Date: Thu, 7 Oct 2004 13:57:29 -0700

I've got a good MX record for postoffice.visionpro.com and I can resolve it
as MX for any of the outside shell accounts that I have???

-brian

"Lee" <leweb2000@hotmail.com> wrote in message
news:ec2nT4KrEHA.596@TK2MSFTNGP11.phx.gbl...
> That will mean that they (yahoo, hotmail) cannot resolve the
> postoffice.visionpro.com mail exchanger to find where to send the mail.
So,
> set up a dns mx record for the domain like you did for the prior domain.
>
> Lee
>
> "Brian D. McGrew" <brian@doubledimension.com> wrote in message
> news:uqPjQyKrEHA.556@tk2msftngp13.phx.gbl...
> > I will look at the recipient policy in ESM.
> >
> > I'm am sending from outside the building; yahoo, excite, msn, hotmail,
> aol,
> > etc.
> >
> > -brian
> >
> > "Lee" <leweb2000@hotmail.com> wrote in message
> > news:uKEHszJrEHA.3288@TK2MSFTNGP12.phx.gbl...
> > > Have you set up a recipient policy for postoffice.visionpro.com in the
> > > exchange system manager? Unable to relay may indicate there is not a
mx
> > > record for the postoffice.visionpro.com in the resolving dns. You're
> > > sending to this address from the exchange 5.5 mailbox right?
> > >
> > > Lee
> > >
> > > "Brian D. McGrew" <brian@doubledimension.com> wrote in message
> > > news:uDXun0IrEHA.3080@TK2MSFTNGP15.phx.gbl...
> > > > Hello:
> > > >
> > > > I recently setup an Exchange 2003 server on a sub-domain. Our
> Exchange
> > > 5.5
> > > > servers are still primary for our domain but I've setup 2003 as
> > > > postoffice.visionpro.com. I want to be able to send mail to
> > > > brian@visionpro.com and have it go to the old Exchange 5.5 server
> (whch
> > > > still works) and then send mail to brian@postoffice.visionpro.com
and
> > have
> > > > it go to the new server. I've already added a dedicated MX record
in
> > DNS
> > > > for this but mail to brian@postoffice.visionpro.com is bouncing with
> the
> > > > following error:
> > > >
> > > > Your message did not reach some or all of the intended recipients.
> > > >
> > > > Subject: Test Four
> > > >
> > > > Sent: 10/7/2004 9:35 AM
> > > >
> > > > The following recipient(s) could not be reached:
> > > >
> > > > 'brian@postoffice.visionpro.com' on 10/7/2004 9:35 AM
> > > >
> > > > You do not have permission to send to this recipient. For
assistance,
> > > > contact your system administrator.
> > > >
> > > > <constellation.doubledimension.com #5.7.1 smtp;550 5.7.1 Unable to
> relay
> > > for
> > > > brian@postoffice.visionpro.com>
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > >
> > > >
> > > > -brian
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Inbound mail, sub-domain
    ... I've got a good MX record for postoffice.visionpro.com and I can resolve it ... > postoffice.visionpro.com mail exchanger to find where to send the mail. ... > set up a dns mx record for the domain like you did for the prior domain. ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: Need Help from DNS Expert on Subdomain DNS Records
    ... When you use nslookup to resolve these names do you get the correct internal ... domain from within and outside our firewall. ... public IP to point to the same private IP, ... You need to verify that the all DNS servers assigned to a the DNS Client be ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot a DC, HOPELESS Case
    ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
    (microsoft.public.win2000.active_directory)
  • Re: aol..
    ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
    (microsoft.public.windows.server.sbs)
  • Re: blocking annoying login popup applets
    ... > DNS server as centralized within my local network? ... Another machine is definitely not necessary for a local caching DNS ... Choice of djbdns vs. BIND: ... domains will resolve to 192.168.27.1. ...
    (comp.os.linux.networking)