head	1.1;
branch	1.1.1;
access;
symbols
	RELENG_8_4:1.1.1.7.0.50
	RELENG_9_1_0_RELEASE:1.1.1.7
	RELENG_9_1:1.1.1.7.0.48
	RELENG_9_1_BP:1.1.1.7
	RELENG_8_3_0_RELEASE:1.1.1.7
	RELENG_8_3:1.1.1.7.0.46
	RELENG_8_3_BP:1.1.1.7
	RELENG_9_0_0_RELEASE:1.1.1.7
	RELENG_9_0:1.1.1.7.0.44
	RELENG_9_0_BP:1.1.1.7
	RELENG_9:1.1.1.7.0.42
	RELENG_9_BP:1.1.1.7
	RELENG_7_4_0_RELEASE:1.1.1.7
	RELENG_8_2_0_RELEASE:1.1.1.7
	RELENG_7_4:1.1.1.7.0.40
	RELENG_7_4_BP:1.1.1.7
	RELENG_8_2:1.1.1.7.0.38
	RELENG_8_2_BP:1.1.1.7
	RELENG_8_1_0_RELEASE:1.1.1.7
	RELENG_8_1:1.1.1.7.0.36
	RELENG_8_1_BP:1.1.1.7
	RELENG_7_3_0_RELEASE:1.1.1.7
	RELENG_7_3:1.1.1.7.0.34
	RELENG_7_3_BP:1.1.1.7
	RELENG_8_0_0_RELEASE:1.1.1.7
	RELENG_8_0:1.1.1.7.0.32
	RELENG_8_0_BP:1.1.1.7
	RELENG_8:1.1.1.7.0.30
	RELENG_8_BP:1.1.1.7
	RELENG_7_2_0_RELEASE:1.1.1.7
	RELENG_7_2:1.1.1.7.0.28
	RELENG_7_2_BP:1.1.1.7
	RELENG_7_1_0_RELEASE:1.1.1.7
	RELENG_6_4_0_RELEASE:1.1.1.7
	RELENG_7_1:1.1.1.7.0.26
	RELENG_7_1_BP:1.1.1.7
	RELENG_6_4:1.1.1.7.0.24
	RELENG_6_4_BP:1.1.1.7
	RELENG_7_0_0_RELEASE:1.1.1.7
	RELENG_6_3_0_RELEASE:1.1.1.7
	RELENG_7_0:1.1.1.7.0.22
	RELENG_7_0_BP:1.1.1.7
	RELENG_6_3:1.1.1.7.0.20
	RELENG_6_3_BP:1.1.1.7
	v8_14_2:1.1.1.7
	RELENG_7:1.1.1.7.0.18
	RELENG_7_BP:1.1.1.7
	v8_14_1:1.1.1.7
	RELENG_6_2_0_RELEASE:1.1.1.7
	RELENG_6_2:1.1.1.7.0.16
	RELENG_6_2_BP:1.1.1.7
	v8_13_8:1.1.1.7
	v8_13_7:1.1.1.7
	RELENG_5_5_0_RELEASE:1.1.1.7
	RELENG_5_5:1.1.1.7.0.14
	RELENG_5_5_BP:1.1.1.7
	RELENG_6_1_0_RELEASE:1.1.1.7
	RELENG_6_1:1.1.1.7.0.12
	RELENG_6_1_BP:1.1.1.7
	v8_13_6:1.1.1.7
	RELENG_6_0_0_RELEASE:1.1.1.7
	RELENG_6_0:1.1.1.7.0.10
	RELENG_6_0_BP:1.1.1.7
	RELENG_6:1.1.1.7.0.8
	RELENG_6_BP:1.1.1.7
	v8_13_4:1.1.1.7
	RELENG_5_4_0_RELEASE:1.1.1.7
	RELENG_5_4:1.1.1.7.0.6
	RELENG_5_4_BP:1.1.1.7
	v8_13_3:1.1.1.7
	RELENG_4_11_0_RELEASE:1.1.1.2.6.3
	RELENG_4_11:1.1.1.2.6.3.0.2
	RELENG_4_11_BP:1.1.1.2.6.3
	RELENG_5_3_0_RELEASE:1.1.1.7
	RELENG_5_3:1.1.1.7.0.4
	RELENG_5_3_BP:1.1.1.7
	RELENG_5:1.1.1.7.0.2
	RELENG_5_BP:1.1.1.7
	v8_13_1:1.1.1.7
	RELENG_4_10_0_RELEASE:1.1.1.2.6.2
	RELENG_4_10:1.1.1.2.6.2.0.10
	RELENG_4_10_BP:1.1.1.2.6.2
	RELENG_5_2_1_RELEASE:1.1.1.6
	v8_12_11:1.1.1.6
	RELENG_5_2_0_RELEASE:1.1.1.6
	RELENG_5_2:1.1.1.6.0.6
	RELENG_5_2_BP:1.1.1.6
	RELENG_4_9_0_RELEASE:1.1.1.2.6.2
	RELENG_4_9:1.1.1.2.6.2.0.8
	RELENG_4_9_BP:1.1.1.2.6.2
	v8_12_10:1.1.1.6
	RELENG_5_1_0_RELEASE:1.1.1.6
	RELENG_5_1:1.1.1.6.0.4
	RELENG_5_1_BP:1.1.1.6
	RELENG_4_8_0_RELEASE:1.1.1.2.6.2
	v8_12_9:1.1.1.6
	RELENG_4_8:1.1.1.2.6.2.0.6
	RELENG_4_8_BP:1.1.1.2.6.2
	v8_12_8:1.1.1.6
	v8_12_7:1.1.1.6
	RELENG_5_0_0_RELEASE:1.1.1.6
	RELENG_5_0:1.1.1.6.0.2
	RELENG_5_0_BP:1.1.1.6
	RELENG_4_7_0_RELEASE:1.1.1.2.6.2
	RELENG_4_7:1.1.1.2.6.2.0.4
	RELENG_4_7_BP:1.1.1.2.6.2
	v8_12_6:1.1.1.6
	RELENG_4_6_2_RELEASE:1.1.1.2.6.2
	RELENG_4_6_1_RELEASE:1.1.1.2.6.2
	v8_12_5:1.1.1.6
	v8_12_4:1.1.1.6
	RELENG_4_6_0_RELEASE:1.1.1.2.6.2
	RELENG_4_6:1.1.1.2.6.2.0.2
	RELENG_4_6_BP:1.1.1.2.6.2
	v8_12_3_20020420:1.1.1.5
	v8_12_3:1.1.1.4
	v8_12_2:1.1.1.4
	RELENG_4_5_0_RELEASE:1.1.1.2.6.1
	RELENG_4_5:1.1.1.2.6.1.0.6
	RELENG_4_5_BP:1.1.1.2.6.1
	RELENG_4_4_0_RELEASE:1.1.1.2.6.1
	RELENG_4_4:1.1.1.2.6.1.0.4
	RELENG_4_4_BP:1.1.1.2.6.1
	v8_11_6:1.1.1.3
	v8_11_5:1.1.1.3
	v8_11_4:1.1.1.3
	RELENG_4_3_0_RELEASE:1.1.1.2.6.1
	RELENG_4_3:1.1.1.2.6.1.0.2
	RELENG_4_3_BP:1.1.1.2.6.1
	v8_11_3:1.1.1.3
	v8_11_2:1.1.1.3
	RELENG_4_2_0_RELEASE:1.1.1.2.6.1
	v8_11_1:1.1.1.3
	RELENG_4_1_1_RELEASE:1.1.1.2.6.1
	PRE_SMPNG:1.1.1.3
	v8_11_0:1.1.1.3
	RELENG_4_1_0_RELEASE:1.1.1.2
	RELENG_3_5_0_RELEASE:1.1.1.2
	RELENG_4_0_0_RELEASE:1.1.1.2
	RELENG_4:1.1.1.2.0.6
	RELENG_4_BP:1.1.1.2
	RELENG_3_4_0_RELEASE:1.1.1.2
	RELENG_3_3_0_RELEASE:1.1.1.2
	RELENG_3_2_PAO:1.1.1.2.0.4
	RELENG_3_2_PAO_BP:1.1.1.2
	RELENG_3_2_0_RELEASE:1.1.1.2
	RELENG_3_1_0_RELEASE:1.1.1.2
	v8_9_3:1.1.1.2
	v8_9_2_header:1.1.1.2
	RELENG_3:1.1.1.2.0.2
	RELENG_3_BP:1.1.1.2
	v8_9_2:1.1.1.2
	RELENG_3_0_0_RELEASE:1.1.1.1
	v8_9_1:1.1.1.1
	SENDMAIL:1.1.1;
locks; strict;
comment	@# @;


1.1
date	98.08.03.05.56.20;	author peter;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	98.08.03.05.56.20;	author peter;	state Exp;
branches;
next	1.1.1.2;

1.1.1.2
date	99.01.12.12.25.41;	author peter;	state Exp;
branches
	1.1.1.2.6.1;
next	1.1.1.3;

1.1.1.3
date	2000.08.12.21.55.30;	author gshapiro;	state Exp;
branches;
next	1.1.1.4;

1.1.1.4
date	2002.02.17.21.56.42;	author gshapiro;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	2002.04.20.20.31.44;	author gshapiro;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	2002.06.11.21.11.54;	author gshapiro;	state Exp;
branches;
next	1.1.1.7;

1.1.1.7
date	2004.08.01.01.04.40;	author gshapiro;	state Exp;
branches
	1.1.1.7.50.1;
next	;

1.1.1.2.6.1
date	2000.08.27.17.31.19;	author gshapiro;	state Exp;
branches;
next	1.1.1.2.6.2;

1.1.1.2.6.2
date	2002.03.25.21.25.36;	author gshapiro;	state Exp;
branches;
next	1.1.1.2.6.3;

1.1.1.2.6.3
date	2004.08.09.00.15.39;	author gshapiro;	state Exp;
branches;
next	;

1.1.1.7.50.1
date	2004.08.01.01.04.40;	author svnexp;	state dead;
branches;
next	1.1.1.7.50.2;

1.1.1.7.50.2
date	2013.03.28.13.02.00;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@#       @@(#)README	8.1 (Berkeley) 2/17/98

This directory contains the source files for mail.local.

This is not intended to be used on *stock* System V derived systems such as
Solaris or HP-UX, since they use a totally different approach to mailboxes
(essentially, they have a setgid program rather than setuid, and they rely
on the ability to "give away"  files to do their work). 

If you choose to run *this* mail.local on these systems then you may also
need to replace the existing MUAs, as well as IMAP and POP servers, with
ones that are compatible with the BSD interface.  You have been warned!
@


1.1.1.1
log
@Import sendmail-8.9.1 (slightly trimmed) onto a fresh branch under
src/contrib as per various discussions.  I will copy across our changes
and then point the Makefiles across once the dust has settled..
@
text
@@


1.1.1.2
log
@Import sendmail-8.9.2 onto vendor branch  (update from 8.9.1)

Obtained from: ftp.sendamil.org
@
text
@d1 1
a1 1
#       @@(#)README	8.1 (Berkeley) 2/17/1998
@


1.1.1.2.6.1
log
@MFC: Import of sendmail 8.11.0.
     Includes: moving /etc/aliases to /etc/mail/aliases, removing outdated
               documentation, and updating freebsd.mc for new syntax.
@
text
@d1 2
d8 1
a8 1
on the ability to "give away"  files to do their work).
a12 29

For systems with maillock() support, compile with -DMAILLOCK and link with
-lmail to use the maillock() routines.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILLOCK')
	APPENDDEF(`conf_mail_local_LIBS', `-lmail')

Defining CONTENTLENGTH (-DCONTENTLENGTH) will build a mail.local which
outputs a Content-Length: header.  Solaris 2.3 and later will automatically
include Content-Length: support.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DCONTENTLENGTH')

Defining MAILGID to a 'gid' (-DMAILGID=6) will cause mailboxes to be
written group writable and with group 'gid'.  This can be accomplished in
your site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILGID=6')

mail.local will not be installed setuid root. To use it as local
delivery agent without LMTP mode, use:

	 MODIFY_MAILER_FLAGS(`LOCAL', `+S')

in the .mc file.

$Revision: 8.8 $, Last updated $Date: 1999/09/10 01:49:41 $
@


1.1.1.2.6.2
log
@MFC: Import sendmail 8.12.2
MFC: Resolve conflicts from sendmail 8.12.2 import
MFC: Remove files no longer part of the sendmail 8.12.2 distribution.
MFC: Fix mail.local build for non-sendmail.org code (1.15)
@
text
@d5 2
a6 2
(essentially, they have a set-group-ID program rather than set-user-ID, and
they rely on the ability to "give away" files to do their work).
d32 1
a32 1
mail.local will not be installed set-user-ID root. To use it as local
d39 1
a39 1
$Revision: 8.10 $, Last updated $Date: 2001/09/08 01:21:04 $
@


1.1.1.2.6.3
log
@MFC: sendmail 8.13.1 import and related changes
@
text
@d39 1
a39 26
Defining HASHSPOOL (-DHASHSPOOL) will build a mail.local which supports
delivering to subdirectories of the mail spool, based on a hash of the
username (i.e., a hash depth of 2 and a username of "user" will result in
/var/spool/mail/u/s/user).  If the hash depth is greater than the length
of the username, "_" will be used.  The necessary subdirectories must
exist; mail.local will not create them.  Use the "-H" option to set the
hash type and depth (like "-H u2" for a username hash two levels deep).

The HASHSPOOL option also adds two other options: "-p path" to specify
an alternate mail spool path (i.e., "-p /local/mail") and "-n" to specify
that mail.local should not strip the @@domain part of recipient addresses
in LMTP mode.

In addition to HASHSPOOL, defining HASHSPOOLMD5 and linking against
libcrypto from OpenSSL like:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DHASHSPOOL -DHASHSPOOLMD5')
	APPENDDEF(`conf_mail_local_LIBS', `-lcrypto')

will offer an alternate hash, using a base64 encoding (changing / to _)
of an MD5 hash of the username.  This results in a more balanced
subdirectory tree.  The subdirectories will be named with A-Z, a-z, 0-9,
+, and _.  The hash type is "m", so use "-H m3" to get a three level MD5
based hash.

$Revision: 8.11 $, Last updated $Date: 2003/10/20 20:19:13 $
@


1.1.1.3
log
@Import of sendmail version 8.11.0 into vendor branch SENDMAIL with
release tag v8_11_0.

Obtained from: ftp://ftp.sendmail.org/pub/sendmail/
@
text
@d1 2
d8 1
a8 1
on the ability to "give away"  files to do their work).
a12 29

For systems with maillock() support, compile with -DMAILLOCK and link with
-lmail to use the maillock() routines.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILLOCK')
	APPENDDEF(`conf_mail_local_LIBS', `-lmail')

Defining CONTENTLENGTH (-DCONTENTLENGTH) will build a mail.local which
outputs a Content-Length: header.  Solaris 2.3 and later will automatically
include Content-Length: support.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DCONTENTLENGTH')

Defining MAILGID to a 'gid' (-DMAILGID=6) will cause mailboxes to be
written group writable and with group 'gid'.  This can be accomplished in
your site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILGID=6')

mail.local will not be installed setuid root. To use it as local
delivery agent without LMTP mode, use:

	 MODIFY_MAILER_FLAGS(`LOCAL', `+S')

in the .mc file.

$Revision: 8.8 $, Last updated $Date: 1999/09/10 01:49:41 $
@


1.1.1.4
log
@Import sendmail 8.12.2
@
text
@d5 2
a6 2
(essentially, they have a set-group-ID program rather than set-user-ID, and
they rely on the ability to "give away" files to do their work).
d32 1
a32 1
mail.local will not be installed set-user-ID root. To use it as local
d39 1
a39 1
$Revision: 8.10 $, Last updated $Date: 2001/09/08 01:21:04 $
@


1.1.1.5
log
@Import of post-8.12.3 bug fixes from vendor repository.

These are being imported for the upcoming FreeBSD 4.6 release.
@
text
@d39 1
a39 1
$Revision: 1.1.1.4 $, Last updated $Date: 2002/02/17 21:56:42 $
@


1.1.1.6
log
@Import sendmail 8.12.4
@
text
@d39 1
a39 1
$Revision: 8.10 $, Last updated $Date: 2001/09/08 01:21:04 $
@


1.1.1.7
log
@Import sendmail 8.13.1
@
text
@d39 1
a39 26
Defining HASHSPOOL (-DHASHSPOOL) will build a mail.local which supports
delivering to subdirectories of the mail spool, based on a hash of the
username (i.e., a hash depth of 2 and a username of "user" will result in
/var/spool/mail/u/s/user).  If the hash depth is greater than the length
of the username, "_" will be used.  The necessary subdirectories must
exist; mail.local will not create them.  Use the "-H" option to set the
hash type and depth (like "-H u2" for a username hash two levels deep).

The HASHSPOOL option also adds two other options: "-p path" to specify
an alternate mail spool path (i.e., "-p /local/mail") and "-n" to specify
that mail.local should not strip the @@domain part of recipient addresses
in LMTP mode.

In addition to HASHSPOOL, defining HASHSPOOLMD5 and linking against
libcrypto from OpenSSL like:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DHASHSPOOL -DHASHSPOOLMD5')
	APPENDDEF(`conf_mail_local_LIBS', `-lcrypto')

will offer an alternate hash, using a base64 encoding (changing / to _)
of an MD5 hash of the username.  This results in a more balanced
subdirectory tree.  The subdirectories will be named with A-Z, a-z, 0-9,
+, and _.  The hash type is "m", so use "-H m3" to get a three level MD5
based hash.

$Revision: 8.11 $, Last updated $Date: 2003/10/20 20:19:13 $
@


1.1.1.7.50.1
log
@file README was added on branch RELENG_8_4 on 2013-03-28 13:02:00 +0000
@
text
@d1 64
@


1.1.1.7.50.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 64
This directory contains the source files for mail.local.

This is not intended to be used on *stock* System V derived systems such as
Solaris or HP-UX, since they use a totally different approach to mailboxes
(essentially, they have a set-group-ID program rather than set-user-ID, and
they rely on the ability to "give away" files to do their work).

If you choose to run *this* mail.local on these systems then you may also
need to replace the existing MUAs, as well as IMAP and POP servers, with
ones that are compatible with the BSD interface.  You have been warned!

For systems with maillock() support, compile with -DMAILLOCK and link with
-lmail to use the maillock() routines.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILLOCK')
	APPENDDEF(`conf_mail_local_LIBS', `-lmail')

Defining CONTENTLENGTH (-DCONTENTLENGTH) will build a mail.local which
outputs a Content-Length: header.  Solaris 2.3 and later will automatically
include Content-Length: support.  This can be accomplished in your
site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DCONTENTLENGTH')

Defining MAILGID to a 'gid' (-DMAILGID=6) will cause mailboxes to be
written group writable and with group 'gid'.  This can be accomplished in
your site.config.m4 file with:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DMAILGID=6')

mail.local will not be installed set-user-ID root. To use it as local
delivery agent without LMTP mode, use:

	 MODIFY_MAILER_FLAGS(`LOCAL', `+S')

in the .mc file.

Defining HASHSPOOL (-DHASHSPOOL) will build a mail.local which supports
delivering to subdirectories of the mail spool, based on a hash of the
username (i.e., a hash depth of 2 and a username of "user" will result in
/var/spool/mail/u/s/user).  If the hash depth is greater than the length
of the username, "_" will be used.  The necessary subdirectories must
exist; mail.local will not create them.  Use the "-H" option to set the
hash type and depth (like "-H u2" for a username hash two levels deep).

The HASHSPOOL option also adds two other options: "-p path" to specify
an alternate mail spool path (i.e., "-p /local/mail") and "-n" to specify
that mail.local should not strip the @@domain part of recipient addresses
in LMTP mode.

In addition to HASHSPOOL, defining HASHSPOOLMD5 and linking against
libcrypto from OpenSSL like:

	APPENDDEF(`conf_mail_local_ENVDEF', `-DHASHSPOOL -DHASHSPOOLMD5')
	APPENDDEF(`conf_mail_local_LIBS', `-lcrypto')

will offer an alternate hash, using a base64 encoding (changing / to _)
of an MD5 hash of the username.  This results in a more balanced
subdirectory tree.  The subdirectories will be named with A-Z, a-z, 0-9,
+, and _.  The hash type is "m", so use "-H m3" to get a three level MD5
based hash.

$Revision: 8.11 $, Last updated $Date: 2003/10/20 20:19:13 $
@


