darix
darix
+1 on tagging a release. most distros if not all have a policy to prefer releases.
irssi at least says `There is no such nick ` in that case.
why not store the metadata for each file in the DB?
make sure the scripts are in the directory configured with ```sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe``` and with the mail_log enabled you should actually see the script being called (from ```journalctl -b --no-tail```)...
This needs support from pigeonhole. in theory one could query the special folder Junk and then use that. then we wouldnt need to hard code the folder path at all...
@mlschroe when can it happen that the binaryarch field is not set?
but the key file in the repository is still with the old expiration date.
user wants to install package from repos with outdated key: e.g. http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/Debian_6.0/Release.key of course the package manager will and _should_ warn him "key outdated". having it republish the repos with...
> The package manager should _not_ warn about an outdated key, an outdated key is perfectly acceptable as long as the signatures were done when the key was not expired....
the interesting part with the service file is how to support password file and interactive mode for the password