Package Details: davmail 4.8.4-1

Git Clone URL: (read-only)
Package Base: davmail
Description: a POP/IMAP/SMTP/Caldav/LDAP gateway for the exchange service
Upstream URL:
Licenses: GPL
Submitter: None
Maintainer: hyness
Last Packager: hyness
Votes: 94
Popularity: 1.391943
First Submitted: 2010-01-20 17:20
Last Updated: 2018-04-05 02:39

Latest Comments

nesk_aur commented on 2018-04-18 07:03

hyness, is there an open bug for trat/taskbar issues? If not - can you create one please? Let's see what DavMail's developer(s) say.

hyness commented on 2018-04-17 14:36

Davmail has removed the linux specific packages this package depended on. I have updated the PKGBUILD to use the current version but there are issues with the tray icon, I'm hesitant to release it right now. Looks like there's support for Unity and KDE. I tried this package in Cinnamon and the tray icon looks terrible and the program shows up in the taskbar all the time with a plain java icon.

I can release the package, but I don't think there is anything I can do to overcome these issues as I think they lie with changes within Davmail.

kwrazi commented on 2018-01-25 02:14

The systemd system_service script expects davmail user to exists. Your package does not create this user by default. Hence, when I try to start davmail system service in headless mode, it dies with the following errors:

$ journalctl _SYSTEM_UNIT=davmail@company.service
... davmail@company.service: Failed to determine user credentials: No such process
... davmail@company.service: Failed at step USER spawning /usr/bin/davmail: No such process

After manually adding this user,

$ useradd --system davmail

the service starts up successfully. You might consider modifying davmail.install to add this user.

hyness commented on 2017-04-24 14:36

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

snuffop commented on 2017-04-24 14:26

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

hyness commented on 2017-03-31 01:42

[ "$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.

snuffop commented on 2017-03-30 14:59

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
-> 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 ... 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]
==> --------------------------------

peterhoeg commented on 2016-11-29 02:19

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/, 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/

Hope that helps! Works splendidly here.

AsmundEr commented on 2016-09-19 07:18

Davmail works fine when I execute `/usr/bin/davmail /etc/davmail/` 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/ (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:

Must be:

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

All comments