Name

lockmail — create mail lock files

Synopsis

lockmail [-r] [-t timeout] {lockfile} {program} [argument...]

DESCRIPTION

lockmail is a helper utility for working with mailbox files. Mailbox files must be locked to prevent other applications from modifying the mailbox at the same time. Different system use different locking conventions. lockmail uses two of the most common locking mechanisms in use, which should work reliably on most systems.

lockfile is the pathname to an existing mailbox file. By default, lockmail tries to lock the mailbox every five seconds (if the mailbox is already locked), and will give up after three minutes. After the mailbox is successfully locked, lockmail runs program as a child process, with any optional arguments. When program terminates, lockmail removes the mailbox lock, and terminates itself.

OPTIONS

-r

If a regular lock fails, try a read-only lock. Use this option to lock mailbox files in a read-only directory.

-t timeout

If the lock attempt fails, try again for up to timeout seconds. The actual timeout is rounded up to the next five second intere have been moved into mailbot(1).

BUGS

For the -a, -A, and -I options, a space after the header name and the colon is considered to be a non-empty field.

Do not provide the same header to more than one family of header-modifying options, such as -u/-U and -a/-A. Doing so yields unpredictable results. It's better to run reformail several times (use a pipe, perhaps).

SEE ALSO

courier(8), sendmail(8), mailbot(1), maildrop(1).

./usr/share/doc/maildrop/html/maildropgdbm.html0000644000000000000000000002414511762470546020515 0ustar rootroot maildropgdbm

Name

maildropgdbm — GDBM/DB support in maildrop

Synopsis

gdbmopen(filename, mode)

gdbmclose

gdbmfetch(key [,default])

gdbmstore(key,value)

DESCRIPTION

The gdbm family of functions provides access to the GDBM library - a library of routines that manage simple database files. The library provides a way of quickly storing and looking up key/data pairs.

GDBM support in maildrop is optional, and may not be available to you.

GDBM support in maildrop can optionally be implemented using the DB library. This option is selected by the system administrator. If this is the case, these functions still work exactly as described below, except that they will operate on DB hash files, instead of GDBM files.

To see whether GDBM or DB support is used, run the command "maildrop -v".

GDBM support is minimal, and simplistic. A filter file may have only one gdbm file open at the same time. However, the filter file can close the current gdbm file, and open another one. If another filter file is included using the include statement, the included filter file may open its own, separate, gdbm file.

A GDBM file contains a list of key/value pairs. All keys in the GDBM file are unique. After storing an arbitrary key/value pair in the GDBM file, the value associated with the given key can be quickly located and retrieved.

gdbmclose - close gdbm file

gdbmclose

This function closes the current GDBM file.

gdbmfetch - retrieve data

gdbmfetch (key [, options] [, default])

This function retrieves the data for the given key. key is the key to retrieve. The gdbmfetch function returns the data associated with this key. If the key does not exist in the GDBM file, gdbmfetch returns the default argument. If the default