Snow Leopard "New Mail" Problem
André Berger
the upgrade to Snow Leopard hosed major parts of my system, it won't
go to sleep automatically any more etc. pp.
Mutt 1.5.19 seems to be confused too, as it will no longer report new
mail.
If I "set check_mbox_size=yes", on the other hand, it will show 51
mailboxes (of type mbox) with new mail -- while, for example, only
three of them really do. When I change to a mailbox, the number is
decreased by one as it should. So I go ahead and change things like
"N" flags on messages, quit mutt, and see the same 51 mailboxes
allegedly containing new mail the next time I start it.
I'm (still) on FileVault, if that matters. And I don't want to change
to maildir because of the overhead caused by a great number of small
files.
-Andr�
--
May as well be hung for a sheep as a lamb!
Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns.org>
iPhone <http://hvkls.dyndns.org/downloads/documentation/README-iphone.html>
Indi
> Dear all,
>
> the upgrade to Snow Leopard hosed major parts of my system, it won't
> go to sleep automatically any more etc. pp.
>
> Mutt 1.5.19 seems to be confused too, as it will no longer report new
> mail.
>
> If I "set check_mbox_size=yes", on the other hand, it will show 51
> mailboxes (of type mbox) with new mail -- while, for example, only
> three of them really do. When I change to a mailbox, the number is
> decreased by one as it should. So I go ahead and change things like
> "N" flags on messages, quit mutt, and see the same 51 mailboxes
> allegedly containing new mail the next time I start it.
>
> I'm (still) on FileVault, if that matters. And I don't want to change
> to maildir because of the overhead caused by a great number of small
> files.
>
>
Hi Andre,
You didn't mention whether you'd built mutt from source, used fink, or
the macports version. But when I upgraded to 10.6 I found it necessary to
rebuild mutt (I build it from source) as well as completely wiping macports
and reinstalling all that. Most everything works fine now except esmtp
and mplayer (dammit).
--
Indi
Sylvain Soliman
> go to sleep automatically any more etc. pp.
No problem here...
> Mutt 1.5.19 seems to be confused too, as it will no longer report new
> mail.
Using the 1.5.20 version built from macports I don't have such an issue.
(mutt-devel @1.5.20_0+compress+gdbm+headercache+imap+pop+sasl+smtp+ssl)
> I'm (still) on FileVault, if that matters. And I don't want to change
> to maildir because of the overhead caused by a great number of small
> files.
I use mostly Maildir but have a few mbox mailboxes, no difference w.r.t.
the SL update...
Best,
Sylvain
--
Sylvain Soliman <Sylvain...@RmThis.m4x.org> GPG Key: 0x0F53AF99
Co-mainteneur de PilotGOne http://minas.ithil.org/pilotgone/
Page personelle http://contraintes.inria.fr/~soliman/
Erwan David
>> the upgrade to Snow Leopard hosed major parts of my system, it won't
>> go to sleep automatically any more etc. pp.
>
> No problem here...
>
>> Mutt 1.5.19 seems to be confused too, as it will no longer report new
>> mail.
>
> Using the 1.5.20 version built from macports I don't have such an issue.
>
> (mutt-devel @1.5.20_0+compress+gdbm+headercache+imap+pop+sasl+smtp+ssl)
+compress did not build for me under macosX. And I prefer tokyocabinet
to gdbm : much faster.
--
Le travail n'est pas une bonne chose. Si �a l'�tait,
les riches l'auraient accapar�
Erwan David
>> the upgrade to Snow Leopard hosed major parts of my system, it won't
>> go to sleep automatically any more etc. pp.
>
> No problem here...
>
>> Mutt 1.5.19 seems to be confused too, as it will no longer report new
>> mail.
>
> Using the 1.5.20 version built from macports I don't have such an issue.
>
> (mutt-devel @1.5.20_0+compress+gdbm+headercache+imap+pop+sasl+smtp+ssl)
+compress did not build for me under snow leopard.
Sylvain Soliman
> +compress did not build for me under snow leopard.
Through macports?
Did build for me without trouble :/
> And I prefer tokyocabinet to gdbm : much faster.
Thanks, I'll give it a look ;)
André Berger
I'm on MacPorts mutt-devel
@1.5.20_1+gpgme+headercache+idn+imap+nntp+pop+sasl+smtp+ssl+tokyocabinet
now, but it still doesn't work for me. Anyone on FileVault except for
me?
Would you care to share your timeout, mail_check, ..., variables
please?
-Andr�
André Berger
> On 2009-09-24, Andr� Berger <andre....@web.de> wrote:
[No new mail notification with Snow Leopard]
> You didn't mention whether you'd built mutt from source, used fink, or
> the macports version. But when I upgraded to 10.6 I found it necessary to
> rebuild mutt (I build it from source) as well as completely wiping macports
> and reinstalling all that. Most everything works fine now except esmtp
> and mplayer (dammit).
It was a self-compiled mutt 1.5.19+nntp. Now I'm on macports
mutt-devel
@1.5.20_1+gpgme+headercache+idn+imap+nntp+pop+sasl+smtp+ssl+tokyocabinet,
no change.
Would you (and those who got it working) please share your
mail_check, timeout etc. settings?
As to libesmtp/esmtp, I had to recompile them, but they do work.
-Andr�
Indi
>
> It was a self-compiled mutt 1.5.19+nntp. Now I'm on macports
> mutt-devel
> @1.5.20_1+gpgme+headercache+idn+imap+nntp+pop+sasl+smtp+ssl+tokyocabinet,
> no change.
>
I wonder then if filevault has anything to do with it somehow...
Haven't used filevault myself.
> Would you (and those who got it working) please share your
> mail_check, timeout etc. settings?
>
I actually don't specify either of those settings, they don't appear
to be necessary. The only imap-related settings I use are the bare
minimum ( i.e. imap_user, imap_host, imap_pass, spoolfile, and folder
settings).
> As to libesmtp/esmtp, I had to recompile them, but they do work.
>
Thank you, that's very good to know -- though I did rebuild it and it
still didn't work for me. I'm going to give it another shot though
when I get a little free time.
--
indi
Sylvain Soliman
> @1.5.20_1+gpgme+headercache+idn+imap+nntp+pop+sasl+smtp+ssl+tokyocabinet
> now, but it still doesn't work for me. Anyone on FileVault except for
> me?
>
> Would you care to share your timeout, mail_check, ..., variables
> please?
(Unfortunately) I'm satisfied with the default values. Note, however, that
I'm not using FileVault either...
Good luck (may be looking for some other SL+FileVault troubles might
provide some hints),
Sylvain
--
Sylvain Soliman <Sylvain...@RmThis.m4x.org> GPG Key: 0x0F53AF99
Page personelle http://contraintes.inria.fr/~soliman/
André Berger
-Andr�
André Berger
> > I'm on MacPorts mutt-devel
> > @1.5.20_1+gpgme+headercache+idn+imap+nntp+pop+sasl+smtp+ssl+tokyocabinet
> > now, but it still doesn't work for me. Anyone on FileVault except for
> > me?
OK, got rid of FV, and things are back to normal. Every new revision
of Mac OS X seems to bring new FV problems!
OT: An interesting discovery might lead to a solution of my
no-auto-sleep problem.
pmset -a ttyskeepawake 0
Indi
>
Thanks Andre, it's okay though. I'll just build them again when I have
a chance. To tell the truth, my Mac mostly runs Debian nowadays. I
reboot into OS X mainly just to do multitrack recording work.
--
Cheers,
indi
Jon Solberg
> On 2009-09-27, André Berger <andre....@web.de> wrote:
>> I could tar up libesmtp/esmtp for you.
>
> a chance. To tell the truth, my Mac mostly runs Debian nowadays. I
> reboot into OS X mainly just to do multitrack recording work.
Have you tried Ardour (at http://www.ardour.org)? Might be an option
for you.
--
Jon Solberg (remove "nospam" from email address).
Indi
> On 2009-10-02, Indi <in...@16x108.local> wrote:
>> On 2009-09-27, André Berger <andre....@web.de> wrote:
>>> I could tar up libesmtp/esmtp for you.
>>
>> Thanks Andre, it's okay though. I'll just build them again when I have
>> a chance. To tell the truth, my Mac mostly runs Debian nowadays. I
>> reboot into OS X mainly just to do multitrack recording work.
>
> Have you tried Ardour (at http://www.ardour.org)? Might be an option
> for you.
>
Thanks, I have tried that (and ecasound, jokosher, a few others).
Linux is just nowhere near as good as OS X for pro sound. It can be made
to work, but it's a similar experience to using windows for that -- things
go wrong and need fiddling with so often it just kills the inspiration.
In fact, I've invested a huge amount of time into trying to do pro audio
work in Linux over the past six years or so (debian, gentoo, crux, arch,
even "ubuntu-studio") but the best results I could get just weren't good
enough, and I've tried it with a number of "supported" soundcards.
Frankly, ALSA/jackd/pulseaudio are completely horrible for pro multitrack
work (hissing, popping, sound quality suddenly degrading, etc). Works fine
for consumer-grade audio, but if you start doing something serious you quickly
encounter the shortcomings.
I wish it were otherwise, then frankly I'd probably not bother buying
Apple hardware anymore. But there are definitely some strong reasons why
a lot of multimedia pros won't work on anything but OS X.
--
Cheers,
idd