New mail notification not working

New mail notification not working

[Russell Hoover]

I'm using zsh-4.0.2 on NetBSD-1.5.1 with mutt-1.2.5i (mutt compiled with S-Lang).
I'm using the maildir mailbox format with mutt.

In my .zshenv I have:

export MAIL=$HOME/.mailspool/rj
export MAILPATH=$HOME/.mailspool/rj:$HOME/Mail/trash'?New mail in trashbox.'

and I cannot get the "You have new mail." to show in zsh.


If the following is relevant (though I don't think it should be), I also have:

in .zprofile:
biff n

and in .zshrc:
setopt NO_MAIL_WARNING

Any advice welcome.

-- 
                                 // rj@panix.com //
                     GUI -- what your computer becomes after
                 spilling your coffee on it. (pronounced 'gooey')

Re: New mail notification not working

[Bart Schaefer]

On Aug 19,  2:39pm, Russell Hoover wrote:
} Subject: New mail notification not working
}
} I'm using the maildir mailbox format with mutt.
} and I cannot get the "You have new mail." to show in zsh.

If you built zsh yourself, try recompiling it with --enable-maildir-support.

Otherwise, zsh only checks for files that have changed -- that is, files
whose modify time is the same as or more recent than their access time.  If
the newly created files in your maildir "new" subdirectory don't have that
property, zsh won't report them as new mail.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

--enable-maildir-support question

[Russell Hoover]

On Sun 08/19/01 at 06:55 PM +0000,
Bart Schaefer <schaefer@brasslantern.com> wrote:

> If you built zsh yourself, try recompiling it with --enable-maildir-support.
> 
> Otherwise, zsh only checks for files that have changed -- that is, files
> whose modify time is the same as or more recent than their access time.  If
> the newly created files in your maildir "new" subdirectory don't have that
> property, zsh won't report them as new mail.

What exactly does zsh do differently once you *have* compiled in the
maildir-support option?  Doing a search on "maildir" in man zshall turns up
no information about --enable-maildir-support.  I have the option set, and
zsh is still giving no mail notification.

export MAIL=$HOME/.mailspool/rj
export MAILCHECK=1

mailpref=$HOME/Mail
mailpath=($HOME/.mailspool/rj
            $mailpref/z/'?New zsh mail.'
            $mailpref/m/'?New mutt mail.'
            $mailpref/trash/'?New mail in trash.')

-- 
                                 // rj@panix.com //
                    Dopeler effect: The tendency of stupid ideas
                   to seem smarter when they come at you rapidly.

Re: --enable-maildir-support question

[Geoff Wing]

Russell Hoover <rj@panix.com> typed:
:What exactly does zsh do differently once you *have* compiled in the
:maildir-support option?  Doing a search on "maildir" in man zshall turns up
:no information about --enable-maildir-support.  I have the option set, and
:zsh is still giving no mail notification.
:
:export MAIL=$HOME/.mailspool/rj
:export MAILCHECK=1
:mailpref=$HOME/Mail
:mailpath=($HOME/.mailspool/rj
:            $mailpref/z/'?New zsh mail.'
:            $mailpref/m/'?New mutt mail.'
:            $mailpref/trash/'?New mail in trash.')

Firstly, ``mailpath'' overrides ``MAIL''.
Secondly, Bart mentioned that multiple Maildir spools don't work
properly (yet).  A single Maildir spool does.

I use ``MAIL'' and not ``mailpath'' (because that's also what mutt
looks at) but also setting ``mailpath'', e.g.

% mailpath=('/path/to/my/Maildir?Postman called. New mail has arrived!!')

worked just fine too.

Regards,
-- 
Geoff Wing  <gcw@pobox.com>
rxvt stuff  <gcw@rxvt.org>
zsh stuff   <gcw@zsh.org>

Re: --enable-maildir-support question

[Russell Hoover]

On Sat 09/08/01 at 07:00 PM +1000, Geoff Wing <gcw@pobox.com> wrote:

> Firstly, ``mailpath'' overrides ``MAIL''.

Okay.  But I think the manual could be more direct about this.
Instead of saying:

            MAIL   If this parameter is set and <em>mailpath</em> is not set,
                   the shell looks for mail in the specified file.

I think it would be more explicit if it said:

           MAIL   If this parameter is set, the shell looks for mail
                  in the specified file.  But if <em>mailpath</em> is set,
                  the shell will look in the file specified by <em>mailpath</em>.
                  <em>mailpath</em> overrides <em>MAIL</em>.


> Secondly, Bart mentioned that multiple Maildir spools don't work
> properly (yet).  A single Maildir spool does.

(You may have already seen my question to him about that.)

Actually, I saw your message before I saw Bart's.  I was looking here
(in zsh-users) for a response, and, although Bart sent his response to
me directly, it managed to go into a mailbox other than my inbox.
Also, he appears to have cc:'d it to zsh-workers, but not zsh-users:

>	From: Bart Schaefer <schaefer@brasslantern.com>
>	Date: Fri, 7 Sep 2001 17:11:12 +0000
>	Subject: Re: New mail notification not working
>	To: Russell Hoover <rj@panix.com>
>	Cc: zsh-workers@sunsite.dk
>	X-Mailer: Z-Mail (5.0.0 30July97)
>	Comments: In reply to Russell Hoover <rj@panix.com>
>	        "Re: New mail notification not working" (Sep  7, 11:52am)

(No big deal.  I thought my question could use a re-phrasing anyway.)

> I use ``MAIL'' and not ``mailpath'' (because that's also what mutt
> looks at) but also setting ``mailpath'', e.g.

Since I use mutt, I should probably be doing the same thing.

> % mailpath=('/path/to/my/Maildir?Postman called. New mail has arrived!!')
> worked just fine too.

That's good news, but I'm stuck on something -- still not getting either
a defined (as per in your mailpath setting) or a default notification
message with:

export MAIL=$HOME/.mailspool/rj

OR with:

mailpath=($HOME/.mailspool/rj'?New mail has arrived.')

though it seems as though I should be . . .
-- 
                                 // rj@panix.com //

Re: New mail notification not working

[Bart Schaefer]

On Sep 9,  1:33pm, Russell Hoover wrote:
} Subject: Re: New mail notification not working
}
} Thanks  --  I asked that because the last sentence for the ``mailpath''
} entry in the manual
} [...] might well lead one to believe that, in the case of maildirs, unless
} I specified the ``new'' subdir, zsh would check the ``tmp'' and ``cur''
} subdirs as well

The manual doesn't tell anything about maildir support, mostly because
the person who contibuted the mailstat code didn't include a man patch
to go with it.  One side-effect of that code is that when checking new
mail, zsh can't tell that maildirs are directories -- mailstat returns
data as if the folder were one huge file.  That's why it's so expensive
in the absence of the (broken) optimization.

} > Anyway, mailstat() is using a single static structure to keep track of
} > the last-modified time of the maildir "new" subdir. This means that it
} > only works correctly if you have exactly one maildir directory in your
} > mailpath
} 
} To understand this fully I seem to need to make a distinction: you say
} "exactly one maildir directory in your mailpath"  --  Does that mean that
} I must have only one *defined* in my mailpath, or only one in existence?

Exactly one named in the value of the mailpath parameter.

} (I'd be quite satisfied, for now at least, to have notification working
} just for my inbox.)

[...]

} Shouldn't notification be working if I just have either of these defined
} in my .zshrc:
} 
}             export MAIL=$HOME/.mailspool/rj
} 
} or:         mailpath=($HOME/.mailspool/rj'?New mail has arrived.')

That should work, but see below.

} (btw, should the opening quote-mark above be where it is, or should it
} be just before ``$HOME'', or does it matter?)

It does matter; you have it right.

} (a)  From within either mutt's index or pager, I press `e' in mutt
}      to edit the raw message;

If you have mutt (or any of several other mail programs) running
continuously in another window, zsh won't regularly notify you of new
mail no matter what the mailbox format is, because there is a race
between mutt and the shell to see which one finds the new message
first.  Once mutt finds the message and adds it to its index, the
file access time will have changed and zsh won't consider the message
to be new any more.

If your maildirs are on NFS-mounted file systems, NFS attribute caching
can also affect whether zsh correctly detects new mail.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: New mail notification not working

[Russell Hoover]

On Fri 09/07/01 at 05:11 PM +0000, Bart Schaefer
<schaefer@brasslantern.com> wrote:

> No, you don't need anything after the name of the directory; you
> don't even need the trailing slash, though it should be harmless.

Thanks  --  I asked that because the last sentence for the ``mailpath''
entry in the manual is this:

             ``If  an element is a directory instead
               of a file the shell will recursively
               check every file in every subdirectory
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
               of the element."


Which might well lead one to believe that, in the case of maildirs, unless
I specified the ``new'' subdir, zsh would check the ``tmp'' and ``cur''
subdirs as well, and checking ``cur'' could be a disaster as ``cur'' might
contain dozens or hundreds of (non-new) messages.

> Anyway, mailstat() is using a single static structure to keep track of
> the last-modified time of the maildir "new" subdir. This means that it
> only works correctly if you have exactly one maildir directory in your
> mailpath -- if you have multiple maildirs, it gets confused about which
> modified-time to compare; it checks each maildir for new-ness against
> the modified time of the one preceding it in the mailpath, cycling to
> check the first maildir against the last on subsequent calls.

To understand this fully I seem to need to make a distinction: you say
"exactly one maildir directory in your mailpath"  --  Does that mean that
I must have only one *defined* in my mailpath, or only one in existence?

(I'd be quite satisfied, for now at least, to have notification working
just for my inbox.)

I have a total of two directories for all my mail:  (a)  my inbox, which
is ~/.mailspool/rj/ (with the three maildir subdirs -- ``cur'', ``new'',
and ``tmp'' -- inside of that) and  (b)  a ``Mail'' directory, containing
about a dozen subdirs of various mailing-list nicknames, etc.  (and each
of them, of course, has *its* own set of the three maildir subdirs).

Shouldn't notification be working if I just have either of these defined
in my .zshrc:

            export MAIL=$HOME/.mailspool/rj

or:         mailpath=($HOME/.mailspool/rj'?New mail has arrived.')

(btw, should the opening quote-mark above be where it is, or should it
be just before ``$HOME'', or does it matter?)

OR, does the mere fact that I have several maildirs *simply existing*
in the ``Mail'' directory (which is not defined in either ``MAIL'' or
``mailpath'' in my zsh init files)  --  does that *in and of itself*
confound mailstat?

(If it's the latter, it would seem that I'm out of luck until mailstat()
can be re-made along the lines of your suggestion.)

> So you ought to be getting notified some of the time, but it would seem
> random when you don't know what's going on.

I am only getting the (default) notification under one circumstance only,
and that is the following:

(a)  From within either mutt's index or pager, I press `e' in mutt
     to edit the raw message;

(b)  I am put into vim and I edit the message;

(c)  I write-quit out of vim and the new message appears in
     mutt's index, while the previous version of that message
     is marked for deletion;

(d)  I quickly switch to another terminal window and see
     ``You have new mail.'' appear before the zsh prompt
     after I press the RETURN key.


Thank you for your indulgence (trying not to seem too
obtuse about it all).

-- 
                                 // rj@panix.com //