175210 - Option to execute external command for biff status

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Carsten Schlipf]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

Hi all,

Mozilla 1.2 has a great feature, I was missing before: On Preferences -> Mail &
Newsgroups -> Notifications you can enter a custom wav file for beeing notified
on new email. However on my Linux System (and I guess on all other Unix like
systems) you can choose different sound daemons, like esound or artsd. However
these sounddaemons do not work together. E.g. if you are hearing music with
artsd, a sound cannot be played through esound.

Actually, entering a WAV file does not work for me here.

What would be way better, is to allow a custom program to be executed on new
Email instead of specifying just a WAV file. Someone who uses esound all the
time, could enter "esdplay ~/mySound.wav", someone using artsd "artsd
~/mySound.wav" or even doing much more fancier stuff with custom scripts, like
running "xsnow" on new email ;-)

Netscape 4.7 has the preference mail.biff.command that can be used to do this.
In Mozilla this seems to be missing. A manual entry in prefs.js would also be OK
for me.

Reproducible: Always

Steps to Reproduce:
1. Run XMMS with output plugin set to esound and play a file
2. On Preferences -> Mail & Newsgroups -> Notifications set a custom wav file
3. Receive Email

Actual Results:  
No WAV is played on new Email

Expected Results:  
Play the WAV file

Comment 1

[Chris Lyon]

->mailnews

Comment 2

[Peter DePasquale]

I can reproduce the wav file not playing.  However, I'm not trying to play it
against other sounds/music.  Under my 1.4 build (Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.4) Gecko/20030617) on Mandrake 8.2, I have reset the new mail
notification to a .wav file which I can successfully play via XMMS.  Configuring
Mozilla to play this file when new mail arrives results only in the standard
system "beep" sound, which is the default behavior of Mozilla.

Comment 3

[Jim Richardson]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030818 on Redhat 9.0. I
too cannot get the 1.4 build to play a wave notification, even in preview with
no other sounds playing. Sounds play fine when viewed in a webpage, as I have
installed the proper video/snd plugins to handle the appropriate multi-media
types. I have observed this behavior with 1.4 and 1.4rc3. (Thunderbird notifies
properly by playing a wave )

Comment 4

[fred]

  this is happening for me with mozilla 1.4 also.  it seems that some of the
options for sound play have disappeared from the configuration page (since
moz1.2 or so?).
  as in other reports, i set a sound file to be played, but the "preview" button
and the arrival of email just cause a simple speaker beep.
  also, this doesn't seem like an enhancement request, it seems like a genuine
bug.  i recommend resetting the severity to "minor" or "normal" to reflect that
(but only the owner can do that).

Comment 5

[Carsten Schlipf]

Fred, I think you are right and I changed the severity. However I would like to
emphasize that my original post also contains an enhancement to allow any
command to be executed on new mail. A simple "Play wav on new mail" will hardly
cover all available sound daemons.

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Kent James (:rkent)]

Something similar to the request here is available as a custom filter action "Launch File" or "Run File" (with slightly different semantics) in my FiltaQuilla extension. I suppose that the request here is for the main notification sound to be allow a customizable program though instead of a filter action.

Comment 11

[Philip Chee]

I'd mark this as a duplicate of Bug 227407 except that that bug was closed as WORKSFORME but only because the reporter there wrote and extension to do that for himself. So I'll morph this bug to cover the intention of Bug 227407.