Package Details: nodejs-imapnotify 0.4.1-9

Git Clone URL: (read-only)
Package Base: nodejs-imapnotify
Description: Execute scripts on new messages using IDLE imap command
Upstream URL:
Licenses: MIT
Submitter: askurihin
Maintainer: yourealwaysbe
Last Packager: yourealwaysbe
Votes: 4
Popularity: 0.000000
First Submitted: 2014-01-29 07:06
Last Updated: 2018-02-06 20:34

Latest Comments

1 2 Next › Last »

yourealwaysbe commented on 2018-02-06 17:20

@ad1217 Argh, that was silly of me. Will fix tonight.

ad1217 commented on 2018-02-06 17:16

@yourealwaysbe Thanks for the update, but you aren't installing the .service file now.

yourealwaysbe commented on 2018-02-05 12:33

Ok, new version ready to go, i just need to get to a machine that has the right ssh key to update the AUR :) PKGBUILD below in case it's useful and i go awol for life reasons:

# Current Maintainer : Matthew Hague <>
# Original Maintainer : a-sk <askurihin at gmail dot com>
pkgdesc="Execute scripts on new messages using IDLE imap command"

package() {
    npm install --cache "${srcdir}/npm-cache" -g --user root --prefix "$pkgdir/usr" "$srcdir/$_npmname-$pkgver.tgz"

yourealwaysbe commented on 2018-02-05 12:11

@ad1217 -- this is annoying. I'm not sure what changed to make this break. I will look into it asap.

ad1217 commented on 2018-02-02 20:44

This package doesn't build correctly for me: it creates usr/lib/node_modules/imapnotify as a symlink to ../../../../../src/nodejs-imapnotify (ie the source directory when building the package), which obviously doesn't work when the package is installed. Also, the author seems to have stopped tagging releases in github, as the npm page ( has a release 0.4.1. Both of these problems can be fixed by getting the package from npm directly, as this does not symlink wierdly.

Rhinoceros commented on 2016-10-10 00:28

Hi @yourealwaysbe. It looks like upstream is moving development to a Python version of imapnotify, based on this issue [a]. I created a PKGBUILD [b], and I'm happy to make you co-maintainer, if you like.


yourealwaysbe commented on 2015-10-23 06:02

Gah, git push probably warned me about that too... Should be ok now.

Rhinoceros commented on 2015-10-23 04:45

Ah perfect. That makes much more sense than my suggestion! It's working perfectly now.

(Also, you forgot to run mksrcinfo, so the pkgrel wasn't bumped. I do that all the time, too!)

yourealwaysbe commented on 2015-10-21 22:01

Thanks for that, sorry for the slow response.

Changed to %h. To solve the file extension issue i kept a single service file, but now you need to include the file extension in the argument. E.g. systemctl start imapnotify@myconf.js

Rhinoceros commented on 2015-10-09 13:00

Thanks for that. However, there's one other issue. You'll need to use %h instead of ~ to refer to the home folder in systemd service files [3].

Also, I personally use a `*.js` file instead of a `*.json` file. This is so I can call an external program to store my password, as per upstream's suggestions. However, if I rename `foo.js` to `foo.json`, imapnotify parses it as a json file, and it fails. Hence, I have to manually change `.json` to `.js` in the installed systemd service file.

I wonder if a better solution would be to install two files? Perhaps install the previous imapnotify@.service, as well as imapnotify_js@.service (or similar) for `*.js` config files. The only difference would be changing `json` to `js`. I'm unsure as to the best solution, so please feel free to argue with me. :)