Arch Linux User Repository

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