Package Details: davmail 4.7.2-1

Git Clone URL: https://aur.archlinux.org/davmail.git (read-only)
Package Base: davmail
Description: a POP/IMAP/SMTP/Caldav/LDAP gateway for the exchange service
Upstream URL: http://davmail.sourceforge.net/
Licenses: GPL
Submitter: None
Maintainer: hyness
Last Packager: hyness
Votes: 85
Popularity: 1.560773
First Submitted: 2010-01-20 17:20
Last Updated: 2016-04-09 16:36

Latest Comments

AsmundEr commented on 2016-09-19 07:18

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.

ogarcia commented on 2016-04-20 12:56

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'.

wangsiyuan commented on 2016-01-13 01:09

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)

hyness commented on 2015-11-05 17:22

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

peterhoeg commented on 2015-10-31 03:42

@hyness, yes, I wrote them myself.

peterhoeg commented on 2015-10-31 03:41

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

getzze commented on 2015-10-29 17:55

@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

hyness commented on 2015-10-29 16:43

@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.

peterhoeg commented on 2015-10-29 03:00

@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

hyness commented on 2015-10-28 17:37

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?

All comments