On Wed, 13 Jul 2016 08:48:49 UTC, Nelson <
nel...@nowhere.com> wrote:
> On Tue, 12 Jul 2016 21:53:23 -0400, John Varela wrote
> (in article <51W5y0sPNk52-pn2-nklPwZ577zmr@localhost>):
>
> > On Tue, 12 Jul 2016 08:28:04 UTC, Nelson <
nel...@nowhere.com> wrote:
> >
> >> On Mon, 11 Jul 2016 21:29:55 -0400, John Varela wrote
> >> (in article <51W5y0sPNk52-pn2-UbwFLkx5Gg91@localhost>):
> >>
> >>> I get dozens of spam emails every day (Verizon's spam detector is
> >>> useless). I have filters that send them to the trash, so I don't see
> >>> most of them, but some still get through.
> >>>
> >>> Sometimes, most recently this evening, Mail will crash when trying
> >>> to download from Verizon's POP server. The crash takes place before
> >>> any of the mail reaches my filters. The solution is to go to
> >>> Verizon's web site and trash all the obvious spam. Then Mail works
> >>> as it should.
> >>>
> >>> I've been trying to identify exactly which email(s) is/are the
> >>> problem, but every time I think I'm closing in on one, Mail crashes
> >>> and the suspect isn't present on the server.
> >>>
> >>> Is anyone else seeing this sort of behavior? This used to happen
> >>> maybe once a month but recently it's been more like once a week.
> >>>
> >>> El Capitan 10.11.5 and Mail.app 9.3 (3124).
> >>>
> >>>
> >>
> >> I'd start by using Mail's Activity and Connection Doctor windows to see
> >> exactly when the crash occurs. You are assuming it is a spam message
> >> that is causing the crash. Could be something else eg a corrupted Mail
> >> database.
> >
> > I'm convinced that the problem is spam because there have been at
> > least a dozen instances of this, and in every instance the problem
> > has been cleared by going to the server web site and deleting spam.
>
> Correlation is not causation :) Apparently _a_lot_ of people have
> problems with mail crashing since upgrading to the "California Named"
> OS's.
>
>
https://www.google.com/webhp#q=%2BNSInternalInconsistencyException+%2B%2
> 2malformed+address%22+Mail+crash
>
> See in particular
>
>
https://discussions.apple.com/thread/7275828?tstart=0
>
> Which sounds almost identical to your problem and discusses several
> solutions.
That does sound the same but it isn't. The suggestion to hold down
the shift key (at
https://support.apple.com/en-us/HT203542) doesn't
work because Mail crashes before the window even opens.
> > I will take a look at those windows the next time this happens. I've
> > never used them so I don't know what's in there. Note that Mail
> > crashes and can't be opened until the spam is deleted at the server
> > web site. So I can't look at those windows until after the problem
> > is cleared.
>
> Disconnect from the internet before starting mail. Then disable all
> accounts from automatic updating. Reconnect to the internet. Open the
> connection doctor window. Retrieve mail manually from one account at a
> time. Connection Doctor will give you a step by step trace of all the
> transactions between you and the server. You should be able to see
> exactly where it is crashing.
That was a good suggestion but it doesn't work, either. The first
time I tried it, one email came up and then Mail crashed, taking
Connection Doctor with it, so Connection Doctor yielded no
information. The one email that got through was harmless, and a
visit to the Verizon site showed dozens of emails to download. The
one that got through was in the middle of the pack, so there was no
way to tell which email had been the one that drashed Mail.
> My solution. Go back to Snow Leopard :) Works fine for me :)
This is becoming a daily occurrence. I have sent dozens of crash
reports to Apple, and maybe they'll fix it (there's no reason bad
data should crash the app if they simply write a little protective
code into the interface) but if they don't do it soon I'm going to
have to start using a different mail reader.
Does anyone have a recommendation for a replacement for Mail.app?
(Not Thunderbird!)
--
John Varela