MREMAP_MAYMOVE flag is the default behaviour on NetBSD and by
adjusting the single mremap() call it can be used on NetBSD too
(remove CONFIGURE_ENV injection kludge).
Thanks to <joerg> and <kamil> respectively for kindly pointing out
that and suggestions! (possible regressions are mine!)
pkgsrc changes:
- Remove no longer needed patches
Changes:
2.0
---
- Remove Courier support
- Add `ignore-errors' flag to ignore possible delivery errors and continue to
the next mail
- Add a `lock-timeout' option to customize default 10 seconds timeout
- Add support for STARTTLS on IMAP and POP3
- Disable OpenSSL insecure stuff enabled by default and introduce a `insecure'
flag to replace `no-tls1'
- Add support for newer OpenSSL
- Use SNI extension (fixes some servers when OpenSSL supports TLS 1.3)
- Misc bug fixes and improvements
When TLS 1.3 is used at least imap.gmail.com requires SNI extension
otherwise fails as follow:
certificate verification failed: self signed certificate
(This can happen with OpenSSL 1.1.1.)
Bump PKGREVISION
- Fix the build with OpenSSL 1.1.0 backporting a patch from upstream.
- Minor mostly cosmetic changes (pointed out by pkglint)
- Take MAINTAINERship
Bump PKGREVISION
pkgsrc changes:
o Update MASTER_SITES and HOMEPAGE to current reality.
o Convert the package in order to use GNU_CONFIGURE and add aclocal,
auto{conf,make} to USE_TOOLS (the configure is not provided by upstream
and need to be generated).
o Avoid mremap(2) usage. The NetBSD's mremap(2) isn't compatible (and probably
also other systems does not have it) so use mmap(2) instead.
Changes:
o Add support for STARTTLS on IMAP and POP3, from Markus Bachmann.
o Add "lock-wait" option to make fdm wait the global lock (lock-file option)
rather than exiting with an error immediately. Also add "lock-time" option
for the lock file timeout rather than a fixed 10 seconds. Requested by
Todd C. Miller.
o Add "ignore-errors" flag to instruct fdm to ignore delivery errors and
continue to the next mail, requested by Todd C. Miller.
o Delete Courier support.
o Delete regress/*
o Convert fdm to use autoconf and automake
o Various misc bug fixes
Update 1.7 to 1.8
(pkgsrc)
- Remove post-build: target in Makefile
(not necessary now)
(upstream)
- No immediate ChangeLog, Release note found other than
1.8 is released on 2014-12-03
Based on PR pkg/48254 by Leonardo Taccari.
pkgsrc changes:
* add options.mk: now fdm supports "debug" and "pcre" options (previously the
PCRE support was always included).
Changes:
* Add mbox tags for messages fetched from a mbox
* Detect GMail's XYZZY capability for IMAP and use it to try and workaround
some of their broken behaviour (incorrectly reported message sizes).
* Print a warning on missing maildirs when fetching from them rather than
crashing or giving an error. Reported by Frank Terbeck.
* Introduce a configure script and tidy up build infrastructure.
* GMail IMAP doesn't correctly set the \Seen flag after UID FETCH BODY[], so
explicitly set it with STORE when mail is kept. Reported by Patrice Clement.
* Properly count mails when polling multiple folders on a single IMAP server,
reported by Claudio M. Alessi.
* Support user and pass on NNTP, requested by Michael Hamann.
* Escape . properly when delivering to SMTP.
* Don't be as strict about format at the end of messages when using IMAP -
accept additional information as well as FLAGS. Reported by rivo nurges.
- The patch was added to define the non-posix MAXNAMLEN macro if it was
not already defined.
- The Makefile had to patched and then inline-replaced to fix the
invocation of the install program. Without this, non-root builds fail.
fdm is a program to fetch mail and deliver it in various ways
depending on a user-supplied ruleset. Mail may be fetched from
stdin, IMAP or POP3 servers, or from local maildirs, and filtered
based on whether it matches a regexp, its size or age, or the output
of a shell command. It can be rewritten by an external process,
dropped, left on the server or delivered into maildirs, mboxes, to
a file or pipe, or any combination.
fdm is designed to be lightweight but powerful, with a compact but
clear configuration syntax. It is primarily designed for single-user
uses but may also be configured to deliver mail in a multi-user
setup. In this case, it uses privilege separation to minimise the
amount of code running as the root user.