Avatar of kmcbrearty
kmcbreartyFlag for United States of America

asked on 

Could not deliver the message in the time limit specified. Please retry or contact your administrator.

I have had e-mail setup on my server for over two years without any problems.  The server handles the e-mails for multiple domains and sends e-mail out through a smart host.

My ISP is SBC Global and lately I have had a number of problems.  The first issue that I had was they started blocking all outgoing e-mails from e-mail addresses they didn't explicitly know about.  No problem, set all the e-mails up and has worked fine for a couple of months.  Now out of teh blue I am getting NDR's.

Could not deliver the message in the time limit specified.  Please retry or contact your administrator.

It isn't happening on all e-mail messages but quite a bit of them.  Through some testing the e-mails that I was sending were taking on average 40 minutes to deliver.  

The research that I have done suggests that these problems are related to DNS.  Although since I am sending the messages through SBC I don't know how that would be a problem.

I am sending out e-mails from:
neo.rr.com (another ISP that is being used for e-mail)
mfschiro.com (Domain I Own)
dmkmarketing.net (Domain I Own)

Before it is asked I have two people who work remotely that have road runner e-mail accounts.  They wanted the ability to send mail while they are on the road from outlook (which RR doesn't allow) and be able to use the out of office assistant which is only availalbe if you are using an exchange server.  These users connect to the exchange server using rpc over http and their e-mail is downloaded periodically from RR pop server to the exchange server using IGetMail.  Their e-mail is setup to be sent using the neo.rr.com e-mail.

I am experiencing the same problems from the RR accounts as I am the other accounts and am not sure how to resolve this issue.
ExchangeOutlookDNS

Avatar of undefined
Last Comment
kmcbrearty
Avatar of Steve
Steve
Flag of Australia image

From reading your message, it appears that you are relaying the email through SBC Global's mail server.. this is why they NDR your messages when they dont know about the domain names..

if you set your mail server to deliver directly using DNS to resolve, you should (so long as SBC dont block mail servers on client networks) be able to send your email directly..

Steve

Avatar of kmcbrearty
kmcbrearty
Flag of United States of America image

ASKER

SBC now knows about the e-mail addresses that I am sending from and that is no longer the problem.  Which by the way I already stated.  As mentioned I can still send e-mail out but many are getting returned indicating that they were not able to be delivered.  

In regards to setting the mail server up to send directly using DNS I had problems in the past becuase at the time I had a dynamic IP address.  Many spam filters are set not to recieve mail from a machine that has a dynamic IP address.  I now have a static IP address and could look at changing this back to use DNS.  Unfortunately, I set this up two years ago and haven't messed with it since.  Can you please let me know what needs to be changed.  My knowledge with exchange is limited.

Thank you for your help.
Avatar of kmcbrearty
kmcbrearty
Flag of United States of America image

ASKER

>> SBC dont block mail servers on client networks

How can I test for this?  

I think I determined why I am having problems and it is only going to get worse.  Apparently SBC is now requiring that you use SSL and port 465 but I can not configure Exchange to use SSL.  For now messages are making it through on Port 25 but probably not for long.  Not to mention all of the other issues I think that I would benefity from setting this up to run over DNS.

The problem I am having now is I get the following message:

>
Avatar of Steve
Steve
Flag of Australia image

I really think you have multiple issues in play here..

so.. lets get things straight.. you can send email from all 3 x domain names no problems, its only the incoming mail that isnt reaching you ?

I just sent a test message to admin@mfschiro.com  and got a bounceback (which i expected) saying user unknown..

So.. lets check a few things :
 - do you have all the domain names setup correctly within exchange ?
 - are the email addresses configured to receive email on those email addresses ?
 - is your mail machine called server.mfschiro.com  (76.253.128.102) ? (checking to make sure dns is setup correctly)

if this is all correct, it looks like your DNS and Mail server are setup correctly..

there is currently a reverse DNS entry set for that IP : adsl-76-253-128-102.dsl.akrnoh.sbcglobal.net
Only problem with that is that you'll probably have problems because they've used 'adsl' and 'dsl' in the reverse name, which a lot of spam filters which use RDNS to verify senders look for..  In saying this i dont think that is your current problem, but just something to keep in mind..

The next issue though that you've got is that your remote road runner accounts (and any other accounts that are remote), are connecting into your rr.com server and trying to relaymail through you.. which by default isnt allowed.. the only way you could fix this would be to either get them static addresses and allow those addresses for relay, or allow the entire road runner range to relay (which IS NOT advisable), or.. set those users up so that they vpn/pptp etc into your server get assigned local IP's and relay their mail through you using the local IPs..

does this help you at all ?

Steve





Avatar of kmcbrearty
kmcbrearty
Flag of United States of America image

ASKER

I can currently recieve mail without any problems.  Lately I have been having problems with outgoing mail that has been set to be sent through a smart host (SBC).  Some e-mails are going through fine while others are getting sent back after 48 hours saying they couldn't be delivered within the time frame allowed.  

A couple of things to note:

1.  I was having a problem with an NDR attack.  (This has been resolved by no longer delivering NDRs and making a few other adjustments)
2.  I have continued to have more and more issues sending mail through SBC.  The latest coming from their technical support after calling regrading another issue is that they are now requiring that you use port 465 and SSL.  At the moment I can still send mail through port 25 but I don't know for how long.
3.  With number 2 in mind I really want to configure my exhange server to send mail using DNS rather than the SBC smart host.

Admin@mfschiro.com isn't a valid account.  You could send a mesage to kmcbrearty@mfschiro.com which is the e-mail address that I use.

The macine name is Server but the domain is dmkmarketing.local.  That being said the domain defined in exchange on the virtual server is mfschiro.com.  Also I have run SMTPDiag and it indicates that everything is fine.

As far as the remote users are concerned I have them setup to use RPC over HTTP so relaying shouldn't be an issue since they are connecting and authenticating to the server.  Additionally, I have the exchange server set to relay for any user that authenticates.

At the moment I have the exchange server set to e-mail out using the SBC smart host.  I have tried to peform the following steps to send mail using DNS.

1.  Set the SMTP connect to send mail using DNS.
2.  Set the outbound security to anonymous on the advanced tab of the SMTP connector
3.  Cleared the Smart Host field on the Virtual Server; Delivery; Advanced
4.  Set the outbound security to anonymous on the Virtual Server; Delivery

After performing these steps and trying to send an e-mail I get the following messages depending on who I am trying to send as:

>
 is not allowed to use this service>

I have the following ports open on my firewall:

Web Server - TCP 80
HTTPS Server - TCP 443
SMTP Server - TCP 25
DNS Server - TCP 53  UDP 53
ASKER CERTIFIED SOLUTION
Avatar of Steve
Steve
Flag of Australia image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of Steve
Steve
Flag of Australia image

in case you havent.. this is how to enable the SMTP protocol logging feature.

http://support.microsoft.com/kb/303738

Steve
Avatar of kmcbrearty
kmcbrearty
Flag of United States of America image

ASKER

The problem is definitely with SBC but their support sucks.  I finally decided to sign up for a third party relay (dnsexit.com).  For $15 a year I can save myself a lot of time and grief.   Thanks for your help.
Exchange
Exchange

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo