File: filter_13.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 (71 lines) | stat: -rw-r--r-- 2,967 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
<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.52
     from filter on 25 November 2000 -->

<TITLE>Exim Filter Specification - The deliver command</TITLE>
</HEAD>
<body bgcolor="#FFFFFF" text="#00005A" link="#FF6600" alink="#FF9933" vlink="#990000">
Go to the <A HREF="filter_1.html">first</A>, <A HREF="filter_12.html">previous</A>, <A HREF="filter_14.html">next</A>, <A HREF="filter_34.html">last</A> section, <A HREF="filter_toc.html">table of contents</A>.
<P><HR><P>


<H2><A NAME="SEC13" HREF="filter_toc.html#TOC13">The deliver command</A></H2>


<PRE>
     deliver &#60;<EM>mail address</EM>&#62;
e.g. deliver "Dr Livingstone &#60;David@somewhere.africa&#62;"
</PRE>

<P>
This provides a forwarding operation. The message is sent on to the given
address, exactly as happens if the address had appeared in a traditional
<TT>`.forward'</TT> file. To deliver a copy of the message to your normal mailbox, your
login name can be given. Once an address has been processed by the filtering
mechanism, an identical generated address will not be so processed again, so
doing this does not cause a loop.

</P>
<P>
However, if you have a mail alias, you should <EM>not</EM> refer to it here. For
example, if the mail address <TT>`L.Gulliver'</TT> is aliased to <TT>`lg103'</TT> then all
references in Gulliver's <TT>`.forward'</TT> file should be to <TT>`lg103'</TT>. A reference to
the alias will not work for messages that are addressed to that alias, since,
like <TT>`.forward'</TT> file processing, aliasing is performed only once on an address,
in order to avoid looping.

</P>
<P>
Only a single address may be given to a <EM>deliver</EM> command, but multiple
occurrences of the command may be used to cause the message to be delivered to
more than one address. However, duplicate addresses are discarded.

</P>
<P>
<font color=green>
Following the new address, an optional second address, preceded by
<TT>`errors_to'</TT> may appear. This changes the address to which delivery errors on
the forwarded message will be sent. Instead of going to the message's original
sender, they go to this new address. For ordinary users, the only value that is
permitted for this address is the user whose filter file is being processed.
For example, the user <TT>`lg103'</TT> whose mailbox is in the domain
<EM>lilliput.example</EM> could have a filter file that contains

<PRE>
     deliver jon@elsewhere.example errors_to lg103@lilliput.example
</PRE>

<P>
Clearly, using this feature makes sense only in situations where some (but not
all) messages are being forwarded. In particular, bounce messages must not be
forwarded in this way, as this is likely to create a mail loop if something
goes wrong.
</font>

</P>

<P><HR><P>
Go to the <A HREF="filter_1.html">first</A>, <A HREF="filter_12.html">previous</A>, <A HREF="filter_14.html">next</A>, <A HREF="filter_34.html">last</A> section, <A HREF="filter_toc.html">table of contents</A>.
</BODY>
</HTML>