Wiki

User Tools

Site Tools

Trace: • managing_the_queue
exim4:test_exim4

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
exim4:test_exim4 [2016/11/07 14:59] – created peterexim4:test_exim4 [2020/07/15 09:30] (current) – external edit 127.0.0.1
Line 16: Line 16:
 <code bash> <code bash>
 exim -bt <local username> exim -bt <local username>
 +</code>
 +
 +Result
 +
 +<code>
 +john@example.com
 +  router = dovecot_user, transport = dovecot_delivery
 </code> </code>
  
Line 24: Line 31:
 exim -bt <remote address> exim -bt <remote address>
 </code> </code>
 +
 +Result
 +
 +<code>
 +R: dnslookup for mail@example.com
 +mail@example.com
 +  router = dnslookup, transport = remote_smtp
 +  host mx00.example.com [123.123.11.12] MX=10
 +  host mx01.example.com [123.123.11.13] MX=10
 +</code>
 +
  
 Then try getting it to deliver mail, both locally and remotely.  This can be done by passing messages directly to Exim, without going through a user agent. For example: Then try getting it to deliver mail, both locally and remotely.  This can be done by passing messages directly to Exim, without going through a user agent. For example:
  
 <code bash> <code bash>
-exim -v postmaster@your.domain.example +exim -v postmaster@example.com 
-From: user@your.domain.example +From: user@example.com 
-To: postmaster@your.domain.example+To: postmaster@example.com
 Subject: Testing Exim Subject: Testing Exim
  
Line 54: Line 72:
 </code> </code>
  
-You must be root or an "admin user" in order to do this.  The -d option produces rather a lot of output, but you can cut this down to specific areas.  For example, if you use -d-all+route only the debugging information relevant to routing is included.  (See the -d option in chapter 5 for more details.)+You must be root or an "admin user" in order to do this.  The **-d** option produces rather a lot of output, but you can cut this down to specific areas.  For example, if you use -d-all+route only the debugging information relevant to routing is included.  (See the -d option in chapter 5 for more details.)
  
-One specific problem that has shown up on some sites is the inability to do local deliveries into a shared mailbox directory, because it does not have the "sticky bit" set on it.  By default, Exim tries to create a lock file before writing to a mailbox file, and if it cannot create the lock file, the delivery is deferred.  You can get round this either by setting the "sticky bit" on the directory, or by setting a specific group for local deliveries and allowing that group to create files in the directory (see the comments above the local_delivery transport in the default configuration file).  Another approach is to configure Exim not to use lock files, but just to rely on fcntl() locking instead.  However, you should do this only if all user agents also use fcntl() locking.  For further discussion of locking issues, see [[http://www.exim.org/exim-html-current/doc/html/spec_html/ch-building_and_installing_exim.html|chapter 26]].+One specific problem that has shown up on some sites is the inability to do local deliveries into a shared mailbox directory, because it does not have the "sticky bit" set on it.  By default, Exim tries to create a lock file before writing to a mailbox file, and if it cannot create the lock file, the delivery is deferred.  You can get round this either by setting the "sticky bit" on the directory, or by setting a specific group for local deliveries and allowing that group to create files in the directory (see the comments above the local_delivery transport in the default configuration file).  Another approach is to configure Exim not to use lock files, but just to rely on fcntl() locking instead.  However, you should do this only if all user agents also use fcntl() locking.  For further discussion of locking issues, see [[http://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_appendfile_transport.html|chapter 26]].
  
 One thing that cannot be tested on a system that is already running an MTA is the receipt of incoming SMTP mail on the standard SMTP port.  However, the -oX option can be used to run an Exim daemon that listens on some other port, or inetd can be used to do this.  The -bh option and the exim_checkaccess utility can be used to check out policy controls on incoming SMTP mail. One thing that cannot be tested on a system that is already running an MTA is the receipt of incoming SMTP mail on the standard SMTP port.  However, the -oX option can be used to run an Exim daemon that listens on some other port, or inetd can be used to do this.  The -bh option and the exim_checkaccess utility can be used to check out policy controls on incoming SMTP mail.
Line 62: Line 80:
 Testing a  new version on a system that is already running Exim can most easily be done by building a binary with a different CONFIGURE_FILE setting. From within the run time configuration, all other file and directory names that Exim uses can be altered, in order to keep it entirely clear of the production version. Testing a  new version on a system that is already running Exim can most easily be done by building a binary with a different CONFIGURE_FILE setting. From within the run time configuration, all other file and directory names that Exim uses can be altered, in order to keep it entirely clear of the production version.
  
 +===== References =====
 +
 +http://www.exim.org/exim-html-current/doc/html/spec_html/ch-building_and_installing_exim.html
 +
 +http://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_appendfile_transport.html
exim4/test_exim4.1478530762.txt.gz · Last modified: 2020/07/15 09:30 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki