Re: NDR ?
From: Allen Clark (acent1_at_nospamplease.com)
Date: 04/20/04
- Next message: Bill Nguyen: "Re: Thousands pending delivery messages in queue!"
- Previous message: duh: "Re: OWA Connection From Alternate Server"
- In reply to: Verizon: "Re: NDR ?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Apr 2004 14:01:16 -0400
Do you or anyone in your group have a dialup access as their primary mail
path? If so, you can get these type of NDR's if your dialup access is
foreign to your network.
Just a thought.
Good luck!
"Verizon" <MrWhipple@whocares.com> wrote in message
news:L0Vec.28397$hd3.15056@nwrddc03.gnilink.net...
> Thanks for the info.
>
> Actually I'm not on Verizon DSL, I'm on a Verio T1. I have a Verizon
account
> and use their news server.
>
> Here is the situation:
>
> 99% of our e-mail works fine. The 1% that doesn't work always gets one of
> the messages below.
>
> I tried the Telnet test and got different responses.
>
> 533 sorry, that domain isn't in my list of allowed rcpthosts <#5.7.1>
> Connection Failed
> Relaying denied. IP name possibly forged
>
> Our mail is setup like this:
>
> We have a Barracuda networks SPAM firewall with a public address of
> 204.245.188.9 = mail.emilyslist.org.
> The actual mail server is running Exchange 5.5 and has an address of
> 204.245.188.3 = hera.emilyslist.org.
> Everything sits behind a SonicWall Pro 230 firewall.
>
> I went to www.dnsreport.com and everything passed.
>
> Any help you could give would be greatly appreciated.
>
>
>
>
> "Allen Clark" <acent1@erols.com> wrote in message
> news:eTNXBfOIEHA.3968@TK2MSFTNGP12.phx.gbl...
> > Actually...
> >
> > I have just gone through an issue with Verizon. Verizon states that
they
> > "do not provide pointer records for DSL customers." This was from the
> > manager of the DSL support group and it is a policy of Verizon. I
> strongly
> > recommend that you dump Verizon as your DSL carrier, and get one that
will
> > actually service you as a business customer.
> >
> > The reason you get this message is because the remote mail server is
> trying
> > to use Reverse DNS to verify that you are who you are. But without a
PTR
> > record for the reverse DNS lookup, their server cannot verify who your
> > server is. This is a major flaw in the way Verizon treats their
business
> > DSL customers.
> >
> > See if there are enough complaints to start a class action lawsuit
against
> > them. The only problem with a Class Action lawsuit is that only the
> lawyers
> > make out like bandits and everyone else gets screwed.
> >
> > Good Luck!
> >
> >
> > "Kirill S. Palagin" <kpalagin@nomail.phxint.please.ru> wrote in message
> > news:eg2GTcNIEHA.3848@tk2msftngp13.phx.gbl...
> > > For some reason other mail servers do not like you. Your IP is ether
> > > listed as spamming, does not have A and PTR records, or PTR record is
> > > something like xxx-yyy-zzz-vvvv-dsl.isp.com. From keyboard of your
> > > Exchange machine perform this testing
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;153119
> > > against other mail servers.
> > >
> > > Verizon wrote:
> > >
> > > > I get one of the following messages whenever I try to send messages
to
> > > > certain recipients:
> > > >
> > > >
> > > >
> > > > The following recipient(s) could not be reached:
> > > > 'betsy@xyz.com' on 4/12/04 9:39 AM
> > > > The recipient name is not recognized
> > > > The MTS-ID of the original message is:
> > > > c=US;a=PRIMARY;p=ELLIST;l=HERAD-040412133844Z-433
> > > > -------------------------------------------------
> > > > The following recipient(s) could not be reached:
> > > > 'adam@abc.com' on 3/25/2004 1:53 PM
> > > > Unable to deliver the message due to a communications failure
> > > > The MTS-ID of the original message is:
> > > > c=US;a=PRIMARY;p=ELLIST;l=HERAD-040325185233Z-4797
> > > >
> > > > I can send messages to this address from outside the office but not
> > inside.
> > > > We have about 70 different address that we get this same reply from,
> and
> > > > when I did an nslookup the only simularity i could find was the mail
> > server
> > > > was not the same domain as the e-mail address (i.e betsy@xyz.com
> returns
> > a
> > > > MX record of registeredserver.com).
> > > > Any ideas?
> > > >
> > > > Thanks,
> > > > rkeating@emilyslist.org
> > > >
> > > >
> >
> >
>
>
- Next message: Bill Nguyen: "Re: Thousands pending delivery messages in queue!"
- Previous message: duh: "Re: OWA Connection From Alternate Server"
- In reply to: Verizon: "Re: NDR ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
