| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| exim4:test_exim4 [2016/11/07 22:27] – peter | exim4:test_exim4 [2020/07/15 09:30] (current) – external edit 127.0.0.1 |
|---|
| |
| <code> | <code> |
| john@sharewiz.net | john@example.com |
| router = dovecot_user, transport = dovecot_delivery | router = dovecot_user, transport = dovecot_delivery |
| </code> | </code> |
| 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 |
| |
| </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-the_appendfile_transport.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]]. |
