On 26 Feb 2001, 12:20, Mohammed R. Arjomandi wrote:

> I have sent a message to [EMAIL PROTECTED] from my OperaMail account.
> But it failed to be sent because "couldn't contact to domain ee.uta.edu"
> problem. OperaMail's Daemon reported this error message every 24 hours,
> until it cancelled the sending process after 72 hours.
> 
> But I successfully sent that message from my Yahoo account. What's the
> problem? Is it a DNS problem? I mean, Was OperaMail unable to resolve
> DNS?
> 
> And here is the error.dat message in Operamail's response:
> 
> Reporting-MTA: dns; operamail.com
> Final-Recipient: rfc822;[EMAIL PROTECTED]
> Action: failed
> Status: 5.0.0
> Last-Attempt-Date: Sat, 24 Feb 2001 16:52:06 -0500
> 
> I will be thankful for any comments.
> Mohammed

The parameters for the mailer daemon software that controls these 
actions are set by the system administrators at each provider or 
network.  Some mail servers are set to wait longer for a response 
from the receiving mail server, while other sending servers wait less 
time for a response.

What you encountered is a service, operamail.com, that apparently has 
it's mail server set to only wait for the proper protocol response 
for a very brief time and then the software is set to bounce the 
message if it does not get an expected answer from the recipient's 
server.

I have the same situation with the mailer daemon from the host where 
I have my ashlists.org located.  It does not wait long for an answer. 
 If the recipient's site is busy or has a brief time out, then that 
message I or my majordomo is sending is going to bounce.

Other mailer daemon software settings, such as your own ISP, may be 
set more generous.  It might wait a second or two longer for a 
response and often only a second more wait can make the difference.  
Your own ISP's mailer daemon may also be set to defer messages that 
encounter busy signals or time outs and might store the message and 
try to send it again later on an automatic time table.  That too is 
often a decision of the system administrator.

So to summarize, this is just an individual software setting decision 
on the part of the system administrators all around the Internet.


Alan
[EMAIL PROTECTED]


Reply via email to