Non-email notifications

Hi,

I was wondering, if it's possible to extend the existing email notification system with something a little more "modern", like Pushbullet, for instance?
AFAIK it should be pretty simple to use their API, so it's just a question of how the current notification system has been implemented - is it open for "overloading", ie is it event-based or something similar, which could be handled by a plugin?

Zitat von dfarning

http://forums.openmediavault.o…s/?postID=48580#post48580']My initial inclination is that while useful, things that depend on external services might not fit into the core server. This feel like plugin. However, as a pure plugin it can not send core notifications.

This might be an interesting place to explore the relationship between core and plugins. Could volker add an abstraction layer to notifications while would enable a plugin developer to create a plugin which uses the service of their choice to push notifications?

This is exactly what I was aiming for.

I like Pushbullet, @davidh2k likes Pushover, someone else prefers Growl - I don't expect any developer to support all of these services out-of-the-box, if only a handful of users actually use them.
But it would be very nice to at least have to opportunity to install a simple plugin, to enable one of these services.
Enabling these services through plugins would probably also make it a lot easier to fix stuff when API's change and what not.

Now, I'm still pretty new to OMV (I've had it installed for a month or so), so I've no idea what's possible, and what's not, in regards to plugins.

Thanks a lot for the reply, I'll look into that when I get some free time

So, for anyone interested, here's what I've done:

Set up a local postfix-alias (in /etc/aliases), like this:

pushbullet: |/var/spool/postfix/email2pushbullet.sh

This will redirect all mail to "pushbullet@??" into the email2pushbullet.sh script.

Here's the content of the script:

#!/bin/bash


# Mail content is passed as file input, so we need to build an "arguments" array manually
args=()


while read line
do
  # Add each line of input to the array
  args+=("$line")
done


# Subject is argument 7 - replace "Subject:" with nothing
subject="${args[7]/Subject: /}"


# Msg is in line 13 and up
msg=""
num_args=${#args[@]}
for (( c=13; c<${num_args}; c++ ))
do
  # Append the new line to the message
  msg+="${args[$c]}"
  # Append a newline, which is not part of the read line
  msg+=$'\n'
done


# Use CURL to send the message to pushbullet
# Leave out -d device_iden=<your-device-id-here> to send to all devices
curl -u <your-api-key-here>: <api-url-here> -d device_iden=<your-device-id-here> -d type=note -d title="$subject" -d body="$msg"

<api-url-here> = https://api.pushbullet.com/v2/pushes (Right-click, copy link)

I'm no postfix expert, so this info might not be enough, but as always: google is your friend

I suspect this could easily be changed to support other API's out there @davidh2k

Update 03-09-14: Added a for-loop to read every line of the provided message. Otherwise, only the first line would be sent.

Update 08-09-14: There's an upper limit as the what can be sent using Pushbullet. I'm not sure what the actual limit is, but a semi-large Snapraid sync could not fit