File: spec_41.html

package info (click to toggle)
exim-html 3.20-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k, sarge, woody
  • size: 2,868 kB
  • ctags: 4,188
  • sloc: makefile: 40; sh: 19
file content (77 lines) | stat: -rw-r--r-- 2,516 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.52
     from spec on 25 November 2000 -->

<TITLE>Exim Specification - 41. Multiple user mailboxes</TITLE>
</HEAD>
<body bgcolor="#FFFFFF" text="#00005A" link="#FF6600" alink="#FF9933" vlink="#990000">
Go to the <A HREF="spec_1.html">first</A>, <A HREF="spec_40.html">previous</A>, <A HREF="spec_42.html">next</A>, <A HREF="spec_59.html">last</A> section, <A HREF="spec_toc.html">table of contents</A>.
<P><HR><P>


<H1><A NAME="SEC788" HREF="spec_toc.html#TOC788">41. Multiple user mailboxes</A></H1>
<P>
<A NAME="IDX1719"></A>
<A NAME="IDX1720"></A>
<A NAME="IDX1721"></A>
<A NAME="IDX1722"></A>
The wildcard facility of the generic <EM>prefix</EM> and <EM>suffix</EM> options for
directors allows you to configure Exim to permit users to make use
of arbitrary local part prefixes or suffixes in any way they wish.
A director such as

<PRE>
userforward:
  driver = forwardfile
  file = .forward
  suffix = -*
  suffix_optional
  filter
</PRE>

<P>
runs a user's <TT>`.forward'</TT> file for all local parts of the form <EM>*username-**</EM>.
Within the filter file the user can distinguish different cases by testing the
variable $<EM>local_part_suffix</EM>. For example:

<PRE>
if $local_part_suffix contains -special then
  save /home/$local_part/Mail/special
endif
</PRE>

<P>
If the filter file does not exist, or does not deal with such addresses, they
fall through to subsequent directors, and, assuming no subsequent use of
the <EM>suffix</EM> option is made, they presumably fail. Thus users have control over
which suffixes are valid.

</P>
<P>
Alternatively, a suffix can be used to trigger the use of a different
<TT>`.forward'</TT> file -- which is the way a similar facility is implemented in
another MTA:

<PRE>
userforward:
  driver = forwardfile
  file = .forward${local_part_suffix}
  suffix = -*
  suffix_optional
  filter
</PRE>

<P>
If there is no suffix, <TT>`.forward'</TT> is used; if the suffix is <EM>-special</EM>, for
example, <EM>.forward-special</EM> is used. Once again, if the appropriate file
does not exist, or does not deal with the address, it is passed on to
subsequent directors, which could, if required, look for an unqualified
<TT>`.forward'</TT> file to use as a default.

</P>

<P><HR><P>
Go to the <A HREF="spec_1.html">first</A>, <A HREF="spec_40.html">previous</A>, <A HREF="spec_42.html">next</A>, <A HREF="spec_59.html">last</A> section, <A HREF="spec_toc.html">table of contents</A>.
</BODY>
</HTML>