Asked 10 years, 5 months ago. Active 2 years, 8 months ago. Viewed 3k times. Edit: Running Debian 6. The code handling this will honor your local changes, so this is usually fine, but will break local schemes that mess around with multiple versions of the file.
Most settings found in here do have corresponding questions in the Debconf configuration, but not all of them. Improve this question. These correspond to your user entries. Also, please post Debian and exim version you are using. All the searches I've done lead to some rootkit. Eg bugs. Apologies for not posting the version info earlier.
Tip - if you want someone to be notified of your message, start it with username. It should not be necessary to edit it manually, but would not hurt to look at it. Add a comment. Active Oldest Votes. Improve this answer. BillThor BillThor 8, 19 19 silver badges 27 27 bronze badges. What do I have to set that macro to? And where do I do that? Also, I tried to explain why I'm not just using the gmail forwarding, but it has to do with wanting the headers to reflect that the mail is being forwarded.
For example, if a a. I actually want c c. I've added additional information to my answer. These tar files contain only the doc directory, not the complete distribution, and are also available in. This restriction does not prevent Exim from being interfaced to UUCP as a transport mechanism, provided that domain addresses are used. Exim insists that every address it handles has a domain attached. For incoming local messages, domainless addresses are automatically qualified with a configured domain value.
Configuration options specify from which remote systems unqualified addresses are acceptable. These are then qualified on arrival. However, a pipe transport is available, and there are facilities for writing messages to files and pipes, optionally in batched SMTP format; these facilities can be used to send messages to other transport mechanisms such as UUCP, provided they can handle domain-style addresses.
Batched SMTP input is also catered for. Exim is not designed for storing mail for dial-in hosts. Although Exim does have basic facilities for scanning incoming messages, these are not comprehensive enough to do full virus or spam scanning. Such operations are best carried out using additional specialized software packages.
If you compile Exim with the content-scanning extension, straightforward interfaces to a number of common scanners are provided. The entries in this file consist of keywords and values, in the style of Smail 3 configuration files.
A default configuration file which is suitable for simple online installations is provided in the distribution, and is described in chapter 7 below. There are also some additional options that are compatible with Smail 3, and some further options that are new to Exim. This information is automatically made into the man page that forms part of the Exim distribution. Control of messages on the queue can be done via certain privileged command line options.
The body of a message is the actual data that the sender wants to transmit. It is the last part of a message, and is separated from the header see below by a blank line. The term bounce is commonly used for this action, and the error reports are often called bounce messages.
The term default appears frequently in this manual. It is used to qualify a value which is used in the absence of any setting in the configuration. It may also qualify an action which is taken unless a configuration setting specifies otherwise. Such deliveries are deferred until a later time. It is not used in that sense here, where it normally refers to the part of an email address following the sign. A message in transit has an associated envelope , as well as a header and a body.
The envelope contains a sender address to which bounce messages should be delivered , and any number of recipient addresses. References to the sender or the recipients of a message usually mean the addresses in the envelope. An MTA uses these addresses for delivery, and for returning bounce messages, not the addresses that appear in the header lines.
Long header lines can be split over several text lines by indenting the continuations. Consult the tcpwrappers documentation for further details. Exim contains code for use on systems that have IPv6 support. It is not known if anyone is actually using A6 records. The support has not been tested for some time. It determines the architecture and operating system types, and creates a build directory if one does not exist. Symbolic links to relevant source files are installed in the build directory.
Warning : The -j parallel flag must not be used with make ; the building process fails if it is set. If this is the first time make has been run, it calls a script that builds a make file inside the build directory, using the configuration files from the Local directory. The new make file is then passed to another instance of make. This does the real work, building a number of utility scripts, and then compiling and linking the binaries for the Exim monitor if configured , a number of utility programs, and finally Exim itself.
The command make makefile can be used to force a rebuild of the make file in the build directory, should this ever be necessary. If you have problems building Exim, check for any comments there may be in the README file concerning your operating system, and also take a look at the FAQ, where some common problems are covered.
The output produced by the make process for compile lines is often very unreadable, because these lines can be very long. For this reason, the normal output is suppressed by default, and instead output similar to that which appears when compiling the 2. However, it is still possible to get the full output, by calling make like this:. When you ask for the full output, it is given in addition to the short output.
The main make file that is created at the beginning of the building process consists of the concatenation of a number of files which set configuration values, followed by a fixed set of make instructions. If a value is set more than once, the last setting overrides any previous ones.
This provides a convenient way of overriding defaults. The files that are concatenated are, in order:. The other three Local files are optional, and are often not needed. Otherwise, the scripts try to get values from the uname command. A number of ad hoc transformations are then applied, to produce the standard names that Exim expects.
You can run these scripts directly from the shell in order to find out what values are being used on your system. Some but not all are mentioned below.
Instead, you should make the changes by putting the new values in an appropriate Local file. Also, the compiler must be called with the option -std1 , to make it recognize some of the features of Standard C that Exim uses.
Most other compilers recognize Standard C by default. Keeping all your local configuration settings separate from the distributed files makes it easy to transfer them to new versions of Exim simply by copying the contents of the Local directory.
All the different kinds of file and database lookup that Exim supports are implemented as separate code modules which are included only if the relevant compile-time options are set. In many cases the relevant include files and interface libraries need to be installed before compiling Exim. However, there are some optional lookup types such as cdb for which the code is entirely contained within Exim, and no external include files or libraries are required.
When a lookup type is not included in the binary, attempts to configure Exim to use it cause run time configuration errors. Exim can be linked with an embedded Perl interpreter, allowing Perl subroutines to be called during string expansion. To enable this facility,. Details of this facility are given in chapter The location of the X11 libraries is something that varies a lot between operating systems, and there may be different versions of X11 to cope with.
Exim itself makes no use of X11, but if you are compiling the Exim monitor, the X11 libraries must be available. These are overridden in some of the operating-system configuration files.
If you need to add any extra libraries to the link steps, these can be put in a variable called EXTRALIBS, which appears in all the link commands, but by default is not defined. The make file copes with rebuilding Exim correctly if any of the configuration files are edited.
The OS directory contains a number of files with names of the form os. These are system-specific C header files that should not normally need to be changed. A similar process is used for overriding things when building the Exim monitor, where the files that are involved are.
The install script copies files only if they are newer than the files they are going to replace. The Exim binary is required to be owned by root and have the setuid bit set, for normal configurations.
Therefore, you must run make install as root so that it can set up the Exim binary in this way. However, in some special situations for example, if a host is doing no local deliveries it may be possible to run Exim without making the binary setuid root see chapter 52 for details. If a run time configuration file already exists, it is left alone.
One change is made to the default configuration file when it is installed: the default configuration contains a router that references a system aliases file. If the system aliases file does not exist, the installation script creates it, and outputs a comment to the user.
The created file contains no aliases, but it does contain comments about the aliases a site should normally have. System aliases and. It is possible to install Exim for special purposes such as building a binary distribution in a private part of the file system. You can do this by a command such as. This has the effect of pre-pending the specified directory to all the file paths, except the name of the system aliases file that appears in the default configuration.
0コメント