Skip to content

John McEleney / mailutils

Go to a project
Toggle navigation
Toggle navigation pinning
Commit 36a5b051 36a5b0512eac8c29222b6e0a3ceb812da0bd4f50 by Sergey Poznyakoff
Options

Updated

1 parent d60aeeee
Inline Side-by-side
Showing 4 changed files with 71 additions and 51 deletions
2005-06-23 Sergey Poznyakoff <gray@Mirddin.farlep.net>
* NEWS: Updated
* README-alpha: Updated
* include/mailutils/mailbox.h
(mu_path_maildir,mu_path_folder_dir): Removed
......
GNU mailutils NEWS -- history of user-visible changes. 2005-05-17
GNU mailutils NEWS -- history of user-visible changes. 2005-06-23
Copyright (C) 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
See the end of file for copying conditions.
......@@ -20,6 +20,8 @@ passwords, `scrambled' for passwords hashed using MySQL algorithm and
* mail
** Improved output of the commands `headers' and `z'
** Improved POSIX compatibility.
In particular, `next' command now works as described by
POSIX. Following commands change the status of the message to `read':
......@@ -60,6 +62,9 @@ Whenever available, `frm' uses BIDI algorithm for display. This
allows for correct display of subject lines written in languages
with right to left script orientation (Arabic, Hebrew).
* Maildir support
Implemented removal of messages.
* New SQL driver: odbc
* Ukrainian localization
......@@ -72,6 +77,11 @@ with right to left script orientation (Arabic, Hebrew).
** SQL authentication: prevent sql injection attacks
** Fixed bug in the default syslog diagnostic printer
** Fixed potential vulnerabilities: IDEF0954, IDEF0955, IDEF0956, IDEF0957
** `Imap:' mailboxes (remote mailboxes opened via imap interface) honor
read-only mode.
** Fixed date support in maildir (header fields Date, Envelope-Date and
Delivery-Date).
** Fixed RFC 2047 encoding.
Version 0.6:
......
......@@ -4,17 +4,17 @@ or CVS version of the package. See end of file for copying conditions.
* Introduction
This is a *pre-release* version, and not ready for production use yet. If you
are taking source from CVS, you will need to have libtool, automake, and
autoconf installed to help contribute. See the chapter `Building' for the
detailed instructions. The script autogen.sh is provided to help
autoconfigure mailutils from the cvs src. After you run autogen.sh,
there should be a file 'INSTALL' with (generic) installation instructions.
Package-specific installation instructions are set forth in the file
README.
Please, note that the accompanying documentation may be inaccurate or
incomplete. The ChangeLog file is the authoritative documentation of
This is a *pre-release* version, and not ready for production use
yet. If you are taking source from CVS, you will need to have libtool,
automake, and autoconf installed to help contribute. See the chapter
`Building' for the detailed instructions. The script autogen.sh is
provided to help autoconfigure mailutils from the cvs src. After you
run autogen.sh, there should be a file 'INSTALL' with (generic)
installation instructions. Package-specific installation instructions
are set forth in the file README.
Please, note that the accompanying documentation may be inaccurate
or incomplete. The ChangeLog file is the authoritative documentation of
all recent changes.
Report bugs to <bug-mailutils@gnu.org>
......@@ -31,13 +31,14 @@ CVS_RSH=ssh \
Make sure SSHv2 is used.
This will give you read-only access. If you think you need write access,
This will give you read-only access. If you think you need write access,
contact the mailing list.
* Building
In order to build this you will first need to have right versions of
autotools. At the time of this writing these are:
In order to build this you will first need to have right versions
of autotools and some auxiliary GNU programs. At the time of this
writing these are:
Package Version (>=)
======== ============
......@@ -45,34 +46,41 @@ autotools. At the time of this writing these are:
autoconf 2.59
libtool 1.5.8
gettext 0.14.1
gawk 3.1.3
To prepare the package for building run autogen.sh. Then run
./configure with the desired options (See INSTALL and README for
the detailed instructions). Finally, run make. Notice that the
first make of the package should be made in the source directory.
Subsequent makes make use build directory different from the source
one.
You will also need bison (or yacc) and flex. The grammar sources
were written so that any version of yacc or bison should be able to
handle them, however using recent bison is anyway recommended. The lex
sources could theoretically be compiled with AT&T lex. I have not
tested this, however, so using flex is higly recommended. I use flex
2.5.4.
To prepare the package for building run autogen.sh. Then run
./configure with the desired options (See INSTALL and README for the
detailed instructions). Finally, run make. Notice that the first make
of the package should be made in the source directory. Subsequent
makes can use build directory different from the source one.
* Debugging
To enable additional debugging information, configure the package with
--enable-debug option.
To enable additional debugging information, configure the package
with --enable-debug option.
Unless you compile mailutils statically, you will need to run following
command to debug a utility:
Unless you compile mailutils statically, you will need to run
following command to debug any utility:
libtool --mode execute gdb UTILITY-NAME
Sometimes it is impossible or inconvenient to start a utility from the
debugger. In this case, use --HANG option, which is supported by any
of the mailutils programs. The option instructs the program to sleep
for a given number of seconds (3600 by default) right after startup.
For example, to debug `mimeview' utility, run
Sometimes it is impossible or inconvenient to start a utility from
the debugger. In this case, use --HANG option, which is supported by
any of the mailutils programs. The option instructs the program to
sleep for a given number of seconds (3600 by default) right after
startup. For example, to debug `mimeview' utility, run
mimeview --HANG [OTHER-OPTIONS]
Then switch to another terminal, get the PID of the ivoked utility
and attach to it using gdb:
Then switch to another terminal, get the PID of the ivoked utility and
attach to it using gdb:
gdb mimeview PID
......@@ -84,30 +92,31 @@ Now set your breakpoints and proceed as usual.
* Importing gnulib files
Mailutils imports several source files from gnulib. These go mainly to
the conventional library libmailutils (directory lib/), but several of them
are incorporated into the main library libmailbox (directory mailbox/).
The imported sources are kept in the CVS repository to avoid using eventually
unstable versions appearing in the main gnulib CVS. Once in a time we
update the sources. The update procedure is quite straightforward:
change to the root directory of the mailutils tree and run `gnulib-sync'
script:
Mailutils imports several source files from gnulib. These go
mainly to the conventional library libmailutils (directory lib/), but
several of them are incorporated into the main library libmailbox
(directory mailbox/). The imported sources are kept in the CVS
repository to avoid using eventually unstable versions appearing in
the main gnulib CVS. Once in a time we update the sources. The update
procedure is quite straightforward: change to the root directory of
the mailutils tree and run `gnulib-sync' script:
$ cd mailutils
$ scripts/gnulib-sync $HOME/src/gnulib
The script takes a single argument: name of the directory with the
The script takes a single argument: name of the directory with the
copy of gnulib source tree (see http://savannah.gnu.org/projects/gnulib
for information on how to obtain gnulib sources). After incorporating
the files, gnulib-sync leaves in the current directory two files named
gnulib.changelog and gnulib.cvs. The file gnulib.changelog contains the
entry to be prepended to ChangeLog, the file gnulib.cvs is a shell script
with the commands necessary to incorporate all the changes into CVS.
If you need to add more gnulib modules to mailutils, add their names
to gnulib.modules file, following the instructions in its heading
comment. Please avoid placing modules in :mailbox section, as this
may lead to unwanted name clashes when linking user programs with
gnulib.changelog and gnulib.cvs. The file gnulib.changelog contains
an entry to be prepended to ChangeLog, the file gnulib.cvs is a shell
script with the commands necessary to incorporate all the changes into
CVS.
If you need to add more gnulib modules to mailutils, add their
names to gnulib.modules file, following the instructions in its
heading comment. Please avoid placing modules in :mailbox section, as
this may lead to unwanted name clashes when linking user programs with
libmailbox.
* Copyright information:
......
......@@ -261,8 +261,8 @@ extern int var_pipe __P ((int argc, char **argv, compose_env_t *env));
/* Cursor */
extern void set_cursor __P ((unsigned value));
extern size_t get_cursor __P ((void));
extern void page_reset __P ((int hard));
extern void cond_page_reset (size_t value);
extern void page_invalidate __P ((int hard));
extern void cond_page_invalidate (size_t value);
extern void page_do __P ((msg_handler_t func, void *data));
extern size_t page_move __P ((off_t offset));
extern int is_current_message __P ((size_t n));
......