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.