Re: 4.4.7 email delays
- From: "Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom>
- Date: Mon, 11 Sep 2006 15:40:54 -0500
That doesn't make sense to me. If you let Exchange send the mail, it will
completely bypass your ISP. Exchange will attempt a direct connection
(using DNS) to the destination mail server. Your ISP's mail server would
not be involved at all for outbound mail.
Is that something you could try?
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Christo" <Christo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:48506977-EE04-4916-9A4F-5436C19E35A4@xxxxxxxxxxxxxxxx
Thanks for staying with this Ben!
I am sensing I will have no choice but to go through our logs to ensure it
is nothing on our end...I still believe it isn't as we never had issues
before switching ISP's and we have no other issues with 99% of the other
domains we deal with.
As far as using the ISP's smtp...the way they are set up is if I use my
smtp
their system and others see it as relaying and that becomes a worst
problem
then what we have now. I am trying to get the 'powers that be' here to
let
me host our own domain (as we host our mail ect. on exchange anyways and
host
our own GIS) as I believe it will be much less problematic...they don't
see
it the same way as they base their decision on the problems our ISP faces
and
think we will have all the same issues....they may have a point...but at
least there will only be 1 person responsible for the fix...and that
person
would be in-house.
"Ben Winzenz [Exchange MVP]" wrote:
Without seeing the actual details of the smtp conversation (smtp logs),
it's
impossible to say anything other than your ISP's mail server was unable
to
deliver the message to hotmail within the time period specified.
As a side note, why are you using your ISP for outbound mail? Exchange
will
send outbound mail quite fine on it's own. If your ISP is having issues,
allowing Exchange to deliver the mail would allow you to perform further
troubleshooting without requiring the assistance of your ISP.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Christo" <Christo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A9C98F38-70B0-4999-9B47-44E5DE151B3F@xxxxxxxxxxxxxxxx
Ok...thanks for the greylisting explanation. As far as dealing with
the
ISP.....pretty sure I could learn brain surgery before getting an
answer
from
them....usually they will deal with me after I have proved that I have
exhausted every other known possibility and that the issue is with
them.
As far as sending external domain based email...the exchange server is
not
involved as far as I understand as it is smtp and pop from the
desktop/outlook.
Below are the delay and fail receipts............
Reporting-MTA: dns;smtp.nexicom.net
Final-Recipient: rfc822;gjsharp@xxxxxxxxxxx
Action: delayed
Status: 4.4.7
Will-Retry-Until: Sun, 10 Sep 2006 09:37:22 -0400
X-Display-Name: gjsharp@xxxxxxxxxxx
Undeliverable: Delivery Status Notification (Failure)
Your message did not reach some or all of the intended recipients.
Subject:
Sent: 9/8/2006 8:37 AM
The following recipient(s) could not be reached:
gjsharp@xxxxxxxxxxx on 9/10/2006 8:44 AM
Could not deliver the message in the time limit specified.
Please retry or contact your administrator.
<smtp.nexicom.net #4.4.7>
*********************************************************
"Ben Winzenz [Exchange MVP]" wrote:
Greylisting means that it won't accept it the *first* time, but the
second
time that you try and deliver it, the message will be accepted, not
NDR'd.
Can you post the full text of the eventual NDR that you receive? Have
you
checked to make sure that your ISP has PTR records set up?
Where exactly is Exchange involved on your side? It sounds like (from
what
you wrote) that the clients (Outlook) are configured with your ISP's
server.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Christo" <Christo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BC8135E-2428-42C2-86FD-EC2DDD771269@xxxxxxxxxxxxxxxx
Thanks for the reply Andy....just so I understand...greylisting in
my
case
would be the recipient (hotmail, sympatico) won't accept mail from
my
ISP
because there have been no successfull deliveries from my domain?
If I am correct...there really isn't anything I nor my ISP can do
about
this?
As a note...our previous ISP never had issues like this....is this
common
now?
...just another reason I should be hosting this all myself...
"andy webb" wrote:
if you're getting a 4.4.7, it's most likely a greylisting scheme by
the
recipient MTA.
"Christo" <Christo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB5C0365-90F9-4302-A1AF-8FF5F6F5B681@xxxxxxxxxxxxxxxx
Windows and Exchange 2003
Outlook 2003
Symantec Enterprise 10 for Exchange
We host internal email and pop/smtp domain email from ISP.
Settings
for
smtp are those of the ISP. For certain domains (hotmail,
sympatico,
ect)
emails are delayed 4.4.7 and then non deliverable. Other domains
are
fine
and even appears sending to problem domains is somtimes
intermittent.
Scanning outbound mail by Symantec has been disabled and we
smtp/pop
from
the desktop.
Is this my issue or our ISP's?????...I can't find anything on my
side
causing this and the error states the ISP's smtp server.
Any help or direction is appreciated.
Christo.
.
- Follow-Ups:
- Re: 4.4.7 email delays
- From: andy webb
- Re: 4.4.7 email delays
- References:
- Re: 4.4.7 email delays
- From: andy webb
- Re: 4.4.7 email delays
- From: Ben Winzenz [Exchange MVP]
- Re: 4.4.7 email delays
- From: Christo
- Re: 4.4.7 email delays
- From: Ben Winzenz [Exchange MVP]
- Re: 4.4.7 email delays
- From: Christo
- Re: 4.4.7 email delays
- Prev by Date: Re: exchange resolving dns? not supposed to!
- Next by Date: Re: exchange resolving dns? not supposed to!
- Previous by thread: Re: 4.4.7 email delays
- Next by thread: Re: 4.4.7 email delays
- Index(es):
Relevant Pages
|
