Prev: Cyberduck latest update
Next: Any one ever try/use IFreeMem?
From: Tom Stiller on 4 Dec 2006 18:48
In article <1165273618.303077.324170(a)j72g2000cwa.googlegroups.com>,
"nyenyec" <nyenyec(a)gmail.com> wrote:

> There is stuff in both the console log and the system log.
> When I filter for "mail" the system log has nothing and the console log
> has a few entries.
>
> 2006-12-04 14:06:22.430 Mail[192] 0x162770c0: observer lock is held,
> postponing release. break at
> /SourceCache/Message/Message-752.3/Utilities.subproj/FoundationAdditions.m:649
> to debug
> 2006-12-04 15:03:29.441 Mail[470] Exception raised during monitored
> invocation of _fetchUnreadCountsCheckForNewMessages:, exception: ***
> -[NSConcreteData initWithBytes:length:copy:freeWhenDone:bytesAreVM:]:
> absurd length: -1, maximum size: -2147483648 bytes
> 2006-12-04 15:03:29.442 Mail[470] +[NSObject(LockingAdditions)
> clearLocks]: object 0x4ec290 still holds lock (count=1) in thread
> 0x199d400
> 2006-12-04 15:03:29.442 Mail[470] +[NSObject(LockingAdditions)
> clearLocks]: object 0x16972cb0 still holds lock (count=1) in thread
> 0x199d400
>
> But these don't correspond to the sending attempts. When I try to send
> new mails, no log entries are generated even though I get the errors in
> the GUI.

If this happened after a restart, it may indicate a problem with the
Mail application. My console log shows only two mail related entries,
each reporting the successful loading of a Mail plug-in.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF
From: Barry Margolin on 4 Dec 2006 20:13
In article
<everyday-7EA7EB.12144204122006(a)newsclstr02.news.prodigy.com>,
Gerry <everyday(a)sunrise.net> wrote:

> In article <1165262699.736148.319630(a)79g2000cws.googlegroups.com>,
> "nyenyec" <nyenyec(a)gmail.com> wrote:
>
> > Gerry wrote:
> > >
> > > Go to Mail / Preferences / Accounts / Outgoing Mail Server (SMTP) /
> > > Server Settings / Authentication / select the option that fits your
> > > service.
> >
> > That's the problem. I do have the correct server settings. The error
> > messages I get are completely bogus.
> >
> > -- nyenyec
>
> The error message is not bogus it's telling you that somewhere in your
> setup you have entered the wrong information.

Unfortunately, Mail's error messages are really poor, and it doesn't
offer any session logging.

What I've done when I've needed to troubleshoot Mail is use tcpdump from
a Terminal window to capture the actual traffic. Do this in Terminal:

sudo tcpdump -nx port 25

try to send mail using the non-SSL server, then type Control-C in the
Terminal window to stop the capture, and post the output.

--
Barry Margolin, barmar(a)alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
From: Shawn Hirn on 5 Dec 2006 01:48
In article <1165273618.303077.324170(a)j72g2000cwa.googlegroups.com>,
"nyenyec" <nyenyec(a)gmail.com> wrote:

> There is stuff in both the console log and the system log.

You need to look at the log file on each smtp server.
If you don't have the type of authority to view those logs, ask the
person who does have the authority for assistance.
From: Keith on 5 Dec 2006 03:32
On 4 Dec 2006 11:43:47 -0800, "nyenyec" <nyenyec(a)gmail.com> wrote:

>"Cannot send message using the server (null)"
>"SMTP server XXXX doesn't support authentication."

Check the addres of the SMTP mail server. You might have a space or
other character that is giving you the problem. I would applekey-a and
press backspace and retype the mail server address in the SMTP server
box.

HTH,

Keith

From: nyenyec on 31 Dec 2006 17:24
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

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Cyberduck latest update
Next: Any one ever try/use IFreeMem?