Re: [Evolution] new mail notification not working?

[Brendan Murphy <Brendan Murphy cudenver edu>]

Eamonn,

Make sure that you have the box 'Apply filters to new messages in INBOX
on this server' selected under Tools -> Settings -> (Select Account) ->
Edit -> Receiving Options

I couldn't get my new mail notification to work until setting this
regardless of whether or not I had filters set.  It seems that the new
mail notification sound is itself a 'default' filter ... that obviously
won't get played unless this box is selected.

Hope this solves your problem-

B

On Tue, 2003-03-04 at 08:26, Eamonn Hamilton wrote:
> Hi Darren.
>
> Yep, I've looked through the history and still nothing. The setting of
> an action on a filter to beep DOES work, so evo can definitely talk to
> the esound setup, but not as new mail notification.
>
> I did have an IMAP account setup ( in addition to the local delivery
> account ), but I've removed that and I still get nothing for new mail
> notification, while setting a sound on the filters does work.
>
> So, in the meantime I've got a filter at the top of my list checking for
> the existence of the To header, and dropping through to the rest of
> them. Not ideal, but it works ( for most mail, anyway ).
>
> The next step, I guess, is to get a version of evolution compiled with
> some form of debugging in place to allow the tracing of filter actions
> as they are executed. Or something. :)
>
> Cheers,
> Eamonn
>
>
> On Tue, 2003-03-04 at 14:35, D. D. Brierton wrote: 
> > On Tue, 2003-03-04 at 10:44, Eamonn Hamilton wrote:
> >
> > > I'm trying to get evolution 1.2.2 ( debian/unstable ) to beep at me when
> > > I receive a mail.
> > > Unfortunately, despite everything I select, it remains mute. Esound is
> > > installed and working, and the mixer levels work fine for everything
> > > else. I've tried both the beep and a wav file.
> >
> > Well I can't get it to work either. I posted this bug report here:
> > http://bugzilla.ximian.com/show_bug.cgi?id=32198
> >
> > Why don't you read hrough it and see if anything there helps. The bug
> > has been closed by Fejj because he claims that he can't reproduce it and
> > there "can't possibly be anything wrong with the code", however, nothing
> > I do has managed to get this feature working and know that others have
> > problems with it too.
> >
> > Best, Darren
-- 
Network/DSL/Video
Computing, Information, and Network Services (CINS)
University of Colorado at Denver
(Tel) 303-556-4308 / Helpdesk 303-556-6100
(Fax) 303-556-2318
~~
"Why aren't you signed up for the 401k?
...I'd never be able to run that far."
        - Scott Adams (Dilbert)