For having an intuitive GUI synchronisation client, you may use grsync using a gvfs path on Linux or a Drive Letter on Windows where the WebDAV Storage is preliminary mounted. Or go for the commercial sync tool GoodSync which has WebDAV protocol built-in.

But now, when you try to synchronise with the WebDAV storage (e.g. to OwnSpace Web Storge or to Dropbox), you probably get many "file not found" errors and you end up with no files on the WebDAV storage.

To get that to work, you must use the rsync option "--inplace". Search for rsync options or an option meaning "directly write to files instead of temporary files".

1. Get cwrsync and install the program
2. If private/public key authentication is needed (as with OwnSpace Offsite Backup), get PuTTYgen
3. Start PuTTYgen and generate a private / public key pair and convert the private key to an OpenSSH Key file.
4. Put the public key onto the backup server.
5. Get this batch file and put it somewhere on your computer and adapt the variables to your needs
6. Test the batch file running it from a command line
7. Go to Task Scheduler (to be found under Computer / Manage) and create a new Task with the batch file cwrsync.cmd as command to execute

Introduction

The abbreviation "OMDR" stands for "obsolete mail domain reporter" and is a small shell script intended to find obsolete MX records to keep your mailserver clean and sane

As a source of currently configured domain can be either
* a textfile, every hosted domain on a seperate line
* a directory tree with the domains

Download

Get the script here

Usage

1. Copy the shell script to your mail server

2. Open the script within an text editor. There are several configuration options at the beginning of the script to adapt the script to your environment. See comment within the script itself!

3. After running the script, you end up with a file that contains all domains that are claimed not to be active any more on that particular mail host

Copyright

This script was written by Mike Rhyner for Adfinis Sygroup AG.

First, set the common name (CN, ~FQDN) for the certificate:

CN=host.domain.tld

Change to the directory where you would like to store the data relevant for certificates, e.g.:

cd /etc/ssl

Then create a private key:

openssl genrsa -out private/${CN}.key 2048

Generate the signing Request, either:
a) interactively, you'll have to answer some questions...:

openssl req -new -key private/${CN}.key -out ${CN}.csr

b) using a customized openssl config file:

openssl req -new -config ${CN}-openssl.cnf -key private/${CN}.key -out ${CN}.csr

Now you may either:
a) send the certificate request to an (official or internal) Certificate Authority to sign the Certificate

b) for testing purposes only, you can also self-sign the certificate:

openssl x509 -req -days 1825 -in ${CN}.csr -signkey private/${CN}.key -out certs/${CN}.crt

When you have received signed (or self-signed) certificate, you can copy all the files to the appropriate location.

Probably you have to create a combined pkcs#12 (.p12, .pfx) file, containing private key and certificates:

openssl pkcs12 -export -in ${CN}.crt -certfile cafile.pem -inkey ${CN}.key -out ${CN}.pfx

(where cafile.pem is the ca certificate bundle of issuing certificate authority)

Clear the shell variable for the Common Name:

CN=

You can actually map network drives to webdav locations. To do so use this:

1. Open Windows Explorer
2. Rightclick on 'Computer'
3. Go to 'map network drive'
4. Choose station/drive letter
5. Enter this path:

\\storage.ownspace.ch@SSL\files\shares\my-files

6. Press OK and your set.