| Author |
|
raindm
Groupie
Joined: 31 January 2008
Location: Israel
Online Status: Offline
Posts: 44
|
| Posted: 31 January 2008 at 3:46am | IP Logged
|
|
|
Hello
I am trying to send using Direct Send .
I receive a lot of the following error:
DNS cache states all SMTP MXes for the domain "domainName.com" are not available or broken.
I receive this from different domains.
What does this error means?
I couldn't find description for this.
|
| Back to Top |
|
| |
Andrew
AfterLogic Support
Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189
|
| Posted: 31 January 2008 at 4:04am | IP Logged
|
|
|
This error means MX record cannot be obtained for the domain your application try to send a message to. In other words, there is no such domain or that domain is not a valid e-mail domain.
Have you tried to send messages to those domains through a relay SMTP server via other e-mail clients like MS Outlook or Outlook Express?
Best regards,
Andrew
|
| Back to Top |
|
| |
raindm
Groupie
Joined: 31 January 2008
Location: Israel
Online Status: Offline
Posts: 44
|
| Posted: 31 January 2008 at 5:55am | IP Logged
|
|
|
Andrew wrote:
This error means MX record cannot be obtained for the domain your application try to send a message to. In other words, there is no such domain or that domain is not a valid e-mail domain.
Have you tried to send messages to those domains through a relay SMTP server via other e-mail clients like MS Outlook or Outlook Express?
Best regards,
Andrew |
|
|
Yes, i have tried and it worked (With Outlook).
The Domain names are valid for sure.. (like yahoo.com).
Maybe i am trying to send too many at a time, but shouldn't i receive different error message like "Cannot establish connection at this time" or something like that?
|
| Back to Top |
|
| |
Andrew
AfterLogic Support
Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189
|
| Posted: 31 January 2008 at 6:34am | IP Logged
|
|
|
Is the relay SMTP server you tried to send messages via MS Outlook through located in the same network your application powered by MailBee.NET Objects located in?
Perhaps, this issue caused by the local DNS server used in your
network. Please run nslookup utility on the workstation/server your
application powered by MailBee.NET Objects is installed on and type
the following commands:
You'll get 3 MX records for google.com domain. Then type your own domain name which causes the issue and check the result. If nslookup utility is not able to obtain MX records, you should check your DNS server configuration.
It's important to run nslookup on the same workstation/server the issue with direct sending happens on.
Best regards,
Andrew
|
| Back to Top |
|
| |
raindm
Groupie
Joined: 31 January 2008
Location: Israel
Online Status: Offline
Posts: 44
|
| Posted: 04 February 2008 at 2:26am | IP Logged
|
|
|
Hello
Thank you very much for the reply.
I tried the following and I see the MX records even while I get the error.
The Scenario:
I load my Sender.
I set it to Direct send and manually set my ISP DNS server (i also tried with other free dns servers (
I start sending e-mails that end with yahoo.com..
I send like 15 threads.
After like 30-200 e-mails i start receiving:
DNS cache states all SMTP MXes for the domain yahoo.com" are not available or broken
When this happens i get all yahoo emails fail and this is process happens VERY fast like 1000 e-mails for 3seconds which might mean that MailBee isn't truly accessing the DNS server since the reply is happening too fast.
While getting the error I loading nslookup and typed:
Set type=mx
Yahoo.com
And I always received the MX records.
Remember this happens only for a few specific domains: like yahoo.com,012.net, bezeqint.net.. not to all of them.
It start sending correctly and after sending like 30-200 e-mails it starts with the error for all the rest of the e-mails.
I tried many things including add Reverse DNS into my ISP DNS server, Changing configurations, etc..
I do not know what is causing this.
|
| Back to Top |
|
| |
Andrew
AfterLogic Support
Joined: 28 April 2006
Location: United States
Online Status: Offline
Posts: 1189
|
| Posted: 04 February 2008 at 6:27am | IP Logged
|
|
|
We're investigating the issue now.
What is the exact version of MailBee.NET.dll you use? You can use Message.Version property to learn it.
Is it possible to let us reproduce the issue directly? For instance, Remote Desktop / Terminal Services access to your server the issue happens on?
Best regards,
Andrew
|
| Back to Top |
|
| |
raindm
Groupie
Joined: 31 January 2008
Location: Israel
Online Status: Offline
Posts: 44
|
| Posted: 04 February 2008 at 10:30am | IP Logged
|
|
|
version: 3.0.2.79
I'll send you information regarding your request in a private message.
Thank you!
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 06 February 2008 at 7:07am | IP Logged
|
|
|
The conclusion: the problem was caused by the mail server which stopped accepting connections from your application due to too large number of simultaneous connections being made. Reducing the number of sending threads should help.
Regards,
Alex
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: What does this error means.
Privacy policy |
Refund policy