Mail Client not working

Rohits.sharma

Registered
I am having issues with My OS 10.5 ::evil:: default Mail client ver 3.0.

Issue : I have account on Microsoft exchange server OS windows 2008 IIS 7. I am able to recive emails in my Mail but not able to send mail's i did a check on network , it shows it was able to authi'cate with SMTP server but still mails are not going out. Can any1 help me in this. Thanks
 
...

Issue : I have account on Microsoft exchange server OS windows 2008 IIS 7. I am able to recive emails in my Mail but not able to send mail's i did a check on network , it shows it was able to authi'cate with SMTP server but still mails are not going out. ...[/FONT]
If you received messages from an Exchange server, then give yourself a pat on the back and give your IT staff a wet sloppy kiss. Your Exchange server issues are probably solved. The SMTP issue is different. It is not clear if you are trying to send messages from your firm's domain or from an outside domain. It is common practice for ISP's to block access to foreign SMTP servers--particularly on default Port 25. Some allow access on secure Port 567.

Blocked SMTP ports is a security measure meant to thwart spammers. If your SMTP access is blocked at work, then you may need to take it up with your IT staff. Every Exchange server is setup differently. No one outside your firm can give you the information needed to work through the issues.
 
Thanks for the reply dude, but the irony is :eek: m frm IT team but Mail team is dfrnt. M sending mails from my exchange server primary domain whn i check my status :

1) Connection Status : Mail was able to connect to the internet
Connection and login to server succeeded
2) In log it shows that it worked on thesePort 23, 995

Evn i thought of Port but this is not blocked frm my router or my office router.
Any other thought
 
Please make your posts in English. There is no need to use SMS text message shortcuts here. What's more, it makes your posts unnecessarily difficult to read.

At any rate, your most recent post confuses the clarity that I thought you had in your original post. By "Mail team," do you mean email team or "[MacOS X] Mail [email client] team."

It is not just about blocking ports. In Star Trek terms, Exchange setups come in infinite variety in infinite combinations. You need to get with the people who manage your Exchange server to learn which of those combinations pertain to your setup.
 
If your Exchange server is set up to disallow open relaying (relaying without authentication), then you cannot use your Exchange server to send email (SMTP) while you are outside of the network that the Exchange server is a member of.

If you configure a Windows computer to use the Exchange server as an SMTP server, can you send email? What I mean is, have you tried using another computer? This will tell you whether it's a Mac mail issue on your Macintosh, or whether it's a configuration issue with either your computer or the Exchange server.

Like MisterMe said, Exchange server setups vary from place to place -- one Exchange server may be infinitely different in terms of setup and configuration than another Exchange server. There isn't a single, definitive "fix" for your problem because we have no clue about the configuration of your Exchange server.

You will need to speak with the person or team that is in charge of your Exchange server at work to get more clarification on the exact setup of Exchange.
 
In the OS X Mail application there is a "Connection Doctor" in the Mail's Windows menu item. When you launch that you can look at the details of that to see what OS X is doing to talk to the SMTP server and report that back to your IT staff. This way they have all the information they may need to help.
 
As i have written in my first post, i am able to receive emails but enable to send and also did a check from Connection Doctor:
1) Connection Status : Mail was able to connect to the internet
Connection and login to server succeeded
2) In Details it shows that it worked on these Port 23, 995.
Which are not blocked, and for authentication i am using Password/Login Auth. I am able to use Entourage maybe because its part of Microsoft this client is not. What all details you guys want me to dig in, i will do. I thing more we have recently upgrade our exchange server from 2003 to 2008. Thanks fellas.
 
...i am using Password/Login Auth.
Is this the proper authentication scheme? Is your Exchange server using Kerberos or some other authentication scheme? This is information you need to get from your Exchange server IT team.

Also, Apple's Mail application uses IMAP or POP to connect to Exchange servers -- it doesn't use Microsoft's Exchange protocol, like Entourage (and Outlook on a PC) use. That means that just because Entourage and Outlook connect, Mail uses a different communication scheme and the fact that Outlook and Entourage work doesn't mean that Mail.app doesn't work -- it just means that you may be connecting improperly. Is IMAP or POP active and running on your Exchange server? Is SMTP active and running on your Exchange server? Again, this is information only your IT team can give you -- we have no clue how your Exchange server is configured.
 
Yes it is, and i am using Mail version 3.5 which supports exchange
Yes, Mail.app supports connections to Exchange servers, but it does not use the same Exchange communication protocol that Outlook and Entourage use.

Outlook and Entourage use Microsoft's closed-source, proprietary Exchange protocol. This protocol is not openly published and documented, and only Microsoft themselves know how it's implemented. Certain companies have reverse-engineered as much of it as possible.

Apple's Mail.app does not use this Exchange protocol to make a connection to your Exchange server (yes, even when you select "Exchange" as your mail server type!). It uses a combination of IMAP, SMTP and portions of the Exchange protocol. This means that because Outlook and Entourage connect to your Exchange server, the Exchange server is properly set up to accept connections using the Microsoft Exchange communications protocol. Other applications that do not use this protocol (like Apple's Mail) may need additional support on the Exchange server side.

I said it once, and I'll say it again: I believe troubleshooting this is beyond the scope of this forum, simply because we have no idea how the Exchange server is set up. You will need to get with the guys at your company that manage the Exchange server. You may say, "Yes, IMAP, POP and SMTP are running on the server," but that still gives us no idea how those services are configured -- those services have many configuration options set on the server that may affect how Mail.app connects to the server.

Without that knowledge, we (or at least I) are no longer able to help. It's just impossible without knowing that. If you can get with your Exchange server guys and get screenshots of exactly how the IMAP, POP and SMTP connectors are configured, we can move on -- but simply saying that the services are running doesn't help.
 
You can post the screenshots with the "attachment" option when you reply here on the forum. We'd like to keep this going here at macosx.com instead of on email so that other people with similar problems can read about the solution without having to ask the same question again.
 
Back
Top