out of date - it was based on a.out OBJECT_FMT, and added entries in the
generated PLISTs to reflect the symlinks that ELF packages uses. It also
tried to be clever, and removed and recreated any symbolic links that were
created, which has resulted in some fun, especially with packages which
use dlopen(3) to load modules. Some recent changes to our ld.so to bring
it more into line with other Operating Systems also exposed some cracks.
+ Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain
the ELF symlinks.
+ Don't mess about with file system entries when handling shared objects in
bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will
have got it right, and have a much better idea than we do.
+ Modify PLISTs to contain "ELF symlinks"
+ On a.out platforms, delete any "ELF symlinks" from the generated PLISTs
+ On ELF platforms, no extra processing needs to be done in bsd.pkg.mk
+ Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on
a.out platforms
+ Update the documentation in Packages.txt
With many thanks to Thomas Klausner for keeping me honest with this.
The most notable user-visible change is the ability of the ipopd daemon to
forward requests to the imapd daemon, thus allowing POP2 and POP3 mail
clients to check IMAP mail.
Most notable operational changes from earlier versions:
. New, faster mailbox update logic is now available for the unix driver
on UNIX and Amiga. The old way is still being done for MMDF and the
unixnt driver on NT.
. External file locking is now available via a setgid mail program named
/etc/mlock (this is defined by LOCKPGM in the c-client Makefile). If
c-client is unable to create a <mailbox>.lock file in the directory
by itself, it will try to call mlock to do it. A sample mlock program
is part of the imap-utils. This is primarily for the benefit of those
paranoid souls who have their mail spool directories protected 775
instead of the recommended 1777.
. SASL authentication is supported in the IMAP and POP3 servers, and in
the IMAP, POP3, and SMTP client code. There is no support for NNTP
SASL yet
. CRAM-MD5 is supported by default for IMAP and POP3 clients. To enable
server support, read file imap-4.7/docs/md5.txt
. The mbox driver is now enabled by default. If the file "mbox" exists on
the user's home directory and is in UNIX mailbox format, then when INBOX
is opened this file will be selected as INBOX instead of the mail spool
file. Messages will be automatically transferred from the mail spool file
into the mbox file
To disable this behavior, delete "mbox" from the EXTRADRIVERS list in the
top-level Makefile and rebuild
. IMAP4rev1 protocol is now supported. The UNIX format support now maintains
unique identifiers (UIDs) and keyword flags for each message, and keeps an
invisible message at the start of the file which contains the UID base
information and a list of assigned keywords. There is no way to disable
this behavior, since it would disable IMAP4rev1 support. This message may
show up if you access the mailbox as a file using older mail software (e.g.
Pine 3.9x). It is invisible with IMAP or POP access, or with access as a
file using Pine 4.0x.
. Support for additional mailbox formats
. No longer keeps entire mailbox in memory for UNIX format files
. Multilingual searching of the following charsets are supported:
US-ASCII, UTF-8, ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4,
ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9,
ISO-8859-10, ISO-8859-11, ISO-8859-13, ISO-8859-14, ISO-8859-15,
KOI8-R, KOI8-U (alias KOI8-RU), TIS-620, VISCII,
ISO-2022-JP, ISO-2022-KR, ISO-2022-CN, ISO-2022-JP-1, ISO-2022-JP-2,
GB2312 (alias CN-GB), CN-GB-12345, BIG5 (alias CN-BIG5),
EUC-JP, EUC-KR, Shift_JIS
All ISO-2022-?? charsets are treated identically, and support ASCII,
JIS Roman, hankaku katakana, ISO-8859-[1 - 10], TIS, GB 2312, JIS X 0208,
JIS X 0212, KSC 5601, and planes 1 and 2 of CNS 11643.
EUC-JP includes support for JIS X 0212 and hankaku katakana
. Fast sorting including IMAP server-based sort
. Fast ordered-subject threading including IMAP server-based threading
