I can receive but not send email

Hi Willebug,

Since it's outgoing mail, your router/firewall shouldn't be involved, nor should the dns service.

First of all, a few questions:

What email client are you using?  I presume Pegasus is one and I'm anticipating Outlook or Outlook Express as others, but if you let us know, we may be better able to help.  If we focus on one and get the configuration right, it will probably answer the questions about configuring one of the other ones.

Also, are you trying to set up Mercury as a stand-alone server or as as a relaying client (via your ISP)?

The following link may be helpful.  It's a Mercury email server setup overview by someone running the same server (see http://www.btofaq.net/articles/servers/mercury.html)  There is a small section on each of 'Outgoing Mail' and 'Email Client Configuration'.

I would like to use outlook and if pegasus/mercury has a webmail interface I would like to use that for away from home use.  I would like to use mercury as a stand-alone server that can authenticate smtp and send email to non-local addresses.  Hopefully I've given enough info to start the wheels turning.  If not let me know.

Assuming your trying to send mail through your own mail server..

Have you verified that your ISP isn't blocking your smtp port (25) ??

Some providers do. If they are the only way around it is to either ask them "nicely" to enable it (they may or may not and it may add a fee to your account) or see about using a hosted mail account.

IF you're trying to send mail through your-domain.com's host, you may need to set your smtp setting on your client
to reflect your ISP's mail path (usually mail.your-provider.com)

Is there any way to know besides calling them?  I have asked them several times about blocking ports and they always tell me that they don't.  Is there something fundamental that I may be missing?  Is there an entry I need to put into my hosts file or something basic that I should know about all this?  I feel like I'm missing something simple.  I tried this with several email clients now and always come up with the same result... Can receive but can't send.  I am trying to use my computer to do smtp.  

Very good point from ken.  Given that you had the same problem with MailEnable, you should confirm with your ISP that you can send mail via smtp.  If this is the case, you can either receive mail on your server (as you're doing now) and send it via your ISP SMTP (with you@yourdomain.com in the 'from email' and 'reply to' fields) or use an SMTP relay service for outgoing mail (ie. www.authsmtp.com or www.smtp.com).

If it's not the case, there must be some other configuration problem.  Can you give us some info about how you configured Outlook?  Ie. what type of server did you select?  If pop/smtp, what did you list as your incoming and outgoing servers, etc.?

Ken, this is sort of a continuation of another post: https://www.experts-exchange.com/questions/21099096/Problems-hosting-website-and-email-server-from-home.html.  If you read that, it might give you a little more background.  As I've said to willebug, mail servers aren't really my area (I have a little experience with Exchange, that's it), so maybe you can help him more than I can.

what OS are you running on your server

what email server are you using

Verify that port 25 is up and running

In Outlook I have set in my pop server 192.168.1.101 as my pop server and willebug.com as my smtp server.  Default ports for both of those.  Usernames and passwords all around are correct.  When I send an email I go to mercury and even with mailenable it said it got the message but could'nt send it because it couldnt establish a connection with the other "yahoo" name server.  I have port 25 open.  I went and did a shields up scan and port 25 and 110 are both showing open.  So I think that is ok.  I'm running xp pro.  I have both mercury and mailenable at my disposal but can't get either to cooperate and send an email out.

Since the SMTP server is on your LAN, try using either the IP address (192.168.1.101 or the server name, ie. 'server' if you have DNS running on your LAN).

Sounds like that's not the problem, but it's worth a try.

Would my dns entries at dyn-dns have anything to do with the problems I'm having?  I got the website name through yahoo and got dns service through dyn-dns because I didn't have a static ip when I first got it.  I had cable so I had to find an alternative.  I since switched to dsl and am not sure if I have all the settings in my dns records correct.  Any idea what they should be?  my domain is willebug.com.  I have mx record willebug.com pointing to willebug.com and also mail.willebug.com pointing to willebug.com.  2 CNAMES:  www and ftp .willebug.com pointing to willebug.com and the A NAME of willebug.com pointing to my static ip address.  I am pretty sure that is all correct but I wanted to make all that known to be sure its right.

Unfortunately I tried that as well with same results.  Seems the two are interchangeable from home.  However when I put willebug.com as my pop server it never logs on...  Does that give any insight?

The DNS for your domain only deals with incoming traffic, ie. resolves willebug.com to your IP address.  If your website is available from the internet (it is) and you can get incoming mail to you@willebug.com, then your DNS is set up correctly.

humeniuk: very informative .. though I'm more geared for Linux and Sendmail heh

willebug: I've noticed the following from your other post.

>  I have the mail server set up for port 81.

This could be part of your problem for 2 reasons

1) services are designed to work on pre-determined ports, to change this requires that you ensure that the port you desire to use isn't assigned to any other service, then configuration changes to ensure things work as they sure (it's usually easier and desired to leave the ports alone unless you have a specific need to service.

2) the port you defined (81) is the port that's used for DNS .. ie you're going to have problems.

.. what steps did you take in changing the port for smtp?

If your computer can't find the POP server at willebug.com but can find it at 192.168.1.101, then it won't be able to find your SMTP server at willebug.com but will be able to find it at 192.168.1.101.  I would set both your POP server and SMTP server to use the IP address.  If you still can't send mail, there is an additional problem, but if we solve that problem we won't know it because your computer still won't be able to find the SMTP server on your LAN.

Just did a test to make sure I can receive again and it is still working.  

As a test, switch your SMTP in Outlook to the IP address and see if you can send me an email (address in my profile).

I set them both to 192.168.1.101 and the test settings completes all tests and I receive the test email from myself.  Also I have made some changes since the post you are referring to ken.  I have smtp on port 25 with 26 as an alt.  I have tried to keep everything as default due to the reason of conflicting services/ports.

Ok I sent an email to you.  Well I tried anyways.

Did you get an error message?

Not from outlook.  It is communicating with mercury fine.  Mercury however gave me an error.  It says Temp Error 249 (temporary mx resolution error) resolving qmail.com.  It says that for every email I've tried to send.

Mailenable would give me simliar messages when sending email.  My client would communicate fine it just wouldnt send the mail due to some communication error with a name server.

> williebug:  Would my dns entries at dyn-dns have anything to do with the problems I'm having?
> humeniuk:  The DNS for your domain only deals with incoming traffic, ie. resolves willebug.com

Actually I may have to disagree with humeniuk on this one.

I'm assuming the DNS for your computers (router etc) is set to the DNS of your provider.

If this is the case then it's going to resolve to what ever is in the name server assigned for the domain willebug.com

"IF" your dns's MX record isn't setup properly then this could be part of your issue.

as humeniuk suggested  try assigning 192.168.1.101 as both pop3 and smtp and see if that clears things up.
Note that this may cause issues with some domains since reverse IP lookups will not resolve to the domain the mail would be sent from and as such may be dropped (earthlink, frontier, aol, and msn have for some god for saken reason started doing this)

I stand corrected.

So should I put my static ip in for the dns name server in my configuration?

>  So should I put my static ip in for the dns name server in my configuration?

No, you should put in the ip or domain information you used for the MX record *if * one exists.

But to see if it works simply use your local ip for your pop3 and smtp settings on your client, and send a email to a hotmail or yahoo account (if you don't have one, get one.. they're great for testing your email servers if you think you are having problems)

KC

humeniuk:

>  I stand corrected.

bah, you've handled yourself quite well from what I've seen ;)

Thank you, Ken  :-)

In the words of Marshall McLuhan (I think), "if you don't like these opinions, I have others".

> "if you don't like these opinions, I have others".

ROFL .. I just may use that heh

Well I tried sending to human, my yahoo, my earthlink, my hotmail, my work email.  All returned the same result.  It says Temp Error 249 (temporary mx resolution error) resolving *.com. * = every domain I tried sending email to.  

hmmm

what is used for the smtp setting on your client ?

> temporary mx resolution error

Seems that there may be a issue with the MX record of your DNS listing(s)

If you have access to the configuration, post it so we can take a look at what you used.

Host                         TTL     TYPE      DATA
willebug.com            60       A           ***.**.***.***
mail.willebug.com    43200  MX         10 willebug.com
willebug.com           43200  MX          5 willebug.com

I also have some CNAMES but I'm not sure they will matter.

www & ftp. willebug.com 43200   CNAME willebug.com

I hope this is what you are after.  I'm not sure what you mean by settings in client.  Do you mean outlook or mercury?  And if you do mean mercury I'll have to figure out exactly what you need out of there.  It's not very user friendly.

try adding :


williebug.com 60 A 65.41.196.189
mail   A   65.41.196.189

Note: it will take a few days untill your DNS provider updates the record, then you have to wait until the rest of the world does

I'm not sure I understand that.  I have willebug.com 60 A ip address.  Are you saying add another mx record?  Or am I missing the point?

Willebug - if you are trying Ken's solution and waiting a few days for DNS propagation, let us know.  Good luck.

Yes I am waiting for that.  Is that going to affect the syntax of my email address?  Should it still be *@willebug.com or *@mail.willebug.com

@willebug.com

don't forget , your server is going to need to be setup to respond as both willebug.com and mail.willebug.com

I'm not sure how that would be done in windows as I don' t use it for this, but humeniuk should be able to assist you on it

Is there any need to rename my computer for this to work?  I have it named willserverhome right now but I didn't know if that would have anything to do with it.

While I'm waiting I'll try to pick your brains and see if there is anything else I'm missing.  Like I said before I feel that there is something simple/basic I'm missing.  I'm also going to put in a call to my isp today to see if they block port 25.  Anything in specific I need to ask them?

>  Is there any need to rename my computer for this to work?

Not usually

> Anything in specific I need to ask them?

1) are they blocking port 25
2) if you'll be able to send mail from your own network, or if it will need to be routed through theirs.

(smtp = mail.your-isp.com instead of mail.willebug.com)

That depends on what your terms of service with them is.  A lot of ISP's don't allow web or mail servers.  If they don't allow them (you may want to look into this first, either on their website or your contract with them), they might not be glad to hear from you.  If you want to find out, though, all you can do is ask.  I would tell them that you are CONSIDERING setting up an SMTP server so that you can send mail from a domain that you own and ask them if they are blocking port 25.

As for it being something simple/basic, Ken's DNS solution would qualify :-)

<< if you'll be able to send mail from your own network, or if it will need to be routed through theirs. >>

If that is the case, you can also configure Mercury as an SMTP relay server for outgoing mail.

> A lot of ISP's don't allow web or mail servers

This is very true.. Actually the way I'd approach them is "you're thinking about setting one up for learning (hobby) and you want to make sure it's ok with them" telling them "you're starting collage soon, and wanted to try to get a head start so you don't feel over whelmed" may be good for brownie points.

But since you've got DSL you "MAY" be ok though port 25 may be a issue as sometimes it's only enabled for commercial accounts.

Note: not all do this

In the case of port 25 not being available would another port be an alternative?  I am on hold with them right now.  My ISP is sprint if you guys know if they block port 25 or not.  I have asked them several times before about block ports and the answer was always no.  Maybe I'm just not asking them the right way I guess.

>  My ISP is sprint if you guys know if they block port 25 or not

ooooooo Sprint

Well sprint is part of Earthlink, which means you may need to use mail.spint.com (or whatever) for your smtp setting on your client.  you should still ask if you'll be able to sent through your own email server (port 25) but I believe you'll need to use their gateway.

BTW - Ken's clearly more of a diplomat than me, so use his approach rather than mine . . . I would.

Switching to an alternate port might help, depending on how careful and watchful your ISP is.

<< I have asked them several times before about block ports and the answer was always no >>
Then they probably don't.  In my experience, few ISP's do, they prefer to monitor your traffic and send you nasty letters.  For example, if you aren't allowed to run a web server, but you have lots & lots of traffic coming in on Port 80, you can bet you'll hear about it.

I dont' know about what you're using.. but with Sendmail (under linux anyway) you can configure it to send through another network instead of the local network.

perhaps humeniuk  knows how to do it with what you're using for your email server.. else <google> ;)

It will be easier just to set your client to use whatever needs to be used.

<< Well sprint is part of Earthlink, which means you may need to use mail.spint.com (or whatever) for your smtp setting on your client.  you should still ask if you'll be able to sent through your own email server (port 25) but I believe you'll need to use their gateway. >>

This is certainly your easiest solution, although you don't get to have the fun of setting up and operating the SMTP part of your server . . . you are having fun, aren't you?  As mentioned abover, remember that you can use your server for incoming mail and Sprint for outgoing mail and still have your domain email address (ie. willebug@willebug.com) listed as the from and reply-to email.

The other alternative, as mentioned is to set up your server for SMTP relay through the Sprint server.

<<  perhaps humeniuk  knows how to do it with what you're using for your email server.. else <google> ;)   >>

Alas, Ken, I don't know how to do it with Mercury, I only know that it can be done . . . thanks to Google.

Mercury is free software, but it costs $ to license the manual (interesting approach), to the tune of about $110/yr.  I've found a few Mercury newsgroups, but they are not as useful as one might hope.  Not many references to Mercury config on E-E either.

Yeah I even tried to use my earthlink smtp as my server and it was giving me the same errors.  So this further leads me to belive that something else isnt right.  I talked to sprint and they assured me NO PORT BLOCKING!!!  So I'm gonna believe them this time.  He even mentioned that lots of people do this so maybe there is something else I/we aren't thinking of.  You guys have been a great help by the way.  Any suggestions on an alternative email client???  Which one would be the easiest to use between mail enable and mercury.  

> Any suggestions on an alternative email client???

You have IE already (it comes with windows)
If you can get it to work, then either stick with that or try Thunderbird  http://www.mozilla.org

If "mercury" is your email server (I don't know what you're using)
other than sendmail, and the typical "MS" solutions, I don't know

Right, I would stick with Outlook for now.  If you can't send mail using your ISP's SMTP server then your problems aren't with your server.  I'm sure you can get proper email client config from their website or support.  If you choose to dump Outlook, I also like Thunderbird.

Well I was wondering between mail enable, mercury, or other alternative for server software.  I am still considering that I have something wrong with my router maybe.  Is that even a possibility?  I cannot connect to mail.willebug.com or willebug.com or my ip address to use as a pop server from work using outlook.  Does that suggest anything?

I think that suggests that Ken's DNS solution may be the right one.

I read some documentation about adding a PTR record?  Any ideas as to whether this might help out or not?  I also read something about being on a spam list.  

I don't think it's you're router (the outgoing problem), because you are getting past your router when you try to send, even if the send isn't successful.  Your router could be blocking you POP access to the mail server from your office, if you don't have port 110 forwarding to your server's internal IP (same as port 80 and 25).

The DNS solution that Ken suggested seems like a good bet to solve both of the problems, but unfortunately you're going to have to way (probably a couple of days), to see.

Just saw this above:

<< don't forget , your server is going to need to be setup to respond as both willebug.com and mail.willebug.com

I'm not sure how that would be done in windows as I don' t use it for this, but humeniuk should be able to assist you on it >>

Do you have that set up now or do you need some directions?

Yeah I am definately a beginner at this and please treat me as if I know nothing.  So help please!!!

Hmm . . . could be interesting with WinXP.  I don't have IIS on XP in front of me, so I'm not entirely certain.  I'm used to IIS 6 with Win2k3 and IIS 5 with Win2k.  I'm going to do a little research and get back to you.

Ok.  Thanks.

Am I supposed to be running my virtual smtp sever in IIS for this???

No, virtual SMTP is something else.  You don't want to use that with a third-party mail server.

Regarding this:
<< don't forget , your server is going to need to be setup to respond as both willebug.com and mail.willebug.com
I'm not sure how that would be done in windows as I don' t use it for this, but humeniuk should be able to assist you on it >>
This may not be applicable to WinXP/IIS5.  This sort of thing is generally done in a Win2k3/IIS6 environment to deal with multiple websites, virtual servers, etc.  Given that WinXP/IIS only allows one website, you don't have the ability to create host headers, etc.  Likewise, you don't have DNS controls as you do in the server example.

Having said that, you need to make sure that your router/firewall is forwarding the correct ports (25,110,80) to the server's local IP - as you have done.  Because there is one default website there, I suspect that there is no need for further configuration to make your server respond to port 80 traffic, because there is one web server platform (IIS) and one website (the default site).  This would likely be true of your mail server as well.  The DNS suggestions that Ken made will route mail.willebug.com traffic to your public IP, your router will forward traffic on the mail ports to your server's local IP where your mail server, if properly configured, will be listening for and receiving traffic on that port.

Disclaimer: I'm not 100% sure about this as I haven't used WinXP for this purpose, so don't take this as a finite answer.  If anyone has anything to add (either to confirm or disagree with this), please speak up.

>  Am I supposed to be running my virtual smtp sever in IIS for this???

?? SMTP and IIS are two different things.. If you're refering to "web based email (aka webmail)"
you'll first need to get your smtp issues resolved.

Virtual SMTP allows 1 smtp server to act as mutiple servers (xyz.com, 123.net, williebug.com, etc) at the same time.

> You don't want to use that with a third-party mail server.

100% true..

If this is your desired path, then I'd recommend either switching to a MS solution (exchange etc) or Sendmail (something that's better documented (ok so Sendmail docs leave alot to be desired), mature, and stable ( hmm, ok so maybe MS might be left behind there too. ;) )

My original recommendation (in the last post) of MailEnable was largely due to the fact that there is good documentation & support available (and free, unlike Exchange).  Willebug switched to Mercury (correct me if I'm wrong) because he was having this same problem with MailEnable.  That fact (same problem common to both mail server platforms) makes me hopeful that the DNS solution will be the proper resolution rather than a server config solution (esp. since I don't know anything about Mercury and can't spend $110 on the manual).

Never tried MailEnable so I can't say..

"IF" the DNS doesn't fix the problem, then my suggestion would be for him to find someone willing to spend "alot" of time, and start from scratch. Or better yet maybe get someone to walk him through (start to finish)

On a different note

DNS seems to be complete on mail.williebug.com

*assuming the DNS he's using for his home connection updated the information

willie: try to ping mail.williebug.com .. "IF" you get a reply, try to send mail using it for you sntp setting

the only other issue he may have will be with reverse ip lookups.

For this he (willie) will need his ISP to make the necessary associations to willie.com and mail.willie.com

I pinged mail.willebug.com and didn't get a request.  Of course I'm doing it from work (my only way to check it from outside the network except from my g/f's house who is out of town for the week) and there is the possibility they block it since it's a government computer at work.  Same for willebug.com.  My dns settings are telling me that the next check will be saturday so I guess it will be at least until then before everything settles there correct?  As for reverse ip lookups...  What do I need to tell them.  I realize I've basically had you guys set this up for me.  And I greatly appreciate the help.  Had no idea it was going to be such a project.  Thanks again for all the help guys.

I pinged both willebug.com and mail.willebug.com (resolved to proper IP address).

Also, I may have discovered a cause for some of these problems.  http://mail.willebug.com:8080 goes to the ArGoSoft Mail Server welcome/log-in screen. So, it appears you still have the ArGoSoft mail server installed and running, which can interfere with the Mercury mail server in several ways, the most obvious being that both are listening for port 25/110 traffic on the server.

You should either disable (or preferably uninstall) ArGoSoft, MailEnable and any other mail server software you have running on your server except for Mercury.

You're right, it could be blocked or you may still be waiting for DNS propagation at that location.  You can try going to www.network-tools.com and you should be able to ping from there.  I did a trace as well and it routes to your proper IP address.

<< the only other issue he may have will be with reverse ip lookups.  For this he (willie) will need his ISP to make the necessary associations to willie.com and mail.willie.com >>
If they will do this for him.

But first, get rid of the other mail server software and test it out.  If you want to provide us with a willebug.com email address (here or by email), we could send you a test.

Turns out our work domain doesn't allow ping option.  I was unable to ping any domain.  So I guess I can't really do that from here.

If you use www.network-tools.com, you ping from their server, not your location.  The results are given to you via the web.

Ok the ping worked fine.  I will set up an email account for you both.  Human@willebug.com password human and ken@willebug.com password ken.

<< the only other issue he may have will be with reverse ip lookups.  For this he (willie) will need his ISP to make the necessary associations to willie.com and mail.willie.com >>

> If they will do this for him.

Sheesh I thought I was the pestemist ;)

You are right though.. w/ earthlink it is a major "IF" they may not even be willing to hand over deligation to his existing DNS provider (if they'll even accept the request on that end) at which point he'll be pretty much looking at roughing it

My shrink says I have to start looking at the bright side (yes, I see a shrink, but don't worry, it's just one of those silly 'court-ordered' things).

Ahem.

On that note . . .

I have configured Outlook to use the account you've set up.  Using mail.willebug.com as the mail server (also works with willebug.com or your public IP address), I am able to find both the incoming (POP) and outgoing (SMTP) servers.  However, I am not able to log on to either of them - error message: Unable to logon to the incoming mail server (POP3).  Please verify the settings in the User Name, Password and E-mail fields".  I tried both human and human@willebug.com as usernames.

BTW - the message is NOT timing out, the server is rejecting the connection.

I presume you haven't configured the mail server to use a secure (SSL connection), have you?

Also, have you removed the other mail server programs yet?  Or do you have to do that later at home?

Yeah I'm still at work.  I'll have to take care of all that stuff at home.  So you want me to go back to which program???  Mercury, mail enable???  Just let me know and I'll make the change.

I don't think it matters which one, it's more a matter of making sure there aren't two or more mail server platforms running on the machine at any given time.  As of right now, I can't log in with the account info you gave me, but if you created the test account on Mercury and ArGoSoft is answering the request, it makes sense that my username/password would be rejected.

So, select one mail server platform, uninstall the other(s), and make sure whichever one remains has an account with the username/password you set up.

I created the addresses for human and ken with the above passwords.  I also made you both sysadmins.  Do your worst :-)

willebug erm,

You do realize that anybody who stumbles accross this posting now not only has the login information for either/both accounts, but also have admin rights ..

>  Do your worst

You could very well wind up with a paper weight if you don't kill the privelages,
or atleast change the passwords/logins

Just a friendly suggestion

I would suggest you change the passwords right away and email us the new passwords.  You just created two admin accounts for a mail server exposed to the internet and posted the usernames/passwords in a public forum.  This is a significant security problem.

(ie. someone else might do their worst)

Ok i changed the permission levels.  You are both just users.  Smack me on the hand why dontcha ;)  I see the error of my ways.

Which server platform did you elect to keep?

I am using mail enable.  And I believe I got rid of everything with the other two after several restarts.  Pesky programs didn't want to go away.

> This is a significant security problem.

ya think??  ;)


Willebug,

Seriously, you didn't just make 1 serious mistake you made 3-4 of them in one foul swoop

I strongly suggest before you get too into playing w/ the server you review (buy) some network/security manuals

and yes there are "Dummy Guides" on the subject.

I have connected to the POP server and received the automated 'your new email account has been activated' message.

However, I can't send mail ("unable to connect to the outgoing mail server").  I'm going to try some variations in the client (Outlook) config and see if that solves it.

No luck.  I still can't connect to the SMTP.  Also, test emails sent from an outside email address to human@willebug.com never show up in my inbox.  Willebug, you may want to configure your Outlook to access the human@willebug.com account on the server via the network (rather than the internet) - use the server's local IP for the incoming and outgoing server names.  See if the test emails I sent made it to the server (I doubt it, but it's worth a look).

Ken, do you think there is a DNS explanation for this (ie. reverse IP lookups)?  Should Willebug speak to his ISP about this as you suggested above?

It's either that or a server config problem.

> do you think there is a DNS explanation

Are you getting any errors, server messages?

at this point I'd have to say configuration issue

No errors or server messages.  No return message "your email couldn't be delivered, etc."

If it's config, at least we have more documentation with MailEnable than with Mercury.  I'll check back later, willebug, when I've had a chance to look at some ME config info.

Ok thanks.  I actually looked at a pdf that came with it.  It didn't mention anything about it being able to run on xp at all.  Could that be the underlying problem?  That it uses some server components/services that xp pro doesn't have?

O
K

I sent 1 message to 2 addresses

ken@willebug.com
and a address on my network

willebug.com was delivered OK (which is good since it's local)

However the "CC" didn't get delivered (nor did it error out) which leads me to believe your issue is configuration related.

NOTE: the field "server needs to be authenticated" needs to be checked.. but not SSL

one thing I did notice from the header of the message to the willebug.com account is

Received: from ([127.0.0.1]) <---- This should have been set to the IP I sent from

I'd suggest you review your configuration

I put in a call to Sprint/Earthlink about the PTR record.  They said that they couldn't do it with the type of service I have now.  So I am going to just give up on this for now.  I was able to get outbound smtp service from my dns provider for a small charge and that will suffice for now.  I was kinda hoping I would be able to do this myself but it just turned out to be too big of a task to make it happen.  I want to thank both of you for you help.

I'm sorry to hear it isn't going to work out.

Good choice.

I am using Mercury/32. I could receive the mails through the server and i could send the mail to internal machines. But i could not sent the mail to outside. from mercury SMTP Client (end-to-end version) getting the following error message

19:39:37: processing job MO000160
Temporary error 249 (temporary MX resolution error) resolving 'msa.hinet.net'.
19:40:57: processing job MO000002
Temporary error 249 (temporary MX resolution error) resolving 'comcast.net'.
19:46:01: processing job MO00015F
Temporary error 249 (temporary MX resolution error) resolving 'msn.com'.
19:46:01: processing job MO00053A
Temporary error 249 (temporary MX resolution error) resolving 'comcast.net'.
19:48:25: processing job MO00053D
Temporary error 249 (temporary MX resolution error) resolving 'msn.com'.
19:48:25: processing job MO00053E
Temporary error 249 (temporary MX resolution error) resolving 'comcast.net'.

Can you help me to fix this problem. Also i am using ISA2004 server in this server.