You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.
I am entirely new to Mailbox Alert so just experimenting to see how it works. I was using the default setting as supplied on a new install of Mailbox Alert. That setting has the title "Default sound" set as "System Default" sound for giving alerts. This didn't work. The sound that was being played was a sort of loud and sharp ping, rather than the default that I am used to with Windows/Betterbird. On my Windows system the default sound for new mail is supplied by the Windows file "Windows Notify Email.wav". To use that as the default I had do two things:
(1) In Betterbird Tools>Settings>General>Incoming Mails I had to untick the "Play a sound" setting.
(2) I then made a copy of the file "Windows Notify Email.wav" into my Betterbird 'chrome' folder and point Mailbox Alert to that copy of the file. Once I did this things started work okay.
I would also note that I had similar difficulties with the Mailbox Alert "Default message" setting. To get that to work properly I had to in Betterbird Tools>Settings>General>Incoming Mails untick the setting "Show an alert" — once I did that the Mailbox Alert notification dialogue started to work properly.
I really think that the Mailbox Alert help file/manual should mention to the user that to get Mailbox Alert to function correctly it might be necessary to untick the settings mentioned above in Thunderbird/Betterbird settings as described above. (It took me quite some time to work out that was what I had to do. Working out how to do that might defeat some new users of Mailbox Alert. So this really needs to be mentioned and made clear in the manual.)
The text was updated successfully, but these errors were encountered:
RadicalRadish
changed the title
Possible Bug: Incorrect Sound Being Used for Alert (Mailbox Alert v0.30)
Possible Bug: Incorrect Sound Being Used for Alert and Similar Issue with Message Dialogue (Mailbox Alert v0.30)
Aug 5, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
OS: Windows 10 Pro.
Email Client: BetterbirdPortable-102.14.0-bb39.en-US.win64 (01 Aug 2023)
Mailbox Alert v0.30
I am entirely new to Mailbox Alert so just experimenting to see how it works. I was using the default setting as supplied on a new install of Mailbox Alert. That setting has the title "Default sound" set as "System Default" sound for giving alerts. This didn't work. The sound that was being played was a sort of loud and sharp ping, rather than the default that I am used to with Windows/Betterbird. On my Windows system the default sound for new mail is supplied by the Windows file "Windows Notify Email.wav". To use that as the default I had do two things:
(1) In Betterbird Tools>Settings>General>Incoming Mails I had to untick the "Play a sound" setting.
(2) I then made a copy of the file "Windows Notify Email.wav" into my Betterbird 'chrome' folder and point Mailbox Alert to that copy of the file. Once I did this things started work okay.
I would also note that I had similar difficulties with the Mailbox Alert "Default message" setting. To get that to work properly I had to in Betterbird Tools>Settings>General>Incoming Mails untick the setting "Show an alert" — once I did that the Mailbox Alert notification dialogue started to work properly.
I really think that the Mailbox Alert help file/manual should mention to the user that to get Mailbox Alert to function correctly it might be necessary to untick the settings mentioned above in Thunderbird/Betterbird settings as described above. (It took me quite some time to work out that was what I had to do. Working out how to do that might defeat some new users of Mailbox Alert. So this really needs to be mentioned and made clear in the manual.)
The text was updated successfully, but these errors were encountered: