Search results for query: *

Things have been working great for awhile. No changes to the server at all. Just started happening for this one particular domain...but now I am seeing it for one or two other domains throughout the day, until the message expires. Not sure what could cause this...surely not related to database...

long shots welcome at this point! But no, the rDNS is pointed at my exchange. I tried the telnet again earlier and was able to send a message to that recipient. They notified me that they received it. The message is just hanging in 'retry' mode on exchange.

did an NSLOOKUP and got the MX record for the destination domain. this is just bizarre to me. Thanks for all the help so far!

Ok, i performed the workaround and asked the senders to retry again. It goes immediately to retry state. At this point, using a smarthost is not an option. We do not have any spf records published.

I went to mxtoolbox.com and did the blacklist test on their site. It said I was ok on them. What about graylisting? Could a company have our domain graylisted? Is that used very much?

The email was tried again this morning and it is still in 'retry' mode. Interesting tho, I have one more queue that is in 'rety' mode that has been sitting there for about an hour. I know this user successfully sent email to that domain before. Nothing has changed on our server, so I'm kind of...

Thanks for the telnet info. Everything appears fine when I telnet into that server. No errors reflected through the telnet session. Although I had to be a fast typer or the connection would get lost. I was able to telnet and enter commands at my leisure to my server.

Yes, we do have a rDNS record. The affected user can send email to both local and non-local recipients. It is only this one external domain that she can't get email to. I'm not real familiar with the telnet commands. But I will look that up and see what I can find out.

Your message did not reach some or all of the intended recipients. Subject: RE: Project Sent: 5/5/2008 4:15 PM The following recipient(s) cannot be reached: John Doe on 5/6/2008 4:34 PM Could not deliver the message in the time limit specified. Please retry or...

I have a user that is replying to an email outside the organization, and it is getting delayed and eventually undeliverable. I see it sitting in the queues with a 'retry' status. All other messages are going through fine. My first thought is that it's something on the other end, but is there...

Man am I glad I found this thread! Thanks AndyPeck for the link! Worked like a charm for me, too!

No I haven't found a solution yet...I had already checked to make sure he was an admin on the machine, and he is, so I don't think that is the issue. I posted this in the Exchange Server 2003 forum as well, and they suggested I delete the profile on the Exchange server itself and then add it...

I have Exchange 2003 on Windows Server 2003, and problem is with only 1 user. When he opens outlook, it prompts him 6 times to enter his username/password, and then it finally takes it and he can access his email. I have reinstalled Outlook to no avail. Do you think this is an Outlook problem...

I have Exchange 2003 on Windows Server 2003, and problem is with only 1 user. When he opens outlook, it prompts him 6 times to enter his username/password, and then it finally takes it and he can access his email. I have reinstalled Outlook to no avail. Do you think this is an Outlook problem...

Thank you very much xmsre!

I have an Exchange 2003 server on Windows 2003 Server, with about 125 users. (No fancy config, just the one server) Being a newbie to Exchange, I attended a class where the instructor suggested rebooting the Exchange server weekly. Then I read something that said it was a good idea to reboot...

rko9h, don't know if you'll see this or not, but we just implemented our new exchange server last week, and we have both server1.mydomain.com and server2.mydomain.com both pointing to the same ip address. It works like a charm! MJ

Hmmmm, might have run into some problems. Anyone know if I will have certificate issues? For example, during config, we issued certificate ourselves for mail2.mydomain.com. When I switch over, I was going to give it a different ip (one of mail1.mydomain.com) will that cause an issue if the...

Thank you wallst32 for the info! I was hoping that would be the case. jpm121, I was also hoping we could (eventually) rid the mail.xx.tld address! rko9h, I had thought about that, but we don't want to leave the old server up and running. -MJ

Hello, I am in the middle of configuring a brand new exchange 2003 server for my company. We previously just had basic pop3 server. Our current pop3 server is mail.mydomain.com and my new exchange box is mail2.mydomain.com Before I came onboard, the one who configured the pop3 server had users...