Arch Linux User Repository

I'm sorry you are still having difficulties building the package. I have been maintaining this package for several years and have not encountered this issue. If you look at the PKGBUILD, it is using the standard download url that SourceForge packages use. I think if this was a widespread issue, more people would be commenting. With that said, if you want to contribute a pull request with a better way of handling this, I'd definitely consider it

It Continues After diging into the actual temp directory, I found that the tgz file is actually plain text and here is a shot of the results
https://dl.dropboxusercontent.com/u/424516/Screenshot_20170424_092049.png
Looks like the mirror I'm being redirected to doesn't have the file and or it's Not likeing the redirect. Grabbing the actual tgs via the gui browser and droping into the temp dir mid build gets it built for me, as the md5sums match, but that is a work around at best.

@snuffop
From PKGBUILD...
[ "$CARCH" = "x86_64" ] && md5sums=('d2c3bff0a30eac74b3596258dcd2e04e')

From Sourceforge...
davmail-linux-x86_64-4.8.0-2479.tgz 2017-03-23 6.7 MB 542542 weekly
MD5: d2c3bff0a30eac74b3596258dcd2e04e

I just built it again and it worked. Not sure what you are doing but this package is not the problem.

Unable to Build due to source Validity
==> Building and installing package
==> Making package: davmail 4.8.0-1 (Thu Mar 30 09:54:08 CDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading davmail-linux-x86_64-4.8.0-2479.tgz...
######################################################################## 100.0%
-> Found davmail.desktop
-> Found davmail.sh
-> Found davmail@.system_service
-> Found davmail@.user_service
==> Validating source files with md5sums...
davmail-linux-x86_64-4.8.0-2479.tgz ... FAILED
davmail.desktop ... Passed
davmail.sh ... Passed
davmail@.system_service ... Passed
davmail@.user_service ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build davmail.
==> Restart building davmail ? [y/N]
==> --------------------------------

The system instance requires config files in /etc/davmail and should be enabled as follows:

systemctl enable --now davmail@davmail.service

You can run it as a system instance for another user with davmail@some_other_user.service like this:

systemctl enable --now davmail@some_other_user.service

In system mode we only support one configuration per user.

The user instance however does not take a USER as its instance name but instead the NAME of a configuration (it's entirely possible to want to run multiple instances).

That means if I'm logged in as user "peter", I would start it with:

systemctl --user enable --now davmail@davmail.service

As you can see from the unit file, it will look for its configuration as /home/peter/.config/davmail/instance_name.properties, but you can start it with a different config like this:

systemctl --user enable --now davmail@customer_a.service in which case the config will be read from /home/peter/.config/davmail/customer_a.properties

Hope that helps! Works splendidly here.

Davmail works fine when I execute `/usr/bin/davmail /etc/davmail/username.properties` from a terminal.
But the systemd files don't work at all, both the @system and @username (with my actual username) services fail with a zero-content error message (see below). Really, this is just another showcase of the horrible brokenness of a cancer that is systemd:

Loaded: loaded (/usr/lib/systemd/system/davmail@.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since Mon 2016-09-19 09:04:43 CEST; 4s ago
Process: 24324 ExecStart=/usr/bin/davmail /etc/davmail/%i.properties (code=exited, status=217/USER)
Main PID: 24324 (code=exited, status=217/USER)

Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Unit entered failed state.
Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Failed with result 'exit-code'.
Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Service hold-off time over, scheduling restart.
Sep 19 09:04:43 heimdall systemd[1]: Stopped DavMail for username.
Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Start request repeated too quickly.
Sep 19 09:04:43 heimdall systemd[1]: Failed to start DavMail for username.
Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Unit entered failed state.
Sep 19 09:04:43 heimdall systemd[1]: davmail@username.service: Failed with result 'start-limit-hit'.

Whoever invented this shit should go and sit in the corner and contemplate how it's even possible to come up with such uselessness.

There is a bug in davmail@.system_service

The line:
User=davmail

Must be:
User=%i

Cause you are running the service with a system user, but this system user does not have to be 'davmail'.

Hi, I can use davmail@.user_service to start davmail(systemctl --user start davmail@siyuan.service). But when I enable it to start automatically（ systemctl --user enable davmail@siyuan.service ), there is no icon. I used 'ps aux|grep davmail' to check, davmail is run. but it stopped soon.
the log:
Jan 13 08:56:12 siyuan davmail[463]: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
Jan 13 08:56:12 siyuan davmail[463]: at davmail.ui.tray.FrameGatewayTray$1.run(FrameGatewayTray.java:72)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:745)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.access$300(EventQueue.java:103)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue$3.run(EventQueue.java:706)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue$3.run(EventQueue.java:704)
Jan 13 08:56:12 siyuan davmail[463]: at java.security.AccessController.doPrivileged(Native Method)
Jan 13 08:56:12 siyuan davmail[463]: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:77)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.dispatchEvent(EventQueue.java:715)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Jan 13 08:56:12 siyuan davmail[463]: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
Jan 13 08:56:12 siyuan davmail[463]: at davmail.ui.tray.FrameGatewayTray$2.run(FrameGatewayTray.java:88)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:745)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.access$300(EventQueue.java:103)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue$3.run(EventQueue.java:706)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue$3.run(EventQueue.java:704)
Jan 13 08:56:12 siyuan davmail[463]: at java.security.AccessController.doPrivileged(Native Method)
Jan 13 08:56:12 siyuan davmail[463]: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:77)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventQueue.dispatchEvent(EventQueue.java:715)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
Jan 13 08:56:12 siyuan davmail[463]: at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Sorry for the delay, the systemd files are now included. Thanks peterhoeg!

@hyness, yes, I wrote them myself.

@getzee - correct, the files are templates, but as they have a "DefaultInstance", you don't need a separate non-template unit file.

@hyness

It's a template unit file. There should be another service file to launch davmail without argument to point to the default properties file in ~/.davmail.properties. It could be called davmail.service.
Also it would be nice to add a small post install message to mention that the service should be enabled.
Thanks

@peterhoeg

I've looked at your patch, are the @ symbols really necessary in the systemd filenames? I've never seen that before, but I don't know enough about systemd to know if they are required. Also, where did you get these? Did you write them yourself? After searching through davmail's svn repo, I can say they definitely do not provide them. The init scripts that people have been mentioning here are specific to redhat and debian.

@hyness, here is a patch that adds both user as well as system units for systemd. I'm using the user version myself.

Neither are enabled by default.

https://gist.github.com/689ec0b82e16002c2184

Re: systemd init file

I'm not opposed to including a systemd init file, however I don't think it should be enabled by default.

1. For example, in a multiuser system, this would not work since davmail is attached to a single user account.
2. In a desktop system, a simple DE startup for davmail works well. It always starts up for me perfectly in xfce4, unlike some other similar packages like dropbox which always seems to have problems showing up in the notification area.
3. I cannot seem to locate this mythical systemd file included with davmail. It's not in the generic linux package and I didn't see it in the rpm.

If someone can send me a merge request or simply email me the changes, I'll include them, but leave it up to users to enable the script. Is this acceptable?

Added check for gtk-update-icon-cache, thanks harpchad

davmail.install calls gtk-update-icon-cache, but gtk-update-icon-cache may not be installed as there's no dependency on the gtk-update-icon-cache package. Rather than adding a dependency, maybe you can test for the binary before executing, e.g.:

[[ -x /usr/bin/gtk-update-icon-cache ]] && gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor

Sorry, package is not actually out of date, my bad.

@elwinar : I created systemd init file and it seems to work well and I combined it with a davmail.server=true which work pretty well.
Just a curiosity what the next version would contain more in this area?
belette

I just flagged the package out-of-date, because there is a new 4.6.2 version, which include init scripts.
I you want some help with this let me know.
Cheers,
Elwinar;

Is it possible to add the systemd script to the package. The one mentioned by square252 should work, but davmail would need to be installed to /opt/davmail instead of /usr/bin and the config file would have to be located at the /opt/davmail folder, otherwise it could be used as the basis and adjusted to the used paths from this package. Thanks!

Thanks Logout22. It's more effective to flag the package as out of date which notifies me. Otherwise its up to me to visit this page and read your comment.

A new version is out:

http://sourceforge.net/projects/davmail/files/davmail/4.6.1/

Cheers!

thanks for providing this package. Sadly Exchange is used almost everywhere in corporate environments...

What about adding this systemd Script to the PKGBUILD? https://github.com/stdevel/davmail-initscript
The one zork posted does not work very well, because davmail itself is not killable via killall. Only the java process (which would kill much more on my system than just davmail)

thanks for providing this package. Sadly Exchange is used almost everywhere in corporate environments...

What about adding this systemd Script to the PKGBUILD? https://github.com/stdevel/davmail-initscript
The one zork posted does not work very well, because davmail itself is not killable via killall. Only the java process (which would kill much more on my system then just davmail)

systemd service for davmail:

[Unit]
Description=DavMail Exchange Gateway
Requires=network.target
After=network.target

[Service]
Type=simple
RemainAfterExit=no
ExecStart=/usr/bin/davmail /etc/davmail.properties
ExecStop=/usr/bin/killall davmail

[Install]
WantedBy=multi-user.target

@maci
The Java Packaging Guidelines say the following...

"You do not need to compile Java applications from source. Very little optimization goes into the compile process, as with gcc created binaries."

this is the prebuilt package.
wouldnt it be better to download the src and actually compile it instead?

Just built and installed the latest version. Here you go, people:

--- davmail/PKGBUILD 2013-07-18 10:53:11.000000000 -0500
+++ davmail.latest/PKGBUILD 2013-09-10 09:38:43.107915270 -0500
@@ -4,2 +4,2 @@
-pkgver=4.3.3
-pkgrel=2
+pkgver=4.3.4
+pkgrel=1
@@ -14 +14 @@
-_rev=2146
+_rev=2174
@@ -16,2 +16,2 @@
-[ "$CARCH" = "i686" ] && md5sums=('f66a6c8bfcf63a1d512d7756c316c145')
-[ "$CARCH" = "x86_64" ] && md5sums=('85f79607fcf4ba4d20ce1315197ec2ff')
+[ "$CARCH" = "i686" ] && md5sums=('119693e45bf6ea62a449879888e7f08b')
+[ "$CARCH" = "x86_64" ] && md5sums=('11cc6fffcef073cc968ea394df995b97')

I won't be able to update this package until next week. If you cannot wait, update the PKGBUILD file locally... it's very easy, just update the version number and revision. You can either update the md5sum or simply tell makepkg to ignore it. Hope that helps.

Latest version available: 4.3.4-2174

Looks like there was another bugfix. Earlier this morning 4.3.2 rev 2138 was released. Looks pretty minor though (thunderbird specific). I modified my local PKGBUILD (very nicely organized by the way ehliam) and it builds without trouble.

New version 4.3 is available. Thanks by your great contribution.

New version 4.3 is available. Thanks by your great contribution.

New PKGBUILD:

====
# Contributor: Hy Goldsher aka hyness <hyness-at-gmail>
# Maintainer: Hy Goldsher aka hyness <hyness-at-gmail>
pkgname=davmail
pkgver=4.2.0
pkgrel=1
pkgdesc="a POP/IMAP/SMTP/Caldav/LDAP gateway for the exchange service"
arch=('i686' 'x86_64')
url="http://davmail.sourceforge.net/"
license=('GPL')
makedepends=('unzip')
depends=('java-runtime')
[ "$CARCH" = "i686" ] && _ARCH=x86
[ "$CARCH" = "x86_64" ] && _ARCH=x86_64
_rev=2066
_src=$srcdir/davmail-linux-${_ARCH}-$pkgver-$_rev
source=(http://downloads.sourceforge.net/davmail/davmail-linux-${_ARCH}-$pkgver-$_rev.tgz davmail.desktop davmail.sh)
[ "$CARCH" = "i686" ] && md5sums=('34cab9538a77e9002837b50cc7d16fe4')
[ "$CARCH" = "x86_64" ] && md5sums=('c5fdc71d729fd223a36d2726f0abf8a2')
md5sums+=('1df37a6120d88de8df3cb735977336ba' '5f7c1bb0b5a9bc69c7015715d87862ea')
install=davmail.install

build() {
install -d $pkgdir/{usr/share/java/$pkgname/lib,usr/bin,usr/share/applications} || return 1
install $_src/davmail.jar $pkgdir/usr/share/java/$pkgname/ || return 1
install -D $_src/lib/* $pkgdir/usr/share/java/$pkgname/lib || return 1
install -m755 ${srcdir}/davmail.sh $pkgdir/usr/share/java/$pkgname || return 1
ln -s /usr/share/java/$pkgname/davmail.sh $pkgdir/usr/bin/davmail || return 1
install -Dm644 ${srcdir}/davmail.desktop ${pkgdir}/usr/share/applications/ || return 1

# Create icons
cd $_src || return 1
unzip -q davmail.jar tray2.png tray32.png tray48.png || return 1
install -Dm644 tray2.png ${pkgdir}/usr/share/icons/hicolor/16x16/apps/davmail.png || return 1
install -Dm644 tray32.png ${pkgdir}/usr/share/icons/hicolor/32x32/apps/davmail.png || return 1
install -Dm644 tray48.png ${pkgdir}/usr/share/icons/hicolor/48x48/apps/davmail.png || return 1
}

====

New version 4.2 is available

I've been running Davmail with this modified /usr/bin/davmail script that decrease memory consumed. The reported patch is:

http://sourceforge.net/mailarchive/message.php?msg_id=30306602

And the /usr/bin/script that I'm running is:

#!/bin/sh
DAVMAIL_HOME=/usr/share/java/davmail
for name in $DAVMAIL_HOME/lib/*.jar ; do
CP=$CP:$name
done
CP=$CP:$DAVMAIL_HOME/davmail.jar
exec "$JAVA_HOME/bin/java" -Xmx128m -XX:+UseCompressedOops -cp $CP davmail.DavGateway $1

@dlinds: there are more packages than just jre7-openjdk, which have 'provides=("java-runtime")' in PKGBUILD.
Though, it is possible that yaourt et group cannot search AUR for such packages - just guessing here.

It seems that the dependency 'java-runtime' has gone missing. Perhaps it could be substituted with 'jre7-openjdk'?

In case anyone is interested I've made a simple init script for davmail, it's available on http://pastebin.com/3FWbv2Hn

Extra md5sum line removed

You have two md5sum-lines in your PKGBUILD.

[...]
md5sums=($_srcmd5
'1df37a6120d88de8df3cb735977336ba'
'5f7c1bb0b5a9bc69c7015715d87862ea')
md5sums=('2ce18e9004874fd1d4cf0d1b4b37c380'
'1df37a6120d88de8df3cb735977336ba'
'5f7c1bb0b5a9bc69c7015715d87862ea')
[...]

Yea, drove me nuts. Good thing we finally switched away from Exchange :)

Does anyone else have the problem where Davmail doesn't respond or show the popup notification on startup? I then have to kill the process and reload Davmail. Sometimes I have to do this five or six times before Davmail will work.

Does anyone else have the problem where Davmail doesn't respond or show the popup notification on startup. I then have to kill the process and reload Davmail. Sometimes I have to do this five or six times before Davmail will work.

working great, thanks!

Nice, finally 3.8.5 works for me!

@xduugu: Fixed problems with desktop file

3.8.2 release doesn't work for me, I cannot connect any more to Exchange 2007 server, davmail asks me if my exchange password is expire, preventing me from logging in...
I had to downgrade to 3.8.1 to have things working again..
Does anyone experienced same issue?

There is an error and a warning in the desktop file you might want to fix some day:

$ desktop-file-validate /usr/share/applications/davmail.desktop
/usr/share/applications/davmail.desktop: warning: value "Application;Network;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Application"
/usr/share/applications/davmail.desktop: error: key "GenericName[en_US]" in group "Desktop Entry" is a localized key, but there is no non-localized key "GenericName"

Sorry, I thought jar was included in the JRE. Seems silly to make people install the jdk just to extract icons so I made unzip a makedepends instead.

Sorry, I thought jar was included in the JRE. Seems silly to make people install the jdk just to extract icons so I made unzip a makedepnds instead

PKGBUILD runs "jar", which is included in jdk package, which should therefore be added into build dependencies...