this too. :)
* Mostly a simple version update, although I tweaked a few things
* Make some Makefile variables more... variable
* SSLTYPE update to match new c-client makefile
* Remove a spurious variable from the port Makefile
* Tab'ify a couple places in patches that had to be regenerated anyway
- Install additional cclient header files
- Move SSL dependency generation for cclient to post-build
- Bump PORTEPOCH
- Removed -drac PKGNAMESUFFIX,more confusion than extra info
- Remove futile build of imapd/ipop3d/ipop2d in cclient, and libc-client4.a
in the imap-uw port.
- Respect CFLAGS and CC
PR: 30954
Submitted by: maintainer
* Add two more master sites that I control myself, to bring some much
needed stability there too (UW has been removing snapshots without
putting them in the old dir).
* Use PAM by default.
* Remove some unnecessary linking parameters.
Submitted by: Anders Nordby <anders@fix.no>
opposite case :) Make the c-client's Makefile use the LDFLAGS files,
when linking the shared library. This ensures, that the things like
-lpam, -lssl are linked into it and an application does not have to
refer to them explicitly.
WITH_SSL should, IMHO, be made a default...
1. Add support for building cclient with SSL. Warn about the possibility
that some ports may have been missed and need ssl added at link time.
2. Update cclient and imap-uw to latest versions.
3. Fix pine4 to add ssl libraries. This can be used as a model for what
other ports may need to do.
4. Release MAINTAINERship (by request).
Submitted by: anders@fix.no
Approved by: petef@databits.net
Update imap-uw to the latest version (imap-2000).
Update pine4 to the latest version (pine-4.31).
Despite the fact that the new releases of imap-uw and pine are
intended to improve security, the security warnings on the pine
and imap-uw ports have been left intact until they have proven
themselves.
As Vladimir Ivanov explains:
unix-mx driver doesn't set file permissions properly for non-private
messages (e.g. public#). The problem caused by mx_append procedure,
where the driver doesn't call set_mbx_permissions for just created
message file.
Submitted by: Vladimir Ivanov <wawa@comptek.ru>
