Mail refuses to send emails
in [Mac Applications]
|
From: nyenyec on 31 Dec 2006 17:39 Ok, I finally found it. The key was to set NTLM authentication instead of password, since this was an Exchange Server. The other mail clients didn't make this distinction that's why I haven't paid attention to the setting. Cheers, nyenyec nyenyec wrote: > So I've given up on this a month ago, but came back now and wrote a > small Python program that stands between the SMTP server and the mail > client and logs the traffic. I found tcpdump very hard to read. > > I compared the logs from mail clients that work (Opera, Thunderbird) > and Mail.app, that doesn't. > > It seems, that Mail.app closes down the connection before even > initiating the sending of the message: > > Client connected from: ('127.0.0.1', 56669) > Connected to server XXXX on port 25 > <<<<< server <<<<< > 220 XXXX Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at > Sun, 31 Dec 2006 16:15:51 -0600 > > >>>>> local >>>>> > EHLO [127.0.0.1] > > <<<<< server <<<<< > 250-XXXX > 250-TURN > 250-ATRN > 250-SIZE > 250-ETRN > 250-PIPELINING > 250-DSN > 250-ENHANCEDSTATUSCODES > 250-8bitmime > 250-BINARYMIME > 250-CHUNKING > 250-VRFY > 250-TLS > 250-STARTTLS > 250-X-EXPS GSSAPI NTLM > 250-AUTH GSSAPI NTLM > 250-X-LINK2STATE > 250-XEXCH50 > 250 OK > > Connection closed by ('127.0.0.1', 56669) > > This is where a normail client sends AUTH. I have no idea why Mail.app > closes the connection at this point. I configured it to password > authentication. > > I simply don't know where to go from here, other than doing random > experimenting or using Outlook through Parallels. > > Any help is appreciated. > > -- nyenyec
From: Alice Faber on 31 Dec 2006 17:43
In article <1167603868.742082.297740(a)a3g2000cwd.googlegroups.com>, "nyenyec" <nyenyec(a)gmail.com> wrote: > So I've given up on this a month ago, but came back now and wrote a > small Python program that stands between the SMTP server and the mail > client and logs the traffic. I found tcpdump very hard to read. > > I compared the logs from mail clients that work (Opera, Thunderbird) > and Mail.app, that doesn't. > > It seems, that Mail.app closes down the connection before even > initiating the sending of the message: > > Client connected from: ('127.0.0.1', 56669) > Connected to server XXXX on port 25 > <<<<< server <<<<< > 220 XXXX Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at > Sun, 31 Dec 2006 16:15:51 -0600 > > >>>>> local >>>>> > EHLO [127.0.0.1] > > <<<<< server <<<<< > 250-XXXX > 250-TURN > 250-ATRN > 250-SIZE > 250-ETRN > 250-PIPELINING > 250-DSN > 250-ENHANCEDSTATUSCODES > 250-8bitmime > 250-BINARYMIME > 250-CHUNKING > 250-VRFY > 250-TLS > 250-STARTTLS > 250-X-EXPS GSSAPI NTLM > 250-AUTH GSSAPI NTLM > 250-X-LINK2STATE > 250-XEXCH50 > 250 OK > > Connection closed by ('127.0.0.1', 56669) > > This is where a normail client sends AUTH. I have no idea why Mail.app > closes the connection at this point. I configured it to password > authentication. > > I simply don't know where to go from here, other than doing random > experimenting or using Outlook through Parallels. > > Any help is appreciated. One of my users has a similar problem, with a wrinkle. He checks mail on two separate accounts on the same server. He has, as far as we can tell in the configuration screens, identical server information for both accounts. He can check mail on one account, but not the other. The only difference between the two accounts (besides the user names!) is that one has a small Inbox and the other (the one that fails) has a very large one. But, since the failure is before the actual Inbox is accessed, it's hard to know how this would make a difference. In the course of trouble-shooting, I found that Mail.app has a fixed (totally non-configurable) timeout setting, whereas other mail applications allow you to increase the timeout setting. If you want to experiment with other clients, Thunderbird is free and has pretty good IMAP support. There is a free version of Eudora as well; its IMAP support, at least the last time I used it, was not so great. So, I'd recommend Thunderbird. Give it a try, and let us know what you find. -- AF "Non Sequitur U has a really, really lousy debate team." --artyw raises the bar on rec.sport.baseball |